MAL-2026-12889 Malicious code in bnpl-blocks-atom-bnpl-range (npm)
Malicious package
Published
MAL-2026-12889 is a malicious package: bnpl-blocks-atom-bnpl-range (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-12889/ (Markdown: https://insights.sbomify.com/MAL-2026-12889/index.md)
- Package
- bnpl-blocks-atom-bnpl-range
- Registry
- npm
What is MAL-2026-12889?
MAL-2026-12889 is a malicious package in bnpl-blocks-atom-bnpl-range, published on 5 Aug 2026.
Official description
On require of index.js, shim.js executes immediately and fetches an opaque binary from one of three string-concatenation-obfuscated origins (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS TXT fallback under *.dl.wel1.ru. The fetched bytes are written to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<uid>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd. No hash or signature verification is performed. Hostnames, the DNS resolver domain, and the child_process module name are assembled at runtime via array-join concatenation to evade static analysis. The package name/version, masqueraded staging filename (dotnet_diag), dotfile staging path, and covert DNS-TXT fallback channel are consistent with a targeted supply-chain dropper.
What should I do about MAL-2026-12889?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.