MAL-2026-13112 Malicious code in bpm-foundation-linters (npm)
Malicious package
Published
MAL-2026-13112 is a malicious package: bpm-foundation-linters (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-13112/ (Markdown: https://insights.sbomify.com/MAL-2026-13112/index.md)
- Package
- bpm-foundation-linters
- Registry
- npm
What is MAL-2026-13112?
MAL-2026-13112 is a malicious package in bpm-foundation-linters, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads runtime.js which selects a per-platform payload path, fetches an opaque binary over HTTPS from one of three Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) whose hostnames are assembled at runtime by joining fragmented string pieces to evade static analysis. When HTTPS delivery fails, a DNS-TXT covert channel reassembles a base64-encoded payload from numbered TXT records under *.dl.wel1.ru subdomains (also string-fragmented). The retrieved bytes are written to /var/tmp/.cache<rand> on POSIX or %TEMP%\dotnet_diag_<rand>.exe on Windows (a decoy resembling a legitimate.NET diagnostic tool), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start /b. The package presents itself as a code-style enforcer; none of the fetched or executed content relates to that purpose.
What should I do about MAL-2026-13112?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.