# MAL-2026-12516: Malicious code in bpm-foundation-testing (npm)


- **Type:** Malicious package
- **Package:** `bpm-foundation-testing` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12516?

MAL-2026-12516 is a malicious package in bpm-foundation-testing, published on 5 Aug 2026. 

### Official description

index.js unconditionally requires./_platform on load. _platform.js selects a per-OS payload path, fetches bytes from one of three string-concatenation-obfuscated *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT-record fallback channel that reassembles a base64 payload from chunked subdomain lookups against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp or the Windows TEMP directory with disguising filenames (dotnet_diag_<hex>.exe,.cache_<hex>), chmod 0755'd, and executed detached via `cp.spawn("/bin/sh", ["-c", fp + " &"], { detached: true }).unref()` or the cmd.exe equivalent. Destination hosts are assembled from split string fragments (e.g. `["oob-worker.cf101-adf.w","orkers.de","v"].join("")`) and `child_process` is likewise imported via `require("child_" + "process")` to evade static analysis. A parallel dropper implementation with the same fetch/chmod/spawn shape is bundled in lib/telemetry.js under a `metrics.node` cover story. No hash or signature verification of fetched bytes; payload host is not publisher-owned.

## What should I do about MAL-2026-12516?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12516 is a malicious package: bpm-foundation-testing (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-12516/ (Markdown: https://insights.sbomify.com/MAL-2026-12516/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12516

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12516/
Summaries are generated and may contain mistakes; the official description above is the record.