← sn-deep-research@2026.9.11

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

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/workbench-runtime/dist/assets/index-Bv_HE0iq.css b/workbench-runtime/dist/assets/index-Bv_HE0iq.css
--- a/workbench-runtime/dist/assets/index-Bv_HE0iq.css
+++ b/workbench-runtime/dist/assets/index-Bv_HE0iq.css
@@ -1,1 +1,0 @@
-@import "https://fonts.googleapis.com/css2?family=Inter:opsz,[email protected],320;14..32,330;14..32,340;14..32,480;14..32,540;14..32,700&family=JetBrains+Mono:wght@400&display=swap";:root{--ink:#000;--canv
diff --git a/workbench-runtime/dist/assets/MarkdownArtifactViewer-C7xIspsK.js b/workbench-runtime/dist/assets/MarkdownArtifactViewer-C7xIspsK.js
--- a/workbench-runtime/dist/assets/MarkdownArtifactViewer-C7xIspsK.js
+++ b/workbench-runtime/dist/assets/MarkdownArtifactViewer-C7xIspsK.js
@@ -2,1 +2,0 @@
-`,`	`],T=[`/`,`?`,`#`],E=255,D=/^[+a-z0-9A-Z_-]{0,63}$/,re=/^([+a-z0-9A-Z_-]{0,63})(.*)$/,O={javascript:!0,"javascript:":!0},ie={http:!0,https:!0,ftp:!0,gopher:!0,file:!0,"http:":!0,"https:":!0,"ftp:"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2026.9.11. 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: sn-deep-research: URL with embedded credentials (KillerSkills verdict caution 49)

## 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 49/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/sn-deep-research/2026.9.11

## Findings with a location
- `workbench-runtime/dist/assets/index-Bv_HE0iq.css:1` · URL with embedded credentials — workbench-runtime/dist/assets/index-Bv_HE0iq.css:1 · URL with embedded credentials — may be phishing or credential leaking
- `workbench-runtime/dist/assets/MarkdownArtifactViewer-C7xIspsK.js:2` · Hidden zero-width characters detected — workbench-runtime/dist/assets/MarkdownArtifactViewer-C7xIspsK.js:2 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 2 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

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.