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. 63 · Caution
Evidence
- Read ~/clawd/skills/node-scaling/.npmrc, ~/.npmrc in the decoy home directory.
Diff · removes 3 caught lines
Download .patchdiff --git a/bin/setup.js b/bin/setup.js
--- a/bin/setup.js
+++ b/bin/setup.js
@@ -195,1 +195,0 @@
-print('\nStep 2: Enter your API key');
diff --git a/install.sh b/install.sh
--- a/install.sh
+++ b/install.sh
@@ -103,1 +103,0 @@
-echo " • Add rules to AGENTS.md → Agent auto-detects parallel tasks"
diff --git a/INSTALL.md b/INSTALL.md
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -9,1 +9,0 @@
-Users who want their agent to consider Swarm for parallelizable tasks can add guidance to their AGENTS.md file.
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.7. 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: swarm: Read ~/clawd/skills/node-scaling/.npmrc, ~/.npmrc in the decoy home directory (KillerSkills verdict caution 63)
## 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 63/100**. Summary: reads credential files. - Read ~/clawd/skills/node-scaling/.npmrc, ~/.npmrc in the decoy home directory. Full trace and findings: https://killerskills.ai/skills/clawhub/swarm/1.3.7 ## Findings with a location - `bin/setup.js:195` · Prompting user to enter sensitive credentials — bin/setup.js:195 · Prompting user to enter sensitive credentials — social engineering - `install.sh:103` · Instructs the agent to modify its persistent memory or instruction files — install.sh:103 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `INSTALL.md:9` · Instructs the agent to modify its persistent memory or instruction files — INSTALL.md:9 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 3 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._
# or from a terminal, under your own account: gh repo fork clawdbot/node-scaling --clone && cd node-scaling curl -s https://killerskills.ai/skills/clawhub/swarm/1.3.7/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.3.7 && git commit -am "swarm: Read ~/clawd/skills/node-scaling/.npmrc, ~/.npmrc in the decoy home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/swarm/1.3.7/patch.md)
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.