← auto-deploy@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. 45 · Blocked

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 7 caught lines

Download .patch
diff --git a/scripts/setup.sh b/scripts/setup.sh
--- a/scripts/setup.sh
+++ b/scripts/setup.sh
@@ -23,1 +23,0 @@
-ssh-keygen -t ed25519 -C "openclaw-server" -f ~/.ssh/server_deploy -N ""
@@ -29,1 +28,0 @@
-ssh-keygen -t ed25519 -C "openclaw-server" -f ~/.ssh/server_deploy -N ""
@@ -35,1 +33,0 @@
-cat ~/.ssh/server_deploy.pub
@@ -39,1 +36,0 @@
-echo "  mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -25,1 +25,0 @@
-ssh-keygen -t ed25519 -C "openclaw-deploy" -f ~/.ssh/openclaw_deploy
@@ -28,1 +27,0 @@
-cat ~/.ssh/openclaw_deploy.pub
diff --git a/scripts/deploy.sh b/scripts/deploy.sh
--- a/scripts/deploy.sh
+++ b/scripts/deploy.sh
@@ -60,1 +60,0 @@
-git clone http://${GIT_USER}:${GIT_PASS}@${GIT_URL#http://} points-build

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: auto-deploy: 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/auto-deploy/1.0.0

## Findings with a location
- `scripts/setup.sh:39` · Reads credential paths from the home directory — scripts/setup.sh:39 · Reads credential paths from the home directory
- `scripts/setup.sh:35` · Reads credential paths from the home directory — scripts/setup.sh:35 · Reads credential paths from the home directory
- `SKILL.md:25` · Reads credential paths from the home directory — SKILL.md:25 · Reads credential paths from the home directory
- `scripts/setup.sh:29` · Reads credential paths from the home directory — scripts/setup.sh:29 · Reads credential paths from the home directory
- `SKILL.md:28` · Reads credential paths from the home directory — SKILL.md:28 · Reads credential paths from the home directory
- `scripts/setup.sh:23` · Reads credential paths from the home directory — scripts/setup.sh:23 · Reads credential paths from the home directory
- `scripts/deploy.sh:60` · URL with embedded credentials — scripts/deploy.sh:60 · URL with embedded credentials — may be phishing or credential leaking

## 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._
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.