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

boxy-maker-busnpm

Advisory published Updated

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

Malicious code in boxy-maker-bus (npm)

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

What this malware does

[email protected] acts as a load-time dropper. The package's index.js unconditionally requires compat.js on load, which assembles Cloudflare Workers hostnames (oob-worker.cf99-9b3/cf100-416/cf101-adf.workers.dev) and a wel1.ru-based DNS covert channel from split string fragments, downloads a platform-specific opaque binary over HTTPS with no hash or signature verification, writes it to a disguised path (dotnet_diag<token>.exe on Windows,.cache_<token> on POSIX) under /tmp or %TEMP%, chmods 0755, and spawns it detached via cmd.exe /c start /b or /bin/sh -c. A secondary delivery path enumerates DNS TXT records at c.<domain> and <i>.<domain>, concatenates the chunks, and base64-decodes them into the executable payload. The dropper is wrapped in cover-story naming (analytics_state stamp file, DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env gates, an unused lib/telemetry.js labeled 'Analytics SDK', dotnet_diag filename) that does not correspond to the package's stated 'runtime support module' purpose. The delivered bytes are attacker-controlled and unverified, giving whoever controls the workers.dev and wel1.ru infrastructure arbitrary code execution on any host that installs or imports the package.

Malicious versions

1 flagged
35.7.7

Indicators of compromise (SHA-256)

b8e609c87c0dbbf2a870faf3c1e8ea2b322b32d147974f4ec62c400fd026744a

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for boxy-maker-bus (version 35.7.7).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015319

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks boxy-maker-bus-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-bus (npm) malicious package — MAL-2026-13058 | O3 Security