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. 75 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/src/simtest_funnel_mcp/csvio.py b/src/simtest_funnel_mcp/csvio.py
--- a/src/simtest_funnel_mcp/csvio.py
+++ b/src/simtest_funnel_mcp/csvio.py
@@ -149,1 +149,0 @@
-if out and out[0].startswith(""):
diff --git a/tests/test_mcp_fetch.py b/tests/test_mcp_fetch.py
--- a/tests/test_mcp_fetch.py
+++ b/tests/test_mcp_fetch.py
@@ -87,1 +87,0 @@
-"https://user:[email protected]/run.csv",
diff --git a/tests/test_mcp_csv.py b/tests/test_mcp_csv.py
--- a/tests/test_mcp_csv.py
+++ b/tests/test_mcp_csv.py
@@ -129,1 +129,0 @@
-sf = load_csv(write_csv("a.csv", "time,a\r\n0,1\r\n1,2\r\n"))
diff --git a/tests/test_mcp_url_server.py b/tests/test_mcp_url_server.py
--- a/tests/test_mcp_url_server.py
+++ b/tests/test_mcp_url_server.py
@@ -192,1 +192,0 @@
-cred = _call(srv, "describe_signals", {"path": "https://u:[email protected]/r.csv"})
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.0b20. 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: simtest-funnel-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 75)
## 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 75/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/simtest-funnel-mcp/1.0.0b20 ## Findings with a location - `src/simtest_funnel_mcp/csvio.py:149` · Hidden zero-width characters detected — src/simtest_funnel_mcp/csvio.py:149 · Hidden zero-width characters detected — may conceal content - `tests/test_mcp_fetch.py:87` · URL with embedded credentials — tests/test_mcp_fetch.py:87 · URL with embedded credentials — may be phishing or credential leaking - `tests/test_mcp_csv.py:129` · Hidden zero-width characters detected — tests/test_mcp_csv.py:129 · Hidden zero-width characters detected — may conceal content - `tests/test_mcp_url_server.py:192` · URL with embedded credentials — tests/test_mcp_url_server.py:192 · 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._
# or from a terminal, under your own account: gh repo fork Symoptia/simtest-funnel --clone && cd simtest-funnel curl -s https://killerskills.ai/skills/pypi/simtest-funnel-mcp/1.0.0b20/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0b20 && git commit -am "simtest-funnel-mcp: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/simtest-funnel-mcp/1.0.0b20/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.