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. 58 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/dist/ide-config.js b/dist/ide-config.js --- a/dist/ide-config.js +++ b/dist/ide-config.js @@ -87,1 +87,0 @@ -const text = raw.replace(/^/, ''); diff --git a/dist/redact.d.ts b/dist/redact.d.ts --- a/dist/redact.d.ts +++ b/dist/redact.d.ts @@ -12,1 +12,0 @@ -* A git remote as it may leave this machine: `https://user:token@host/...` and `https://token@host/...` diff --git a/dist/redact.js b/dist/redact.js --- a/dist/redact.js +++ b/dist/redact.js @@ -9,1 +9,0 @@ -/** Credentials embedded in a URL: https://user:token@host/... (a git remote with a personal access token). */ @@ -48,1 +47,0 @@ -* A git remote as it may leave this machine: `https://user:token@host/...` and `https://token@host/...`
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.32. 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-server: Hidden zero-width characters detected (KillerSkills verdict caution 58)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 58/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-server/1.0.32 ## Findings with a location - `dist/ide-config.js:87` · Hidden zero-width characters detected — dist/ide-config.js:87 · Hidden zero-width characters detected — may conceal content - `dist/redact.d.ts:12` · URL with embedded credentials — dist/redact.d.ts:12 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.js:9` · URL with embedded credentials — dist/redact.js:9 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.js:48` · URL with embedded credentials — dist/redact.js:48 · 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 nieuwsolutions/agilemonster --clone && cd agilemonster curl -s https://killerskills.ai/skills/npm/mcp-server/1.0.32/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.32 && git commit -am "mcp-server: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/mcp-server/1.0.32/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.