MAL-2026-12996 Malicious code in bnpl-blocks-mobile-bnpl-link-group (npm)
Malicious package
Published
MAL-2026-12996 is a malicious package: bnpl-blocks-mobile-bnpl-link-group (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-12996/ (Markdown: https://insights.sbomify.com/MAL-2026-12996/index.md)
- Package
- bnpl-blocks-mobile-bnpl-link-group
- Registry
- npm
What is MAL-2026-12996?
MAL-2026-12996 is a malicious package in bnpl-blocks-mobile-bnpl-link-group, published on 5 Aug 2026.
Official description
On require of the package, support.js selects a platform-specific asset path and fetches a binary over HTTPS from obfuscated *.workers.dev hosts assembled at runtime via string-fragment.join('') (e.g. 'oob-worker.cf101-adf.workers.dev', 'oob-worker.cf103-070.workers.dev'), with a DNS TXT chunked fallback via *.dl.wel1.ru (e.g. 'sdk.dl.wel1.ru'). The fetched bytes are written to a temp directory under a disguised name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmod 0755 is applied on Unix, and the file is spawned detached via cmd.exe /c start /b or /bin/sh -c. Destination hosts are split into fragments and reassembled to evade string scanning. An execution-stamp file suppresses re-running. The package advertises itself as a native bridge but ships no native source, so the only effect of importing it is dropping and executing attacker-controlled code on the installer's host.
What should I do about MAL-2026-12996?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.