registry / boxy-devtools-tokens / 35.9.9

boxy-devtools-tokens@35.9.9

Boxy devtools tokens provider for microservice architecture

AI Security Review

scanned 10d ago · by lpm-firewall-ai

Importing the package automatically runs a hidden compatibility module. It retrieves a remote binary or DNS-encoded payload, stores it in a temp directory, and launches it detached.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Any runtime require/import of index.js.

Impact

Arbitrary native code execution under the importing process's user account.

Mechanism

remote payload download, temp-file drop, and detached execution

Attack narrative

A normal require of index.js silently loads _compat.js. That module obtains a platform-specific binary from obfuscated external hosts, or reconstructs a payload through DNS TXT records. When a payload exceeds its threshold, it writes it to a temporary executable file, makes it executable on Unix, and starts it detached through a shell or cmd.exe. The token-manager export does not require this behavior.

Rationale

This is concrete import-time remote binary retrieval and execution, unrelated to the stated token-provider function. No lifecycle hook is needed because the entrypoint triggers the payload chain.

Evidence

package.jsonindex.js_compat.js/tmp/.analytics_state/var/tmp/.cache_<random>

Network endpoints8

oob-worker.c.f99-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.dev

boxy-devtools-tokens@35.9.9

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code