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. 70 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 7 caught lines
Download .patchdiff --git a/dist/chunk-QB5Z2W52.mjs b/dist/chunk-QB5Z2W52.mjs
--- a/dist/chunk-QB5Z2W52.mjs
+++ b/dist/chunk-QB5Z2W52.mjs
@@ -7543,1 +7543,0 @@
-…y is an authorized_keys-style line: `<type> <base64-key> [comment]`, e.g. from `~/.ssh/id_ed25519.pub`. Send `[]` to remove all keys.", examples: [ …
@@ -10905,1 +10904,0 @@
-throw new Error("runpod: API key required (set RUNPOD_API_KEY or pass apiKey)");
diff --git a/mcp:tools/update-endpoint b/mcp:tools/update-endpoint
--- a/mcp:tools/update-endpoint
+++ b/mcp:tools/update-endpoint
@@ -1,1 +1,0 @@
-ret-looking values as [redacted]: never send that placeholder back, it would overwrite the secret with the literal string. Supply the real value or a {{ RUNP
diff --git a/dist/stdio.mjs b/dist/stdio.mjs
--- a/dist/stdio.mjs
+++ b/dist/stdio.mjs
@@ -7447,1 +7447,0 @@
-…y is an authorized_keys-style line: `<type> <base64-key> [comment]`, e.g. from `~/.ssh/id_ed25519.pub`. Send `[]` to remove all keys.", examples: [ …
@@ -10978,1 +10977,0 @@
-throw new Error("runpod: API key required (set RUNPOD_API_KEY or pass apiKey)");
diff --git a/dist/http.cjs b/dist/http.cjs
--- a/dist/http.cjs
+++ b/dist/http.cjs
@@ -7595,1 +7595,0 @@
-…y is an authorized_keys-style line: `<type> <base64-key> [comment]`, e.g. from `~/.ssh/id_ed25519.pub`. Send `[]` to remove all keys.", examples: [ …
@@ -11150,1 +11149,0 @@
-throw new Error("runpod: API key required (set RUNPOD_API_KEY or pass apiKey)");
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 4.14.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: mcp-server: Credential pass-through configuration (KillerSkills verdict caution 70)
## 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 70/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/4.14.0 ## Findings with a location - `dist/chunk-QB5Z2W52.mjs:10905` · Credential pass-through configuration — dist/chunk-QB5Z2W52.mjs:10905 · Credential pass-through configuration — agent relays sensitive credentials - `mcp:tools/update-endpoint:1` · Tool description instructs the agent: credential exfiltration instruction — mcp:tools/update-endpoint:1 · Instruction aimed at the agent: credential exfiltration instruction - `dist/stdio.mjs:7447` · References a credential file in the home directory — dist/stdio.mjs:7447 · References a credential file in the home directory - `dist/http.cjs:7595` · References a credential file in the home directory — dist/http.cjs:7595 · References a credential file in the home directory - `dist/http.cjs:11150` · Credential pass-through configuration — dist/http.cjs:11150 · Credential pass-through configuration — agent relays sensitive credentials - `dist/stdio.mjs:10978` · Credential pass-through configuration — dist/stdio.mjs:10978 · Credential pass-through configuration — agent relays sensitive credentials - `dist/chunk-QB5Z2W52.mjs:7543` · References a credential file in the home directory — dist/chunk-QB5Z2W52.mjs:7543 · References a credential file in the home directory ## Proposed change The attached patch removes the 7 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 runpod/runpod-mcp --clone && cd runpod-mcp curl -s https://killerskills.ai/skills/npm/mcp-server/4.14.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/4.14.0 && git commit -am "mcp-server: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/mcp-server/4.14.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.