MAL-2026-12904 Malicious code in bnpl-blocks-atom-icon-loader (npm)
Malicious package
Published
MAL-2026-12904 is a malicious package: bnpl-blocks-atom-icon-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-12904/ (Markdown: https://insights.sbomify.com/MAL-2026-12904/index.md)
- Package
- bnpl-blocks-atom-icon-loader
- Registry
- npm
What is MAL-2026-12904?
MAL-2026-12904 is a malicious package in bnpl-blocks-atom-icon-loader, published on 5 Aug 2026.
Official description
On require of the package, index.js unconditionally loads compat.js, which selects a platform-specific output path (Linux/Darwin: /tmp/.cache<rand>; Windows: TEMP/dotnet_diag_<rand>.exe), downloads an opaque binary via https.get from one of several Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), writes it to disk, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. Destination hostnames are assembled at runtime by joining split string fragments (e.g. ['oob','-worker.cf99-9b3.workers.dev'].join(''); ['sdk.dl.w','el','1.r','u'].join('')) to evade static URL scanning, and a DNS-TXT chunked base64 fallback channel targets sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. Cover-story comments referencing SHA-256 integrity checks, CI skipping, and exponential backoff appear in code that implements none of that logic. The dropped Windows artifact is named dotnet_diag_<rand>.exe to masquerade as a Microsoft diagnostic tool. No signature verification, no pinning, no publisher-matching source.
What should I do about MAL-2026-12904?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.