Anti-BLA

In response to BLA

BLA adds obfuscation, decoys and analysis-exhaustion payloads to artifacts. Anti-BLA is a practical response: keep the original bytes intact, inspect a bounded part of the artifact, and attach evidence to the result.

Use it to recover selected JavaScript facts, navigate amplified ASAR headers, inspect native and data structures, and prepare inspection views for REA. Original hashes, source ranges, assumptions and incomplete results stay visible.

v0.1 is a research preview. Recovery claims apply to the measured tasks. A parser limit, an embedded claim or a successful inspection does not establish complete semantic recovery.

Related MCP server: Fathom

Works with REA

Anti-BLA is a companion to REA — Reverse Engineer Anything by morluto. REA provides the broader reverse-engineering tools; Anti-BLA adds bounded inspection and evidence for selected BLA-protected artifacts. Your agent can use both together.

1. Install REA using its official setup guide.

2. Add Anti-BLA's MCP server and agent skill using the setup below.

3. Inspect the artifact with Anti-BLA, then pass a verified inspection view to REA when needed.

The v0.1 handoff was verified against REA 6.8.0, pinned to 317bf3f. See the measured results for the tested scope.

Quick start

Requires Node.js 24.16+. REA is installed separately; the research comparison used its supported Node.js 24.22.1 runtime.

git clone --branch v0.1 https://github.com/juniper234/anti-bla.git
cd anti-bla
npm ci --ignore-scripts
npm run build
node dist/cli.js --help

Inspect the included benign example without executing it:

node dist/cli.js inspect-javascript examples/routes.mjs --root examples --entry-export register --section facts

Point an operation at your own artifact with an explicit allowed directory:

node dist/cli.js inspect-artifact /path/to/app.asar --root /path/to
node dist/cli.js inspect-asar /path/to/app.asar --root /path/to --limit 20
node dist/cli.js read-asar-entry /path/to/app.asar --root /path/to --member-path package.json --length 1024

Precompiled packages are available from the v0.1 release. Install the downloaded tarball into a directory you own:

npm install --prefix ./anti-bla-tool ./anti-bla-0.1.0.tgz --ignore-scripts --omit=dev
node ./anti-bla-tool/node_modules/anti-bla/dist/cli.js --help

What it does

Default clients are read-only. Inputs are inspected statically; target imports, getters, functions and build hooks are never executed by the companion.

CLI operation names use hyphens: inspect-javascript, read-asar-entry, etc. Use bare --help and discover the configured operation set with capabilities --root <directory>.

What the evidence says

The research pins are BLA 1.5.1 / b2d6436 and REA 6.8.0 / 317bf3f. The source inventory covers 51/51 shield files. Inventory coverage is distinct from recovery coverage.

The initial research workspace passed 348 tests and received independent code, security and evidence reviews. This public release separates 326 portable tests from 22 opt-in research tests that require the original providers and retained raw evidence. Public validation details are recorded in the release summary.

Read the coverage matrix for partial results, damaged GGUF assumptions, source-map information loss, default size refusals, unmeasured memory/cost and other UNKNOWN boundaries. The research notes explain provenance and reproduction.

MCP + agent skill

Generate a concrete configuration for your client:

node dist/cli.js setup --root /absolute/path/to/artifacts --dry-run

This returns absolute server and skill paths. It writes no client settings. The stdio command is:

node dist/cli.js serve --root /absolute/path/to/artifacts

The package includes local Codex and Claude plugin manifests plus the agent skill. A trusted client can set ANTI_BLA_ARTIFACT_ROOT for the plugin launcher; its fallback is the client's trusted working directory. Explicit roots make the scope easiest to review.

For inspection sidecars, supply an existing directory you own:

node dist/cli.js prepare-javascript-view /path/to/app.mjs --root /path/to --workspace /path/to/views --entry-export register

Require a successful response, complete evidence and matching view/evidence hashes before handing the returned directory to REA. Interrupted or uncertain outputs remain UNKNOWN. Follow the sidecar contract; inspection files are never executable-equivalence claims.

Bounds you can see

Adapters retain their own structural caps. Worker heap limits do not bound total process RSS, and filesystem identity checks do not provide an OS sandbox against hostile concurrent writers. ok means the stated bounded operation completed; incomplete coverage and equivalence remain separate. CLI exit codes are 0 for ok, 3 for unknown, and 2 for error.

Development

npm test                 # portable source suite; no research checkout required
npm run test:research    # explicit provider/evidence prerequisites

The research suite fails explicitly when its prerequisites are absent. Missing providers and excluded research tests never count as passed. Controlled dynamic research fixtures run only in disposable containers; the shipped companion performs static inspection.

Documentation

MIT licensed. See LICENSE and third-party notices.