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. 79 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -105,1 +105,0 @@ -<summary><strong>What "recovered" means, and what it does not</strong></summary> <br /> - **Decoded strings** come from sound static folding: literals, bitwise @@ -128,1 +127,0 @@ -<summary><strong>Earlier paired agent run on owned fixtures (no BLA)</strong></summary> <br /> The same Sonnet subagent answered 7 questions twice (4 hardened-s @@ -180,1 +178,0 @@ -<summary><strong>Is it safe to run on hostile files?</strong></summary> It is built for hostile input. Anti-BLA does not execute, `require` or instantiate targe @@ -187,1 +184,0 @@ -<summary><strong>Can it be fooled?</strong></summary> Yes. Detection is structural and versioned against REA 6.8.0 and BLA 3.2.1. New hardening shapes can slip @@ -194,1 +190,0 @@ -<summary><strong>Is this legal to use?</strong></summary> Use it only on software you own, have permission to analyze, or that was published as a challenge. Ant
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.1. 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: anti-bla: Collapsed <details> block carrying instructions (KillerSkills verdict caution 79)
## 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 79/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/anti-bla/0.1.1 ## Findings with a location - `README.md:180` · Collapsed <details> block carrying instructions — README.md:180 · Collapsed <details> block carrying instructions - `README.md:128` · Collapsed <details> block carrying instructions — README.md:128 · Collapsed <details> block carrying instructions - `README.md:187` · Collapsed <details> block carrying instructions — README.md:187 · Collapsed <details> block carrying instructions - `README.md:194` · Collapsed <details> block carrying instructions — README.md:194 · Collapsed <details> block carrying instructions - `README.md:105` · Collapsed <details> block carrying instructions — README.md:105 · Collapsed <details> block carrying instructions ## Proposed change The attached patch removes the 5 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 ShambaC/anti-bla --clone && cd anti-bla curl -s https://killerskills.ai/skills/npm/anti-bla/0.1.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.1 && git commit -am "anti-bla: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/anti-bla/0.1.1/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.