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. 77 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 11 caught lines
Download .patchdiff --git a/dist/redact.d.ts b/dist/redact.d.ts
--- a/dist/redact.d.ts
+++ b/dist/redact.d.ts
@@ -46,1 +46,0 @@
-* monitor's own URL mid-sentence ("connect ETIMEDOUT to http://admin:s3cret@host"). One
@@ -126,1 +125,0 @@
-* `redactUrlCredentials` turns `http://user:pass@host` into `http://***:***@host`, and that
@@ -139,1 +137,0 @@
-* nothing is restored. Otherwise `http://***:***@somewhere-else` would send a password the
diff --git a/dist/monitors/rules.js b/dist/monitors/rules.js
--- a/dist/monitors/rules.js
+++ b/dist/monitors/rules.js
@@ -277,1 +277,0 @@
-* Each node is a URL, and `redactUrlCredentials` turns `https://user:pass@host` into
@@ -278,1 +277,0 @@
-* `https://***:***@host`. `rehydrateSecrets` skips arrays and only recognises a bare "***"
diff --git a/dist/monitors/rules.d.ts b/dist/monitors/rules.d.ts
--- a/dist/monitors/rules.d.ts
+++ b/dist/monitors/rules.d.ts
@@ -52,1 +52,0 @@
-* Each node is a URL, and `redactUrlCredentials` turns `https://user:pass@host` into
@@ -53,1 +52,0 @@
-* `https://***:***@host`. `rehydrateSecrets` skips arrays and only recognises a bare "***"
diff --git a/dist/redact.js b/dist/redact.js
--- a/dist/redact.js
+++ b/dist/redact.js
@@ -90,1 +90,0 @@
-* monitor's own URL mid-sentence ("connect ETIMEDOUT to http://admin:s3cret@host"). One
@@ -318,1 +317,0 @@
-* `redactUrlCredentials` turns `http://user:pass@host` into `http://***:***@host`, and that
@@ -331,1 +329,0 @@
-* nothing is restored. Otherwise `http://***:***@somewhere-else` would send a password the
diff --git a/dist/tools/docker-hosts.js b/dist/tools/docker-hosts.js
--- a/dist/tools/docker-hosts.js
+++ b/dist/tools/docker-hosts.js
@@ -26,1 +26,0 @@
-// A TCP dockerDaemon can be http://user:pass@host:2375 — the field name gives no
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.16.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-uptime-kuma: URL with embedded credentials (KillerSkills verdict caution 77)
## 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 77/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-uptime-kuma/0.16.0 ## Findings with a location - `dist/redact.d.ts:126` · URL with embedded credentials — dist/redact.d.ts:126 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.d.ts:46` · URL with embedded credentials — dist/redact.d.ts:46 · URL with embedded credentials — may be phishing or credential leaking - `dist/monitors/rules.js:278` · URL with embedded credentials — dist/monitors/rules.js:278 · URL with embedded credentials — may be phishing or credential leaking - `dist/monitors/rules.js:277` · URL with embedded credentials — dist/monitors/rules.js:277 · URL with embedded credentials — may be phishing or credential leaking - `dist/monitors/rules.d.ts:53` · URL with embedded credentials — dist/monitors/rules.d.ts:53 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.js:318` · URL with embedded credentials — dist/redact.js:318 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.js:90` · URL with embedded credentials — dist/redact.js:90 · URL with embedded credentials — may be phishing or credential leaking - `dist/tools/docker-hosts.js:26` · URL with embedded credentials — dist/tools/docker-hosts.js:26 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.d.ts:139` · URL with embedded credentials — dist/redact.d.ts:139 · URL with embedded credentials — may be phishing or credential leaking - `dist/redact.js:331` · URL with embedded credentials — dist/redact.js:331 · URL with embedded credentials — may be phishing or credential leaking - `dist/monitors/rules.d.ts:52` · URL with embedded credentials — dist/monitors/rules.d.ts:52 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 11 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 DavidFuchs/mcp-uptime-kuma --clone && cd mcp-uptime-kuma curl -s https://killerskills.ai/skills/npm/mcp-uptime-kuma/0.16.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.16.0 && git commit -am "mcp-uptime-kuma: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/mcp-uptime-kuma/0.16.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.