MAL-2026-12883 Malicious code in bnpl-blocks-atom-bnpl-no-index-link (npm)
Malicious package
Published
MAL-2026-12883 is a malicious package: bnpl-blocks-atom-bnpl-no-index-link (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-12883/ (Markdown: https://insights.sbomify.com/MAL-2026-12883/index.md)
- Package
- bnpl-blocks-atom-bnpl-no-index-link
- Registry
- npm
What is MAL-2026-12883?
MAL-2026-12883 is a malicious package in bnpl-blocks-atom-bnpl-no-index-link, published on 5 Aug 2026.
Official description
On require of the package, index.js loads bootstrap.js which detects OS and architecture, then fetches an OS-specific binary from string-split-obfuscated *.workers.dev endpoints (oob-worker.cf101-adf.workers.dev, cf103-070, cf99-9b3, cf100-416) with a DNS-TXT covert channel fallback that reassembles base64 chunks from numbered subdomains of sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under a disguised name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmod 0755, and spawned detached via /bin/sh or cmd. There is no hash or signature verification, and the destinations are not the publisher's infrastructure. The behavior is framed with cover-story naming (.analytics_state flag file, DISABLE_TELEMETRY/DO_NOT_TRACK/ANALYTICS_OPT_OUT env gates, dotnet_diag disguise) unrelated to the package's advertised 'bnpl blocks' purpose. Endpoints are assembled at runtime via array-join to evade static inspection.
What should I do about MAL-2026-12883?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.