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. 59 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 6 caught lines
Download .patchdiff --git a/index.js b/index.js --- a/index.js +++ b/index.js @@ -8,1 +8,0 @@ -sshKey: '~/.ssh/id_ed25519_central_to', @@ -15,1 +14,0 @@ -sshKey: '~/.ssh/id_ed25519_tokyo' @@ -65,1 +63,0 @@ -let r = await exec(`ssh -i ~/.ssh/id_ed25519_central_to -o StrictHostKeyChecking=no [email protected] "ps aux | grep 'node index.js' | grep -v grep"`); @@ -69,1 +66,0 @@ -r = await exec(`ssh -i ~/.ssh/id_ed25519_tokyo -o StrictHostKeyChecking=no [email protected] "ps aux | grep 'node index.js' | grep -v grep"`); diff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -18,1 +18,0 @@ -| CENTRAL_SSH_KEY | 中央 SSH 密钥路径 | ~/.ssh/id_ed25519 | @@ -19,1 +18,0 @@ -| TOKYO_SSH_KEY | 东京 SSH 密钥路径 | ~/.ssh/id_ed25519 |
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.1.0. 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: evomap-node-controller: References a credential file in the home directory (KillerSkills verdict caution 59)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 59/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/evomap-node-controller/2.1.0 ## Findings with a location - `index.js:65` · References a credential file in the home directory — index.js:65 · References a credential file in the home directory - `index.js:8` · References a credential file in the home directory — index.js:8 · References a credential file in the home directory - `index.js:15` · References a credential file in the home directory — index.js:15 · References a credential file in the home directory - `index.js:69` · References a credential file in the home directory — index.js:69 · References a credential file in the home directory - `SKILL.md:18` · References a credential file in the home directory — SKILL.md:18 · References a credential file in the home directory - `SKILL.md:19` · References a credential file in the home directory — SKILL.md:19 · References a credential file in the home directory ## 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._
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.