MalwarePublished 5 Aug 2026

bpm-foundation-testing (npm) · Malicious Code

Affects bpm-foundation-testingSource GCVE Database

Malicious package : remove bpm-foundation-testing and rotate any secrets on hosts that installed it.

Data as of 5 Aug 2026, 15:45 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-12516

What to do

Remove bpm-foundation-testing from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmbpm-foundation-testing	Affected =35.4.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package bpm-foundation-testing version 35.4.3 contains malicious code that fetches and executes obfuscated payloads from external, non-publisher-controlled hosts. The payloads are downloaded via DNS TXT record fallback and HTTP requests, saved to temporary directories with disguised filenames, made executable, and then run detached from the main process. This behavior is implemented in multiple parts of the package, including index.js and lib/telemetry.js, using evasion techniques to avoid static analysis. No integrity checks are performed on the downloaded payloads.

Impact

This malicious package can execute arbitrary code on the host system by downloading and running payloads from attacker-controlled infrastructure without any integrity verification. This can lead to full system compromise, data theft, or further malware deployment. The lack of publisher control over payload hosts and absence of signature verification increases the risk of undetected malicious activity.

Defensive guidance

Users should immediately remove and stop using bpm-foundation-testing version 35.4.3. There is no known official patch or fix available. Avoid installing this package or any versions that include this malicious code. Monitor for any unexpected processes or files created in temporary directories that match the described patterns. Consider using trusted package sources and verifying package integrity before installation.

Summary

The bpm-foundation-testing npm package version 35.4.3 includes malicious code that unconditionally loads a platform-specific module which fetches obfuscated payloads from several external worker hosts and via DNS TXT record lookups from suspicious domains. These payloads are base64 reassembled, saved to temporary directories with disguised filenames, permissioned for execution, and launched detached from the main process using shell commands. The code uses string concatenation and dynamic require calls to evade static detection. There is no verification of the payload integrity or authenticity, and the payload hosts are not controlled by the package publisher. This behavior is present in index.js and also mirrored in lib/telemetry.js under a metrics.node cover story.

References

npmjs.com/package/bpm-foundation-testing/v/35.4.3 (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Aug 2026, 15:45 UTC

Technical details

References

Community reviews