← mcp-server@4.12.0

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 10 caught lines

Download .patch
diff --git a/dist/hosted.cjs b/dist/hosted.cjs
--- a/dist/hosted.cjs
+++ b/dist/hosted.cjs
@@ -6779,1 +6779,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: [ …
@@ -10216,1 +10215,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
@@ -6776,1 +6776,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: [ …
@@ -10213,1 +10212,0 @@
-throw new Error("runpod: API key required (set RUNPOD_API_KEY or pass apiKey)");
diff --git a/dist/stdio.cjs b/dist/stdio.cjs
--- a/dist/stdio.cjs
+++ b/dist/stdio.cjs
@@ -7851,1 +7851,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: [ …
@@ -11267,1 +11266,0 @@
-throw new Error("runpod: API key required (set RUNPOD_API_KEY or pass apiKey)");
diff --git a/dist/chunk-LVRT6ZRI.mjs b/dist/chunk-LVRT6ZRI.mjs
--- a/dist/chunk-LVRT6ZRI.mjs
+++ b/dist/chunk-LVRT6ZRI.mjs
@@ -6734,1 +6734,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: [ …
@@ -9996,1 +9995,0 @@
-throw new Error("runpod: API key required (set RUNPOD_API_KEY or pass apiKey)");
diff --git a/dist/stdio.mjs b/dist/stdio.mjs
--- a/dist/stdio.mjs
+++ b/dist/stdio.mjs
@@ -6686,1 +6686,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: [ …
@@ -10099,1 +10098,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.12.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.8.1) 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.12.0

## Findings with a location
- `dist/hosted.cjs:10216` · Credential pass-through configuration — dist/hosted.cjs:10216 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/http.cjs:6776` · References a credential file in the home directory — dist/http.cjs:6776 · References a credential file in the home directory
- `dist/stdio.cjs:7851` · References a credential file in the home directory — dist/stdio.cjs:7851 · References a credential file in the home directory
- `dist/http.cjs:10213` · Credential pass-through configuration — dist/http.cjs:10213 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/chunk-LVRT6ZRI.mjs:6734` · References a credential file in the home directory — dist/chunk-LVRT6ZRI.mjs:6734 · References a credential file in the home directory
- `dist/hosted.cjs:6779` · References a credential file in the home directory — dist/hosted.cjs:6779 · References a credential file in the home directory
- `dist/stdio.cjs:11267` · Credential pass-through configuration — dist/stdio.cjs:11267 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/stdio.mjs:10099` · Credential pass-through configuration — dist/stdio.mjs:10099 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/chunk-LVRT6ZRI.mjs:9996` · Credential pass-through configuration — dist/chunk-LVRT6ZRI.mjs:9996 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/stdio.mjs:6686` · References a credential file in the home directory — dist/stdio.mjs:6686 · References a credential file in the home directory

## Proposed change
The attached patch removes the 10 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.12.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/4.12.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.12.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.