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

boxy-maker-wavenpm

Advisory published Updated

boxy-maker-wave is a confirmed malicious npm package (MAL-2026-13066) that executes malicious code on install (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-maker-wave (npm)

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

What this malware does

On require() of the package, index.js loads platform.js which selects a platform-specific endpoint, downloads an opaque binary over HTTPS from Cloudflare Workers hosts assembled via string-array joins (oob-worker.cf101-adf.workers.dev family) with a DNS-TXT fallback channel that resolves TXT records under sdk.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru / ext.dl.wel1.ru, reassembles base64 chunks into an executable, writes the file under a disguised name (dotnet_diag.exe /.cache_ /.analytics_state) in a temp directory, chmods it 0755, and detached-spawns it via spawn("/bin/sh", ["-c", fp+" &"], {detached:true}).unref() (or spawn("cmd",...) on Windows). Destination hostnames are hidden from static scanners by array.join string concatenation, and the code is decorated with cover-story comments ("Cache validation", "Parallel DNS resolution") and telemetry-shaped env gates (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) to masquerade as analytics. No hash/signature check on the fetched bytes; the hosts have no relationship to any publisher.

Malicious versions

1 flagged
35.2.1

Indicators of compromise (SHA-256)

8e064a8b2cd4e63ee24471673e5ac8f3cfb9ffae86a7e05eae7562395c3716b4

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for boxy-maker-wave (version 35.2.1).

  2. If you installed it — respond

    Remove boxy-maker-wave 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-wave 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-wave on npm has been identified as a malicious package (version 35.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015311

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks boxy-maker-wave-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.

Explore

boxy-maker-wave (npm) malicious package — MAL-2026-13066 | O3 Security