hunting-signature-replay-and-eip712-domain-trust SKILL.md skillA
hunting-signature-replay-and-eip712-domain-trust from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/hunting-signature-replay-and-eip712-domain-trust@git:20260901.f8395d1Pins git:20260901.f8395d1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/hunting-signature-replay-and-eip712-domain-trust/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260901.f8395d1, committed Sep 1, 2026
- Size
- 10,034 bytes
- Repository stars
- 26
- License
- MIT
Hunt for signed messages a contract or backend accepts more than once or in a context they were never meant for: an EIP-712 signature with no nonce so it replays, a signature missing chain id or verifying-contract in its domain separator so it replays across chains or deployments, a permit or meta-transaction reused after it was already consumed, a signature whose signed fields omit something the action depends on so a different action reuses it, and a signer recovery that accepts a malleable…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Hunting signature replay and EIP-712 domain trust: a signature authorizes one action, once, here A signature is an authorization, and an authorization has to be bound to exactly what it authorizes: one action, on one chain, at one contract, used once. When any part of that binding is missing, the same signature authorizes more than the signer intended. EIP-712 exists to make the binding explicit, the domain separator carries the chain id and the verifying contract, and the typed data carries the action's fields, but a contract only gets the protection it actually checks. A signature with no nonce can be submitted again, so a permit or meta-transaction replays. A domain separator missing the chain id or the verifying contract lets a signature valid on one chain or one deployment be replayed on another. Signed fields that omit something the action depends on, an amount, a recipient, a deadline, let a different action reuse the same signature. And signer recovery that accepts a malleable signature or an unchecked zero address lets a forged or duplicated signature through. The hunt is to find where a signed message is verified and check whether its binding is …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/hunting-signature-replay-and-eip712-domain-trust@sha256:32ee71a51a9f0ee8The line at the top of this page pins the label git:20260901.f8395d1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hi7aascr7j4c5cba)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 1, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10034 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hi7aascr7j4c5cba GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/hunting-signature-replay-and-eip712-domain-trust GET https://markdownregistry.com/api/v1/blob/32ee71a51a9f0ee8ea06d6b641c5c7e4c947e61d2792bc551cd27721c85d0f20
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.