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 4 caught lines
Download .patchdiff --git a/dist/gate.js b/dist/gate.js
--- a/dist/gate.js
+++ b/dist/gate.js
@@ -3,1 +3,0 @@
-…/\s/g,"").split(">")[0]??"",n=t.length%2?t+"0":t;return/^[0-9A-Fa-f]*$/.test(n)?Buffer.from(n,"hex"):null}function aa(e){let t=/\/Filter\s*(\[[^\]]*\]|\/\w+)/.exec(e);return!t||!t[1]?[]:[...t[1].matchAll(/\/(\w+)/g)].map(n=>n[1]??"")}function …
@@ -45,1 +44,0 @@
-…stname||void 0}catch{return}}function ar(e){if(!e)return null;let t=e.replace(/^ /,"");if(!/\[ZoneTransfer\]/i.test(t))return null;let n=s=>new RegExp(`^\\s*${s}…
diff --git a/dist/scan-worker.js b/dist/scan-worker.js
--- a/dist/scan-worker.js
+++ b/dist/scan-worker.js
@@ -4,1 +4,0 @@
-…/\s/g,"").split(">")[0]??"",n=t.length%2?t+"0":t;return/^[0-9A-Fa-f]*$/.test(n)?Buffer.from(n,"hex"):null}function Oi(e){let t=/\/Filter\s*(\[[^\]]*\]|\/\w+)/.exec(e);return!t||!t[1]?[]:[...t[1].matchAll(/\/(\w+)/g)].map(n=>n[1]??"")}function …
@@ -49,1 +48,0 @@
-…stname||void 0}catch{return}}function Fa(e){if(!e)return null;let t=e.replace(/^ /,"");if(!/\[ZoneTransfer\]/i.test(t))return null;let n=i=>new RegExp(`^\\s*${i}…
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.6.70. 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: mcp: Host or code 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.9.2) 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/npm/mcp/1.6.70 ## Findings with a location - `dist/gate.js:3` · Host or code assembled from base64 fragments — dist/gate.js:3 · Host or code assembled from base64 fragments - `dist/gate.js:45` · Hidden zero-width characters detected — dist/gate.js:45 · Hidden zero-width characters detected — may conceal content - `dist/scan-worker.js:49` · Hidden zero-width characters detected — dist/scan-worker.js:49 · Hidden zero-width characters detected — may conceal content - `dist/scan-worker.js:4` · Host or code assembled from base64 fragments — dist/scan-worker.js:4 · Host or code assembled from base64 fragments ## 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.