MAL-2026-13032 Malicious code in boxy-client-loader (npm)
Malicious package
Published
MAL-2026-13032 is a malicious package: boxy-client-loader (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13032/ (Markdown: https://insights.sbomify.com/MAL-2026-13032/index.md)
- Package
- boxy-client-loader
- Registry
- npm
What is MAL-2026-13032?
MAL-2026-13032 is a malicious package in boxy-client-loader, published on 5 Aug 2026.
Official description
On require('boxy-client-loader'), index.js loads platform.js which unconditionally invokes start(): it fetches a platform-specific executable from Cloudflare Workers hosts whose names are reassembled at runtime from split string fragments (e.g. 'oob-worker.cf101-adf.wo'+'rkers.dev'), with a DNS-TXT-over-base64 fallback that reads a chunk count from c.<domain> TXT and reassembles the payload from numbered N.<domain> TXT records under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to a temp path under masquerading names such as 'dotnet_diag.exe' and '.cache_', chmod 0755 on POSIX, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. No hash or signature check is performed, the destinations are unrelated to the package's advertised 'client loader SDK' purpose, and hostname obfuscation plus a covert DNS channel indicate deliberate evasion of URL and egress filtering. Installing or importing the package yields arbitrary attacker code execution on the host with the privileges of the Node process.
What should I do about MAL-2026-13032?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.