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.

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.

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.