Which versions of boxy-maker-readiness are malicious?

The following npm versions of boxy-maker-readiness are flagged malicious: 35.3.4. Treat any of these as compromised.

How do I remediate boxy-maker-readiness if I installed it?

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.

I already installed boxy-maker-readiness — how do I know if it already compromised me?

If boxy-maker-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.

Is boxy-maker-readiness part of a known attack campaign?

Yes — boxy-maker-readiness is associated with the IN-MAL-2026-015324 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find boxy-maker-readiness across my projects, lockfiles, and CI pipelines?

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

Malicious package

boxy-maker-readinessnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-13062

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall boxy-maker-readiness

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

1 flagged

35.3.4

Indicators of compromise (SHA-256)

47b6eaa6662082b79fce51e2ed8c152fa566d22ecb3b27311bbea6b069f25b14

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for boxy-maker-readiness (version 35.3.4).
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 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-readiness on npm has been identified as a malicious package (version 35.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015324

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database