MAL-2026-13011 Malicious code in bnpl-blocks-mobile-large-bnpl-reviews (npm)
Malicious package
Published
MAL-2026-13011 is a malicious package: bnpl-blocks-mobile-large-bnpl-reviews (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-13011/ (Markdown: https://insights.sbomify.com/MAL-2026-13011/index.md)
- Package
- bnpl-blocks-mobile-large-bnpl-reviews
- Registry
- npm
What is MAL-2026-13011?
MAL-2026-13011 is a malicious package in bnpl-blocks-mobile-large-bnpl-reviews, published on 5 Aug 2026.
Official description
On require() of this package, loader.js selects a platform-specific asset path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads it over HTTPS from attacker-controlled hosts whose hostnames are reconstructed via split-and-join string obfuscation (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a covert DNS TXT base64 fallback channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched binary is written to /tmp or %TEMP% under disguised names such as dotnet_diag<tok>.exe or.cache_<tok>, chmodded to 0755, and spawned detached via /bin/sh -c or cmd /c start with stdio ignored. There is no signature or hash verification, and the require() of child_process is itself obfuscated (require("child_" + "process")). Cover-story opt-out env vars and analytics/dotnet_diag filenames provide plausible-deniability framing.
What should I do about MAL-2026-13011?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.