MAL-2026-13007 Malicious code in bnpl-blocks-mobile-bnpl-tab-buttons (npm)
Malicious package
Published
MAL-2026-13007 is a malicious package: bnpl-blocks-mobile-bnpl-tab-buttons (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-13007/ (Markdown: https://insights.sbomify.com/MAL-2026-13007/index.md)
- Package
- bnpl-blocks-mobile-bnpl-tab-buttons
- Registry
- npm
What is MAL-2026-13007?
MAL-2026-13007 is a malicious package in bnpl-blocks-mobile-bnpl-tab-buttons, published on 5 Aug 2026.
Official description
On require() of the package, index.js side-loads adapter.js which selects a platform-specific asset, downloads bytes over HTTPS from hostnames reconstructed at runtime by joining split string fragments (oob-worker.cf10{0..3}-*.workers.dev), writes the bytes to a disguised temp file (/tmp/.cache<hex> on POSIX, %TEMP%/dotnet_diag_<hex>.exe on Windows), sets mode 0o755, and spawns the file detached via /bin/sh -c or cmd.exe /c start. A DNS-TXT fallback channel queries c.<domain> then N.<domain> records under *.dl.wel1.ru, base64-decodes the concatenated chunks, and executes the resulting binary when the HTTPS mirrors fail. The package advertises itself as a native bridge with a trivial no-op class in index.js; the dropper logic is hidden in _adapter.js with cover-story variable names (analytics_state, telemetry). Hostname reconstruction from split literals is a deliberate static-scanner evasion technique, and DNS-TXT payload staging is a covert-channel technique to bypass HTTPS egress filtering.
What should I do about MAL-2026-13007?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.