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

Evidence

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

Diff · removes 9 caught lines

Download .patch

diff --git a/bash_security/bash_categories.json b/bash_security/bash_categories.json
--- a/bash_security/bash_categories.json
+++ b/bash_security/bash_categories.json
@@ -26,1 +26,0 @@
-"base64 -d | bash",
@@ -77,1 +76,0 @@
-"base64 -d",
diff --git a/bash_security/bash_ast_normalize.py b/bash_security/bash_ast_normalize.py
--- a/bash_security/bash_ast_normalize.py
+++ b/bash_security/bash_ast_normalize.py
@@ -11,1 +11,0 @@
-4. 管道解码执行:  base64 -d x | bash / printf '\\x..'          —— 解码后直接执行,绕过字符串匹配
diff --git a/bash_security/bash_raw_traits.json b/bash_security/bash_raw_traits.json
--- a/bash_security/bash_raw_traits.json
+++ b/bash_security/bash_raw_traits.json
@@ -32,1 +32,0 @@
-"base64 -d | bash",
@@ -117,1 +116,0 @@
-"base64 -d | bash",
@@ -118,1 +116,0 @@
-"base64 -d | sh",
diff --git a/bash_security/bash_file_write.json b/bash_security/bash_file_write.json
--- a/bash_security/bash_file_write.json
+++ b/bash_security/bash_file_write.json
@@ -97,1 +97,0 @@
-"危险内容特征": ["/dev/tcp/", "bash -i", "exec /bin/", "nc -e", "base64 -d | bash"],
@@ -108,1 +107,0 @@
-"危险内容特征": ["chmod u+s", "useradd -u 0", "iptables -F", "/dev/tcp/", "base64 -d | bash", "LD_PRELOAD"],
diff --git a/js_security/js_ast_normalize.py b/js_security/js_ast_normalize.py
--- a/js_security/js_ast_normalize.py
+++ b/js_security/js_ast_normalize.py
@@ -19,1 +19,0 @@
-5. 污点链摊平   : a=process.env.CMD; b=atob(a); eval(b) → eval(atob(process.env.CMD))

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

## 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 68/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/poly-mal-scan/0.0.2

## Findings with a location
- `bash_security/bash_categories.json:26` · Host or command assembled from base64 fragments — bash_security/bash_categories.json:26 · Host or command assembled from base64 fragments
- `bash_security/bash_categories.json:77` · Host or command assembled from base64 fragments — bash_security/bash_categories.json:77 · Host or command assembled from base64 fragments
- `bash_security/bash_ast_normalize.py:11` · Host or command assembled from base64 fragments — bash_security/bash_ast_normalize.py:11 · Host or command assembled from base64 fragments
- `bash_security/bash_raw_traits.json:118` · Host or command assembled from base64 fragments — bash_security/bash_raw_traits.json:118 · Host or command assembled from base64 fragments
- `bash_security/bash_raw_traits.json:32` · Host or command assembled from base64 fragments — bash_security/bash_raw_traits.json:32 · Host or command assembled from base64 fragments
- `bash_security/bash_raw_traits.json:117` · Host or command assembled from base64 fragments — bash_security/bash_raw_traits.json:117 · Host or command assembled from base64 fragments
- `bash_security/bash_file_write.json:97` · Host or command assembled from base64 fragments — bash_security/bash_file_write.json:97 · Host or command assembled from base64 fragments
- `js_security/js_ast_normalize.py:19` · Host or code assembled from base64 fragments — js_security/js_ast_normalize.py:19 · Host or code assembled from base64 fragments
- `bash_security/bash_file_write.json:108` · Host or command assembled from base64 fragments — bash_security/bash_file_write.json:108 · Host or command assembled from base64 fragments

## Proposed change
The attached patch removes the 9 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.