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. 45 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 9 caught lines
Download .patchdiff --git a/lib/proxy.js b/lib/proxy.js
--- a/lib/proxy.js
+++ b/lib/proxy.js
@@ -7,1 +7,0 @@
-function decodeProxyCredential(value) {
@@ -20,1 +19,0 @@
-username: decodeProxyCredential(proxy.username),
@@ -21,1 +19,0 @@
-password: decodeProxyCredential(proxy.password),
@@ -102,1 +99,0 @@
-return `http://${user}:${pass}@${host}:${port}`;
@@ -130,1 +126,0 @@
-return `http://${user}:${pass}@${host}:${port}`;
@@ -248,1 +243,0 @@
-* Build a proxy URL string (http://user:pass@host:port) suitable for
@@ -263,1 +257,0 @@
-return `http://${user}:${pass}@${config.backconnectHost}:${config.backconnectPort}`;
diff --git a/tests/unit/proxy.test.js b/tests/unit/proxy.test.js
--- a/tests/unit/proxy.test.js
+++ b/tests/unit/proxy.test.js
@@ -13,1 +13,0 @@
-test('decodes percent-encoded proxy credentials', () => {
@@ -246,1 +245,0 @@
-expect(url).toBe('http://myuser:[email protected]:10001');
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: camofox-browser: Credential pass-through configuration (KillerSkills verdict caution 45)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 45/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/camofox-browser/1.0.0 ## Findings with a location - `lib/proxy.js:7` · Credential pass-through configuration — lib/proxy.js:7 · Credential pass-through configuration — agent relays sensitive credentials - `lib/proxy.js:263` · URL with embedded credentials — lib/proxy.js:263 · URL with embedded credentials — may be phishing or credential leaking - `lib/proxy.js:102` · URL with embedded credentials — lib/proxy.js:102 · URL with embedded credentials — may be phishing or credential leaking - `lib/proxy.js:248` · URL with embedded credentials — lib/proxy.js:248 · URL with embedded credentials — may be phishing or credential leaking - `lib/proxy.js:20` · Credential pass-through configuration — lib/proxy.js:20 · Credential pass-through configuration — agent relays sensitive credentials - `lib/proxy.js:130` · URL with embedded credentials — lib/proxy.js:130 · URL with embedded credentials — may be phishing or credential leaking - `tests/unit/proxy.test.js:13` · Credential pass-through configuration — tests/unit/proxy.test.js:13 · Credential pass-through configuration — agent relays sensitive credentials - `lib/proxy.js:21` · Credential pass-through configuration — lib/proxy.js:21 · Credential pass-through configuration — agent relays sensitive credentials - `tests/unit/proxy.test.js:246` · URL with embedded credentials — tests/unit/proxy.test.js:246 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 9 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 jo-inc/camofox-browser --clone && cd camofox-browser curl -s https://killerskills.ai/skills/clawhub/camofox-browser/1.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0 && git commit -am "camofox-browser: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/camofox-browser/1.0.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.