MAL-2026-12890 Malicious code in bnpl-blocks-atom-bnpl-review (npm)
Malicious package
Published
MAL-2026-12890 is a malicious package: bnpl-blocks-atom-bnpl-review (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-12890/ (Markdown: https://insights.sbomify.com/MAL-2026-12890/index.md)
- Package
- bnpl-blocks-atom-bnpl-review
- Registry
- npm
What is MAL-2026-12890?
MAL-2026-12890 is a malicious package in bnpl-blocks-atom-bnpl-review, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads platform.js which fetches a platform-specific binary from Cloudflare Workers subdomains whose hostnames are assembled at runtime from split string fragments (e.g. oob-worker.cf99-9b3.workers.dev, cf103-070/cf101-adf/cf100-416.workers.dev). If HTTPS fetches fail, the module falls back to a DNS TXT-record covert channel under *.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), reading a chunk count from c.<domain> and base64-decoding concatenated TXT records from numbered subdomains. The retrieved bytes are written to /tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. No signature or hash verification is performed and the payload is unrelated to the package's advertised BNPL-review purpose. A second copy of the dropper is bundled in lib/telemetry.js (81 KB) wrapped as an APM SDK, containing matching base64 payload assembly, chmod 0755, and /bin/sh -c spawn primitives; it is not reachable from the main entry in this version but mirrors the same infrastructure.
What should I do about MAL-2026-12890?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.