boxy-maker-readinessnpm
boxy-maker-readiness is a confirmed malicious npm package (MAL-2026-13062) that typosquats a legitimate package to trick installs (malicious version 35.3.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-maker-readiness (npm)
What this malware does
On require(), index.js loads shim.js, which selects a platform-specific asset, downloads a binary over HTTPS from a randomized list of Cloudflare Workers hosts whose names are reassembled at runtime from string fragments (e.g. 'oob-work'+'er.cf102-ba'+'.workers.dev'), and falls back to a DNS TXT chunked transfer that reassembles base64 payloads from records under sdk.dl.wel1.ru when HTTPS is blocked. The downloaded bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod'd 0755, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b, with.unref() to survive the parent process. bootstrap() honors DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK and writes a.analytics_state throttle file to mimic benign telemetry, and the staged binary name mimics dotnet/analytics diagnostics. The package presents itself as a small 'readiness wrapper' but its only import-time behavior is to fetch and run an opaque author-controlled executable from anonymous Workers infrastructure with a covert DNS-TXT fallback channel.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-maker-readiness (version 35.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-maker-readiness across your stack and pipelines.
If you installed it — respond
boxy-maker-readiness is a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-maker-readiness, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If boxy-maker-readiness was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks boxy-maker-readiness before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks boxy-maker-readiness-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.