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 4 caught lines
Download .patchdiff --git a/agent_reach/cli.py b/agent_reach/cli.py
--- a/agent_reach/cli.py
+++ b/agent_reach/cli.py
@@ -66,1 +66,0 @@
-help="Residential proxy for Reddit/Bilibili (http://user:pass@ip:port)")
@@ -232,1 +231,0 @@
-print(" For full access: agent-reach configure proxy http://user:pass@ip:port")
@@ -1062,1 +1060,0 @@
-print(" 格式: http://用户名:密码@IP:端口")
diff --git a/agent_reach/channels/reddit.py b/agent_reach/channels/reddit.py
--- a/agent_reach/channels/reddit.py
+++ b/agent_reach/channels/reddit.py
@@ -25,1 +25,0 @@
-" agent-reach configure proxy http://user:pass@ip:port"
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: agent-reach-skip: URL with embedded credentials (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/agent-reach-skip/1.0.0 ## Findings with a location - `agent_reach/cli.py:1062` · URL with embedded credentials — agent_reach/cli.py:1062 · URL with embedded credentials — may be phishing or credential leaking - `agent_reach/cli.py:232` · URL with embedded credentials — agent_reach/cli.py:232 · URL with embedded credentials — may be phishing or credential leaking - `agent_reach/cli.py:66` · URL with embedded credentials — agent_reach/cli.py:66 · URL with embedded credentials — may be phishing or credential leaking - `agent_reach/channels/reddit.py:25` · URL with embedded credentials — agent_reach/channels/reddit.py:25 · URL with embedded credentials — may be phishing or credential leaking ## 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._
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.