boxy-maker-page-readinessnpm
boxy-maker-page-readiness is a confirmed malicious npm package (MAL-2026-13061) that executes malicious code on install (malicious version 35.7.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-maker-page-readiness (npm)
What this malware does
index.js unconditionally requires bootstrap.js on module load. bootstrap.js reassembles hostnames from split-string arrays (e.g. ['oo','b-worker.cf101-adf.worke','rs.','de','v'].join('') and ['sdk.dl.','we','l1.','ru'].join('')) to resolve to *.workers.dev and *.dl.wel1.ru endpoints. It selects a platform-specific payload path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), fetches the binary over HTTPS, writes it to a temp path under decoy names (dotnet_diag*.exe,.cache*,.analytics_state), chmods 0755, and spawns it detached via spawn("/bin/sh") or spawn("cmd"). A base64-over-DNS-TXT fallback channel (resolveTxt of c.<domain> and <i>.<domain> reassembled and base64-decoded) provides an alternate retrieval path when HTTPS fetch fails. The fetched executable is unpinned and unverified, obtained from hosts unrelated to the package's stated readiness-interface purpose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-maker-page-readiness (version 35.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-maker-page-readiness across your stack and pipelines.
If you installed it — respond
Remove boxy-maker-page-readiness from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If boxy-maker-page-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-page-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-page-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.