boxy-maker-readiness
Reusable boxy maker readiness components
This report shows the evidence for boxy-maker-readiness@35.3.4, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe benign wrapper is a cover for reachable import-time remote payload execution. No install hook is needed because normal use of the declared main entrypoint activates the chain.
Decision evidence
public snapshot- index.js imports _shim.js on every package require.
- _shim.js downloads platform-specific bytes from disguised Workers hosts.
- _shim.js falls back to DNS TXT payload retrieval.
- _shim.js writes payloads under /var/tmp or Windows Temp, chmods them, then launches detached.
- Downloaded payload execution is hidden behind empty-error handlers and a benign wrapper API.
- lib/telemetry.js contains a parallel configurable download-to-execute implementation.
- package.json has no lifecycle scripts.
- Public BoxyMakerReadiness API itself is a minimal wrapper.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_shim.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to boxy-maker-readiness@35.3.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-maker-readiness@35.3.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.