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. 45 · Blocked
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/deploy/setup_ssh_key.sh b/deploy/setup_ssh_key.sh
--- a/deploy/setup_ssh_key.sh
+++ b/deploy/setup_ssh_key.sh
@@ -51,1 +51,0 @@
-for f in ~/.ssh/id_ed25519.pub ~/.ssh/id_rsa.pub ~/.ssh/id_ecdsa.pub; do
@@ -60,1 +59,0 @@
-ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519 -N "" -C "$(whoami)@$(hostname)"
@@ -61,1 +59,0 @@
-KEY_FILE=~/.ssh/id_ed25519.pub
@@ -84,1 +81,0 @@
-cat "$KEY_FILE" | ssh "${SERVER_SSH}" "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys"
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: skills-monitor: Reads credential paths from the home directory (KillerSkills verdict blocked 45)
## 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 **BLOCKED 45/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/skills-monitor/1.0.0 ## Findings with a location - `deploy/setup_ssh_key.sh:84` · Reads credential paths from the home directory — deploy/setup_ssh_key.sh:84 · Reads credential paths from the home directory - `deploy/setup_ssh_key.sh:60` · References a credential file in the home directory — deploy/setup_ssh_key.sh:60 · References a credential file in the home directory - `deploy/setup_ssh_key.sh:51` · References a credential file in the home directory — deploy/setup_ssh_key.sh:51 · References a credential file in the home directory - `deploy/setup_ssh_key.sh:61` · References a credential file in the home directory — deploy/setup_ssh_key.sh:61 · References a credential file in the home directory ## Proposed change The attached patch removes the 4 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 MerkyorLynn/skills-monitor --clone && cd skills-monitor curl -s https://killerskills.ai/skills/clawhub/skills-monitor/1.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0 && git commit -am "skills-monitor: Reads credential paths from the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/skills-monitor/1.0.0/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.