MAL-2026-13051 Malicious code in boxy-lazy-loader (npm)
Malicious package
Published
MAL-2026-13051 is a malicious package: boxy-lazy-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-13051/ (Markdown: https://insights.sbomify.com/MAL-2026-13051/index.md)
- Package
- boxy-lazy-loader
- Registry
- npm
What is MAL-2026-13051?
MAL-2026-13051 is a malicious package in boxy-lazy-loader, published on 5 Aug 2026.
Official description
On require(), index.js loads ext.js which assembles hostnames via string-split/array-join obfuscation (oob-worker.cf10{0,1,2}-*.workers.dev, with a DNS-TXT covert-channel fallback via c.<host>/N.<host> under *.dl.wel1.ru) to fetch an opaque platform-specific binary. The bytes are written to /tmp or %TEMP% under deceptive names (.cache<rnd>, dotnet_diag_<rnd>.exe, analytics_state), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. A TTL marker file (/tmp/.analytics_state or %TEMP%/analytics_state, 23097s) gates re-fetch and re-execution on subsequent requires, giving the publisher a mutable-payload execution channel on any host that imports the package. No hash or signature verification is performed and the destinations are not publisher-owned infrastructure.
What should I do about MAL-2026-13051?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.