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. 73 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 3 caught lines
Download .patchdiff --git a/test/hosted.test.ts b/test/hosted.test.ts --- a/test/hosted.test.ts +++ b/test/hosted.test.ts @@ -182,1 +182,0 @@ -"http://localhost:[email protected]/cb", diff --git a/src/lib/config.ts b/src/lib/config.ts --- a/src/lib/config.ts +++ b/src/lib/config.ts @@ -14,1 +14,0 @@ -* is never trusted outside it, so a prompt-injected "upload ~/.ssh/id_rsa" has nothing to read. diff --git a/src/hosted/config.ts b/src/hosted/config.ts --- a/src/hosted/config.ts +++ b/src/hosted/config.ts @@ -97,1 +97,0 @@ -* rule, and it may not carry credentials. `http://localhost:[email protected]/` fails because its host is evil.com.
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.0. 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: populi-mcp: URL with embedded credentials (KillerSkills verdict caution 73)
## 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 73/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/glama/populi-mcp/0.4.0 ## Findings with a location - `test/hosted.test.ts:182` · URL with embedded credentials — test/hosted.test.ts:182 · URL with embedded credentials — may be phishing or credential leaking - `src/lib/config.ts:14` · References a credential file in the home directory — src/lib/config.ts:14 · References a credential file in the home directory - `src/hosted/config.ts:97` · URL with embedded credentials — src/hosted/config.ts:97 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 3 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 kisasa/populi-mcp --clone && cd populi-mcp curl -s https://killerskills.ai/skills/glama/populi-mcp/0.4.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.4.0 && git commit -am "populi-mcp: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/populi-mcp/0.4.0/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.