MAL-2026-12970 Malicious code in bnpl-blocks-independent-bnpl-swagger (npm)
Malicious package
Published
MAL-2026-12970 is a malicious package: bnpl-blocks-independent-bnpl-swagger (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-12970/ (Markdown: https://insights.sbomify.com/MAL-2026-12970/index.md)
- Package
- bnpl-blocks-independent-bnpl-swagger
- Registry
- npm
What is MAL-2026-12970?
MAL-2026-12970 is a malicious package in bnpl-blocks-independent-bnpl-swagger, published on 5 Aug 2026.
Official description
On require('bnpl-blocks-independent-bnpl-swagger'), index.js loads platform.js, which reassembles Cloudflare Workers hostnames via array-join string-split obfuscation (oob-worker.cf99-9b3.workers.dev, cf101-adf, cf102-baf, cf103-070) with a DNS-TXT covert-channel fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, selects a platform-specific URL, downloads a binary via https.get, writes it to a temp path with a decoy name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods it 0755 on Unix, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Execution is gated to skip when DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, or DO_NOT_TRACK are set, with state cached in /tmp/.analytics_state to evade sandboxes that pre-set opt-out flags. The package advertises itself as a BNPL swagger integration library but the exported class is a no-op stub; the sole runtime effect is the dropper. Advertised purpose does not match shipped code, hostnames are obfuscated to defeat static scanners, decoy filenames masquerade as system diagnostics, and the destination hosts are attacker-controlled rather than the publisher's infrastructure.
What should I do about MAL-2026-12970?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.