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. 64 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/tools/soul-viz.py b/tools/soul-viz.py
--- a/tools/soul-viz.py
+++ b/tools/soul-viz.py
@@ -182,1 +182,0 @@
-@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@300;400;500;700&family=DM+Sans:ital,wght@0,300;0,400;0,500;0,700;1,400&display=swap');
@@ -1356,1 +1355,0 @@
-@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@300;400;500;700&family=DM+Sans:ital,wght@0,300;0,400;0,500;0,700;1,400&display=swap');
diff --git a/configure.md b/configure.md
--- a/configure.md
+++ b/configure.md
@@ -756,1 +756,0 @@
-### Step 8: Update AGENTS.md
@@ -882,1 +881,0 @@
-Add this in the Memory area of AGENTS.md:
@@ -969,1 +967,0 @@
-3. Update `MEMORY.md` with distilled learnings from reflections
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: evoclaw: URL with embedded credentials (KillerSkills verdict caution 64)
## 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 64/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/evoclaw/1.0.1 ## Findings with a location - `tools/soul-viz.py:182` · URL with embedded credentials — tools/soul-viz.py:182 · URL with embedded credentials — may be phishing or credential leaking - `configure.md:756` · Instructs the agent to modify its persistent memory or instruction files — configure.md:756 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `configure.md:882` · Instructs the agent to modify its persistent memory or instruction files — configure.md:882 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `tools/soul-viz.py:1356` · URL with embedded credentials — tools/soul-viz.py:1356 · URL with embedded credentials — may be phishing or credential leaking - `configure.md:969` · Instructs the agent to modify its persistent memory or instruction files — configure.md:969 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 5 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.