← prod-shield@1.2.1

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. 61 · Caution

Evidence

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

Diff · removes 3 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -477,1 +477,0 @@
-- `base64 -d | bash` or similar decode-and-execute patterns
@@ -706,1 +705,0 @@
-- Pass secrets as command-line arguments (visible in `ps aux` and shell history)
@@ -964,1 +962,0 @@
-- Never pass secrets as `--build-arg` to Docker builds

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.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: prod-shield: Host or command assembled from base64 fragments (KillerSkills verdict caution 61)

## 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 61/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/prod-shield/1.2.1

## Findings with a location
- `SKILL.md:477` · Host or command assembled from base64 fragments — SKILL.md:477 · Host or command assembled from base64 fragments
- `SKILL.md:706` · Credential pass-through configuration — SKILL.md:706 · Credential pass-through configuration — agent relays sensitive credentials
- `SKILL.md:964` · Credential pass-through configuration — SKILL.md:964 · Credential pass-through configuration — agent relays sensitive credentials

## Proposed change
The attached patch removes the 3 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 gitleaks/gitleaks --clone && cd gitleaks
curl -s https://killerskills.ai/skills/clawhub/prod-shield/1.2.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.2.1 && git commit -am "prod-shield: Host or command assembled from base64 fragments"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/prod-shield/1.2.1/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.