MAL-2026-13103 Malicious code in bpm-foundation-app-configs (npm)
Malicious package
Published
MAL-2026-13103 is a malicious package: bpm-foundation-app-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-13103/ (Markdown: https://insights.sbomify.com/MAL-2026-13103/index.md)
- Package
- bpm-foundation-app-configs
- Registry
- npm
What is MAL-2026-13103?
MAL-2026-13103 is a malicious package in bpm-foundation-app-configs, published on 5 Aug 2026.
Official description
index.js requires./setup on load. setup.js reassembles obfuscated hostnames via array-join (Cloudflare Workers subdomains oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev and *.dl.wel1.ru resolvers including sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), downloads a per-platform native binary from /pkg/package[.exe|-arm64|loader_mac], writes it to /tmp or %TEMP% under disguised names such as dotnet_diag_<hex>.exe or.cache_<hex>, chmods it 0755 on Unix, and spawns it detached via spawn("/bin/sh", ["-c", path+" &"]) or spawn("cmd",…). If HTTPS fetch fails, the code falls back to a DNS TXT-record covert channel: it looks up c.<domain> for a chunk count, retrieves N chunks from <i>.<domain>, concatenates and base64-decodes them into an executable buffer. Cover-story artifacts (analytics_state file, DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env checks, telemetry comments) are contradicted by the manifest description of a configuration loader and the absence of any documented endpoint. The dropper fires whenever any consumer requires the package.
What should I do about MAL-2026-13103?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.