MAL-2026-12969 Malicious code in bnpl-blocks-independent-bnpl-separator (npm)
Malicious package
Published
MAL-2026-12969 is a malicious package: bnpl-blocks-independent-bnpl-separator (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-12969/ (Markdown: https://insights.sbomify.com/MAL-2026-12969/index.md)
- Package
- bnpl-blocks-independent-bnpl-separator
- Registry
- npm
What is MAL-2026-12969?
MAL-2026-12969 is a malicious package in bnpl-blocks-independent-bnpl-separator, published on 5 Aug 2026.
Official description
Requiring this package triggers init.js, which selects a platform-specific payload URL from string-concat-obfuscated Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT base64 reassembly fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /tmp or the Windows temp directory under disguised names such as dotnet_diag.exe and.cache_, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Cover-story naming (
.analytics_state run-once marker, DISABLE_TELEMETRY/DO_NOT_TRACK env checks) frames the behavior as analytics. A secondary dropper with the same fetch/writeFile/chmod/spawn shape ships in lib/telemetry.js, using base64-decoded payload chunks and split-string require('child_'+'process'). The destinations are non-publisher infrastructure, the payload bytes are opaque, and hostnames plus module names are assembled at runtime to evade static review.What should I do about MAL-2026-12969?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.