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. 75 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/browser/ui/base-layout.mjs b/browser/ui/base-layout.mjs
--- a/browser/ui/base-layout.mjs
+++ b/browser/ui/base-layout.mjs
@@ -10,1 +10,0 @@
-stylesheet: "https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"
diff --git a/index.js b/index.js
--- a/index.js
+++ b/index.js
@@ -6,1 +6,0 @@
-…lwind:"https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4",fonts:{preconnect:["https://fonts.googleapis.com","https://fonts.gstatic.com"],stylesheet:"https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"}};var BUILT_IN_AUTH_PAGE_CSP=["default-src 'self'"…
diff --git a/esm/index.mjs b/esm/index.mjs
--- a/esm/index.mjs
+++ b/esm/index.mjs
@@ -9,1 +9,0 @@
-…lwind:"https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4",fonts:{preconnect:["https://fonts.googleapis.com","https://fonts.gstatic.com"],stylesheet:"https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap"}};var BUILT_IN_AUTH_PAGE_CSP=["default-src 'self'"…
diff --git a/ui/base-layout.d.ts b/ui/base-layout.d.ts
--- a/ui/base-layout.d.ts
+++ b/ui/base-layout.d.ts
@@ -36,1 +36,0 @@
-readonly stylesheet: "https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap";
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.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: auth: URL with embedded credentials (KillerSkills verdict caution 75)
## 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 75/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/auth/1.12.0 ## Findings with a location - `browser/ui/base-layout.mjs:10` · URL with embedded credentials — browser/ui/base-layout.mjs:10 · URL with embedded credentials — may be phishing or credential leaking - `index.js:6` · URL with embedded credentials — index.js:6 · URL with embedded credentials — may be phishing or credential leaking - `esm/index.mjs:9` · URL with embedded credentials — esm/index.mjs:9 · URL with embedded credentials — may be phishing or credential leaking - `esm/index.mjs:397` · Base64 encoding combined with network call — esm/index.mjs:397 · Base64 encoding combined with network call — potential data exfiltration - `ui/base-layout.d.ts:36` · URL with embedded credentials — ui/base-layout.d.ts:36 · URL with embedded credentials — may be phishing or credential leaking - `index.js:394` · Base64 encoding combined with network call — index.js:394 · Base64 encoding combined with network call — potential data exfiltration ## 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 agentfront/frontmcp --clone && cd frontmcp curl -s https://killerskills.ai/skills/npm/auth/1.12.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.12.0 && git commit -am "auth: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/auth/1.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.