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. 68 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 7 caught lines
Download .patchdiff --git a/crates/stealth/src/indexeddb.js b/crates/stealth/src/indexeddb.js
--- a/crates/stealth/src/indexeddb.js
+++ b/crates/stealth/src/indexeddb.js
@@ -74,1 +74,0 @@
-const IDENT = /^[$_\p{ID_Start}][$_\p{ID_Continue}]*$/u;
diff --git a/crates/cdp/src/server.rs b/crates/cdp/src/server.rs
--- a/crates/cdp/src/server.rs
+++ b/crates/cdp/src/server.rs
@@ -3073,1 +3073,0 @@
-let p = super::parse_proxy_server("http://user:[email protected]:8080").unwrap();
diff --git a/crates/cli/src/main.rs b/crates/cli/src/main.rs
--- a/crates/cli/src/main.rs
+++ b/crates/cli/src/main.rs
@@ -109,1 +109,0 @@
-/// `http://user:pass@host:port` or `socks5://host:port`. Essential for
@@ -3213,1 +3212,0 @@
-let p = parse_proxy("http://user:[email protected]:8080").expect("should parse");
@@ -3248,1 +3246,0 @@
-assert_eq!(parse_proxy("http://u:[email protected]:80").expect(":80").port, 80);
@@ -3255,1 +3252,0 @@
-let p = parse_proxy("http://us%40er:p%3Ass%[email protected]:3128").expect("should parse");
diff --git a/crates/pool/src/canvas.rs b/crates/pool/src/canvas.rs
--- a/crates/pool/src/canvas.rs
+++ b/crates/pool/src/canvas.rs
@@ -1726,1 +1726,0 @@
-for seq in ["👩❤️💋👨", "👨👩👧👦", "👨👩👦", "🇺🇦", "👍🏽"] {
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r1. 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: nokk: Hidden zero-width characters detected (KillerSkills verdict caution 68)
## What the honeypot observed
KillerSkills ran **nokk@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 68/100**. Summary: no network, touches nothing outside the project, writes no memory.
- See the findings below.
Full trace and findings: https://killerskills.ai/skills/glama/nokk/r1
## Findings with a location
- `crates/stealth/src/indexeddb.js:74` · Hidden zero-width characters detected — crates/stealth/src/indexeddb.js:74 · Hidden zero-width characters detected — may conceal content
- `crates/cdp/src/server.rs:3073` · URL with embedded credentials — crates/cdp/src/server.rs:3073 · URL with embedded credentials — may be phishing or credential leaking
- `crates/cli/src/main.rs:3248` · URL with embedded credentials — crates/cli/src/main.rs:3248 · URL with embedded credentials — may be phishing or credential leaking
- `crates/cli/src/main.rs:3213` · URL with embedded credentials — crates/cli/src/main.rs:3213 · URL with embedded credentials — may be phishing or credential leaking
- `crates/cli/src/main.rs:109` · URL with embedded credentials — crates/cli/src/main.rs:109 · URL with embedded credentials — may be phishing or credential leaking
- `crates/pool/src/canvas.rs:1726` · Hidden zero-width characters detected — crates/pool/src/canvas.rs:1726 · Hidden zero-width characters detected — may conceal content
- `crates/cli/src/main.rs:3255` · URL with embedded credentials — crates/cli/src/main.rs:3255 · URL with embedded credentials — may be phishing or credential leaking
## Proposed change
The attached patch removes the 7 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 koloss777/nokk --clone && cd nokk curl -s https://killerskills.ai/skills/glama/nokk/r1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/r1 && git commit -am "nokk: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/nokk/r1/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.