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 3 caught lines
Download .patchdiff --git a/run.go b/run.go --- a/run.go +++ b/run.go @@ -336,1 +336,0 @@ -waitSecret = "Type the password in the page, then let the agent continue" diff --git a/main.go b/main.go --- a/main.go +++ b/main.go @@ -70,1 +70,0 @@ -token: strings.TrimSpace(os.Getenv(pkgmeta.RoomRelayTokenEnv)), @@ -73,1 +72,0 @@ -fmt.Fprintf(os.Stderr, "bnbloc-browser: %s and %s are required (the bridge sets them for a room-credential tool)\n", pkgmeta.RoomRelayURLEnv, pkgmeta.RoomRelayTokenEnv)
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.7.5. 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: bnbloc-browser: Prompting user to enter sensitive 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.9.2) 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/glama/bnbloc-browser/0.7.5 ## Findings with a location - `run.go:336` · Prompting user to enter sensitive credentials — run.go:336 · Prompting user to enter sensitive credentials — social engineering - `main.go:70` · Credential pass-through configuration — main.go:70 · Credential pass-through configuration — agent relays sensitive credentials - `main.go:73` · Credential pass-through configuration — main.go:73 · Credential pass-through configuration — agent relays sensitive credentials ## Proposed change The attached patch removes the 3 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 luckylhb90/bnbloc-browser --clone && cd bnbloc-browser curl -s https://killerskills.ai/skills/glama/bnbloc-browser/0.7.5/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.7.5 && git commit -am "bnbloc-browser: Prompting user to enter sensitive credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/bnbloc-browser/0.7.5/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.