← erc8004-agent@0.0.2

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 69 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 6 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -261,1 +261,0 @@
-2. **After wallet creation** — Write address + backend info to MEMORY.md. Private key goes to proxy keystore only.
@@ -262,1 +261,0 @@
-3. **After registration** — Write agentId, agentRegistry, agentURI, chainId to MEMORY.md.
@@ -346,1 +344,0 @@
-// Write ONLY public data to MEMORY.md
@@ -391,1 +388,0 @@
-After building, update MEMORY.md profile:
@@ -496,1 +492,0 @@
-After `npm run register`, update MEMORY.md with the output agentId.
diff --git a/references/security-model.md b/references/security-model.md
--- a/references/security-model.md
+++ b/references/security-model.md
@@ -199,1 +199,0 @@
-4. Update MEMORY.md with the new address

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.0.2. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: erc8004-agent: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 69)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 69/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/erc8004-agent/0.0.2

## Findings with a location
- `SKILL.md:391` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:391 · Instructs the agent to modify its persistent memory or instruction files
- `SKILL.md:496` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:496 · Instructs the agent to modify its persistent memory or instruction files
- `SKILL.md:261` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:261 · Instructs the agent to modify its persistent memory or instruction files
- `SKILL.md:346` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:346 · Instructs the agent to modify its persistent memory or instruction files
- `references/security-model.md:199` · Instructs the agent to modify its persistent memory or instruction files — references/security-model.md:199 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `SKILL.md:262` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:262 · Instructs the agent to modify its persistent memory or instruction files

## Proposed change
The attached patch removes the 6 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.