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 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 7 caught lines
Download .patchdiff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -38,1 +38,0 @@ -ssh -i ~/.ssh/id_rsa user@hostname "command" @@ -48,1 +47,0 @@ -IdentityFile ~/.ssh/id_rsa @@ -259,1 +257,0 @@ -"key": "~/.ssh/id_rsa", @@ -302,1 +299,0 @@ -chmod 600 ~/.ssh/id_rsa @@ -305,1 +301,0 @@ -ssh -i ~/.ssh/id_rsa user@hostname diff --git a/scripts/host_manager.py b/scripts/host_manager.py --- a/scripts/host_manager.py +++ b/scripts/host_manager.py @@ -14,1 +14,0 @@ -host_manager.py add production 192.168.1.100 --user admin --key ~/.ssh/id_rsa --tags web,critical diff --git a/scripts/ssh_exec.py b/scripts/ssh_exec.py --- a/scripts/ssh_exec.py +++ b/scripts/ssh_exec.py @@ -10,1 +10,0 @@ -ssh_exec.py 192.168.1.100 "docker ps" --user admin --key ~/.ssh/id_rsa
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: remote-terminal: References a credential file in the home directory (KillerSkills verdict caution 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 **CAUTION 45/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/remote-terminal/1.0.0 ## Findings with a location - `SKILL.md:305` · References a credential file in the home directory — SKILL.md:305 · References a credential file in the home directory - `SKILL.md:38` · References a credential file in the home directory — SKILL.md:38 · References a credential file in the home directory - `SKILL.md:48` · References a credential file in the home directory — SKILL.md:48 · References a credential file in the home directory - `scripts/host_manager.py:14` · References a credential file in the home directory — scripts/host_manager.py:14 · References a credential file in the home directory - `scripts/ssh_exec.py:10` · References a credential file in the home directory — scripts/ssh_exec.py:10 · References a credential file in the home directory - `SKILL.md:302` · References a credential file in the home directory — SKILL.md:302 · References a credential file in the home directory - `SKILL.md:259` · References a credential file in the home directory — SKILL.md:259 · References a credential file in the home directory ## Proposed change The attached patch removes the 7 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.