anti-bla@0.1.1
CAUTION· install onlyPublisher claims: "Read-only, bounded triage of adversarially hardened artifacts (BLA-style obstruction) to complement REA (Reverse Engineer Anything)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-18 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Collapsed <details> block carrying instructions; Collapsed <details> block carrying instructions; Collapsed <details> block carrying instructions. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
Use `anti-bla` if it is on PATH; otherwise `npx -y [email protected]` (same arguments). Check withFix: Pin versions and sources; vendor anything fetched at install time.log('CLI: `npm install -g anti-bla` puts `anti-bla` on PATH, or the skill falls back to `npx -y anti-bla`. REA itself: `npx rea-agents setup`.');Fix: Pin versions and sources; vendor anything fetched at install time."source": "tools/list advertised by the connected [email protected] MCP server (npx -y [email protected] mcp), observed 2026-11-10",Fix: Pin versions and sources; vendor anything fetched at install time.<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 targeFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.anti-bla report <report.json> [--format markdown|json] [--output f]Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.<summary><strong>Earlier paired agent run on owned fixtures (no BLA)</strong></summary> <br /> The same Sonnet subagent answered 7 questions twice (4 hardened-sFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<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 Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<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. AntFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><strong>What "recovered" means, and what it does not</strong></summary> <br /> - **Decoded strings** come from sound static folding: literals, bitwise Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.report: `anti-bla report <report.json> [--format markdown|json] [--output <file>] [--force]Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for anti-bla@0.1.1 as of 13 min ago. This is the package itself, not its dependencies.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim shambac: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.