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. 65 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/lib/fix/apply.js b/lib/fix/apply.js
--- a/lib/fix/apply.js
+++ b/lib/fix/apply.js
@@ -40,1 +40,0 @@
-// Code points HFS+ ignores in names, so ".git" is ".git" on macOS (CVE-2014-9390).
@@ -41,1 +40,0 @@
-const IGNORABLE = /[----]/g;
diff --git a/lib/retirejs.js b/lib/retirejs.js
--- a/lib/retirejs.js
+++ b/lib/retirejs.js
@@ -9,1 +9,0 @@
-* 2. File content pattern matching (/*! jQuery v3.5.1 */)
diff --git a/src/mcp/results.js b/src/mcp/results.js
--- a/src/mcp/results.js
+++ b/src/mcp/results.js
@@ -36,1 +36,0 @@
-const HIDDEN = /[\u0000-\u0008\u000B\u000C\u000E-\u001F\u007F-\u009Fᅟᅠ឴឵----ㅤ︀-️ᅠ\u{E0000}-\u{E007F}\u{E0100}-\u{E01EF}]+/gu;
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.3.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: penthera: Hidden zero-width characters detected (KillerSkills verdict caution 65)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 65/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/npm/penthera/2.3.1 ## Findings with a location - `lib/fix/apply.js:41` · Hidden zero-width characters detected — lib/fix/apply.js:41 · Hidden zero-width characters detected — may conceal content - `lib/fix/apply.js:40` · Hidden zero-width characters detected — lib/fix/apply.js:40 · Hidden zero-width characters detected — may conceal content - `lib/retirejs.js:9` · Hidden zero-width characters detected — lib/retirejs.js:9 · Hidden zero-width characters detected — may conceal content - `src/mcp/results.js:36` · Hidden zero-width characters detected — src/mcp/results.js:36 · Hidden zero-width characters detected — may conceal content ## 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 danoszz/penthera --clone && cd penthera curl -s https://killerskills.ai/skills/npm/penthera/2.3.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/2.3.1 && git commit -am "penthera: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/penthera/2.3.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.