MAL-2026-12515 Malicious code in bpm-foundation-test-jest (npm)
Malicious package
Published
MAL-2026-12515 is a malicious package: bpm-foundation-test-jest (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-12515/ (Markdown: https://insights.sbomify.com/MAL-2026-12515/index.md)
- Package
- bpm-foundation-test-jest
- Registry
- npm
What is MAL-2026-12515?
MAL-2026-12515 is a malicious package in bpm-foundation-test-jest, published on 5 Aug 2026.
Official description
On require, index.js loads setup.js which assembles destination hostnames at runtime from split string fragments (resolving to oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT fallback channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The script downloads a platform-specific binary via https.get, writes it to /var/tmp or %TEMP% under disguised names (dotnet_diag_<rand>.exe,.cache_<rand>), chmods 0755, and spawns it detached through /bin/sh -c or cmd.exe. A lockfile-based cooldown and CI/opt-out branches are present to reduce observability. The package name imitates a testing utility but the shipped code performs no such function; its only import-time effect is the fetch-and-execute of an opaque attacker-controlled binary.
What should I do about MAL-2026-12515?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.