MAL-2026-13108 Malicious code in bpm-foundation-date-range (npm)
Malicious package
Published
MAL-2026-13108 is a malicious package: bpm-foundation-date-range (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-13108/ (Markdown: https://insights.sbomify.com/MAL-2026-13108/index.md)
- Package
- bpm-foundation-date-range
- Registry
- npm
What is MAL-2026-13108?
MAL-2026-13108 is a malicious package in bpm-foundation-date-range, published on 5 Aug 2026.
Official description
Requiring the package's main entry triggers polyfill.js, which selects a platform-specific endpoint and downloads a native binary over HTTPS from hostnames assembled by Array.join from split string fragments (Cloudflare Workers mirrors such as oob-worker.cf*-*.workers.de). If HTTPS mirrors fail, a covert DNS-TXT retrieval channel keyed by platform (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) reconstructs the binary from base64-chunked TXT records. The downloaded bytes are written to /tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe,.cache_<hex>), chmodded 0755 on POSIX, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start. No hash or signature is verified, the payload host is not the package publisher, and the package's advertised purpose (a date-range utility) has no legitimate need to fetch or run a native binary.
What should I do about MAL-2026-13108?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.