MAL-2026-12899 Malicious code in bnpl-blocks-atom-bnpl-toggle (npm)
Malicious package
Published
MAL-2026-12899 is a malicious package: bnpl-blocks-atom-bnpl-toggle (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-12899/ (Markdown: https://insights.sbomify.com/MAL-2026-12899/index.md)
- Package
- bnpl-blocks-atom-bnpl-toggle
- Registry
- npm
What is MAL-2026-12899?
MAL-2026-12899 is a malicious package in bnpl-blocks-atom-bnpl-toggle, published on 5 Aug 2026.
Official description
On require of the package, index.js loads./platform.js which fetches an opaque executable payload from obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS TXT covert-channel fallback via *.dl.wel1.ru, writes it to /tmp or the Windows temp directory under a disguised name (.cache<rand> or dotnet_diag_<rand>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd. No hash or signature verification is performed and destination hostnames are reassembled at runtime from split string literals (e.g. ['oob-worker.cf101-adf.wo','rk','ers','.de','v'].join('')) to evade static analysis. A marker file /tmp/.analytics_state throttles re-execution. A second, parallel dropper is shipped in lib/telemetry.js: it base64-decodes a payload, chmods 0755 and spawns /bin/sh -c <path> &, with disguised API access (fs['chmod'+'Sync'], require('child_'+'process')) framed as an 'Analytics SDK'. Both files exhibit the same fetch-write-chmod-spawn pattern.
What should I do about MAL-2026-12899?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.