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. 78 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 1 caught line

Download .patch

diff --git a/dist/web/assets/main-DQdcRbRl.css b/dist/web/assets/main-DQdcRbRl.css
--- a/dist/web/assets/main-DQdcRbRl.css
+++ b/dist/web/assets/main-DQdcRbRl.css
@@ -1,1 +1,0 @@
-@import "https://fonts.googleapis.com/css2?family=Source+Sans+Pro:ital,wght@0,400;0,600;0,700;0,900;1,400;1,700&display=swap";@layer components;@layer prope…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.34. 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: hf-mcp-server: Base64 encoding combined with network call (KillerSkills verdict caution 78)

## 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 78/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/hf-mcp-server/0.4.34

## Findings with a location
- `dist/web/assets/main-B6UWQI-c.js:9` · Base64 encoding combined with network call — dist/web/assets/main-B6UWQI-c.js:9 · Base64 encoding combined with network call — potential data exfiltration
- `dist/web/assets/main-DQdcRbRl.css:1` · URL with embedded credentials — dist/web/assets/main-DQdcRbRl.css:1 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 1 line 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._

Open the issue on GitHub (evalstate/hf-mcp-server)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork evalstate/hf-mcp-server --clone && cd hf-mcp-server
curl -s https://killerskills.ai/skills/npm/hf-mcp-server/0.4.34/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.4.34 && git commit -am "hf-mcp-server: Base64 encoding combined with network call"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/hf-mcp-server/0.4.34/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.