NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

boxy-maker-page-readinessnpm

Advisory published Updated

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)

MAL-2026-13061
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall boxy-maker-page-readiness

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

1 flagged
35.7.8

Indicators of compromise (SHA-256)

273f130823f6759922a2e1d6f7c58ba24b9df17f7c08c6f6e43b0818b5aad4ed

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for boxy-maker-page-readiness (version 35.7.8).

  2. 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.

  3. Did it already run?

    If boxy-maker-page-readiness was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. boxy-maker-page-readiness on npm has been identified as a malicious package (version 35.7.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015330

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
boxy-maker-page-readiness (npm) malicious package — MAL-2026-13061 | O3 Security