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. 70 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/scripts/install_openclaw_remote.sh b/scripts/install_openclaw_remote.sh --- a/scripts/install_openclaw_remote.sh +++ b/scripts/install_openclaw_remote.sh @@ -96,1 +96,0 @@ -$0 [email protected] user ~/.ssh/id_rsa @@ -99,1 +98,0 @@ -$0 [email protected] user ~/.ssh/id_rsa --async @@ -102,1 +100,0 @@ -$0 [email protected] user ~/.ssh/id_rsa --docker diff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -175,1 +175,0 @@ -chmod 600 ~/.ssh/id_rsa @@ -178,1 +177,0 @@ -ssh-add ~/.ssh/id_rsa
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.1. 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: openclaw-remote-install: References a credential file in the home directory (KillerSkills verdict caution 70)
## 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 70/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/openclaw-remote-install/1.0.1 ## Findings with a location - `scripts/install_openclaw_remote.sh:96` · References a credential file in the home directory — scripts/install_openclaw_remote.sh:96 · References a credential file in the home directory - `SKILL.md:175` · References a credential file in the home directory — SKILL.md:175 · References a credential file in the home directory - `scripts/install_openclaw_remote.sh:99` · References a credential file in the home directory — scripts/install_openclaw_remote.sh:99 · References a credential file in the home directory - `SKILL.md:178` · References a credential file in the home directory — SKILL.md:178 · References a credential file in the home directory - `scripts/install_openclaw_remote.sh:102` · References a credential file in the home directory — scripts/install_openclaw_remote.sh:102 · References a credential file in the home directory ## Proposed change The attached patch removes the 5 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.