← openclaw-github-backup@1.0.0

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. 43 · Blocked

Evidence

  • Read ~/.ssh/id_ed25519.pub in the decoy home directory.

Diff · removes 4 caught lines

Download .patch
diff --git a/scripts/install.sh b/scripts/install.sh
--- a/scripts/install.sh
+++ b/scripts/install.sh
@@ -40,1 +40,0 @@
-if [[ -f ~/.ssh/id_ed25519.pub ]] || [[ -f ~/.ssh/id_rsa.pub ]]; then
@@ -50,1 +49,0 @@
-cat ~/.ssh/id_ed25519.pub 2>/dev/null || cat ~/.ssh/id_rsa.pub 2>/dev/null
@@ -60,1 +58,0 @@
-ssh-keygen -t ed25519 -C "openclaw-backup" -f ~/.ssh/id_ed25519 -N ""
@@ -64,1 +61,0 @@
-cat ~/.ssh/id_ed25519.pub

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: openclaw-github-backup: Read ~/.ssh/id_ed25519.pub in the decoy home directory (KillerSkills verdict blocked 43)

## 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 **BLOCKED 43/100**. Summary: reads credential files.

- Read ~/.ssh/id_ed25519.pub in the decoy home directory.

Full trace and findings: https://killerskills.ai/skills/clawhub/openclaw-github-backup/1.0.0

## Findings with a location
- `scripts/install.sh:40` · References a credential file in the home directory — scripts/install.sh:40 · References a credential file in the home directory
- `scripts/install.sh:60` · Reads credential paths from the home directory — scripts/install.sh:60 · Reads credential paths from the home directory
- `scripts/install.sh:50` · Reads credential paths from the home directory — scripts/install.sh:50 · Reads credential paths from the home directory
- `scripts/install.sh:64` · Reads credential paths from the home directory — scripts/install.sh:64 · Reads credential paths from the home directory
- `scripts/install.sh:50` · References a credential file in the home directory — scripts/install.sh:50 · References a credential file in the home directory
- `scripts/install.sh:60` · References a credential file in the home directory — scripts/install.sh:60 · 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

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.