MAL-2026-13023 Malicious code in bnpl-core (npm)
Malicious package
Published
MAL-2026-13023 is a malicious package: bnpl-core (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-13023/ (Markdown: https://insights.sbomify.com/MAL-2026-13023/index.md)
- Package
- bnpl-core
- Registry
- npm
What is MAL-2026-13023?
MAL-2026-13023 is a malicious package in bnpl-core, published on 5 Aug 2026.
Official description
index.js unconditionally requires./setup on load. setup.js constructs Cloudflare Workers hostnames via string-splitting array joins (e.g. oob-worker.cf102-baf.workers.dev, cf100-416, cf99-9b3, cf101-adf under workers.dev) and, if HTTPS fetches fail, retrieves a base64-chunked payload over DNS TXT records under *.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under names masquerading as system tooling (dotnet_diag_<hex>.exe,.cache_<hex>), chmodded 0755 on POSIX, and spawned detached via cmd.exe /c start /b or /bin/sh -c. A TTL lock file at /tmp/.analytics_state throttles re-execution. package.json advertises a 'core runtime' with an empty dependency set and a trivial BnplCore init/version/configure surface as a cover story; DISABLE_TELEMETRY-style env checks reinforce the disguise. The host is anonymous Cloudflare Workers infrastructure with no publisher relationship, the fetch is unpinned and unverified, and the payload is opaque.
What should I do about MAL-2026-13023?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.