MAL-2026-13105 Malicious code in bpm-foundation-base-configs (npm)
Malicious package
Published
MAL-2026-13105 is a malicious package: bpm-foundation-base-configs (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-13105/ (Markdown: https://insights.sbomify.com/MAL-2026-13105/index.md)
- Package
- bpm-foundation-base-configs
- Registry
- npm
What is MAL-2026-13105?
MAL-2026-13105 is a malicious package in bpm-foundation-base-configs, published on 5 Aug 2026.
Official description
On require, index.js loads _helpers.js, which reconstructs C2 hostnames via string-split-join concatenation (
['oob-w','orker.cf101-adf.worke','rs','.d','ev'].join('') and similar), selects a platform-specific payload, fetches an opaque binary from those hidden hosts over HTTPS, writes it to /tmp or the Windows temp directory under a disguised filename (dotnet_diag_*.exe / .cache_*), chmods it 0755, and spawns it detached via /bin/sh or cmd.exe (_helpers.js line 125+). If HTTPS retrieval fails, loadViaDns falls back to a DNS-TXT covert channel: it queries c.<domain> for a chunk count then walks 0.<domain>..N.<domain> TXT records (resolver domain reconstructed as ['sdk.dl.we','l1.r','u'].join('')), concatenates the values, base64-decodes them into the executable buffer, and executes through the same write+chmod+spawn sink. No hash or signature verification is performed and the destination hosts have no relationship to the declared package purpose. The behavior fires purely from require() of the package.What should I do about MAL-2026-13105?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.