What does the bpm-ng-security malware do?

On require('bpm-ng-security'), index.js loads _bridge.js whose top-level bootstrap fetches a platform-specific binary from anonymous Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, cf99-9b3, cf101-adf, cf102-baf) with a DNS TXT covert-channel fallback under dl.wel1.ru, writes it to /tmp/.cache_ or %TEMP%\dotnet_diag_ .exe, chmods 0755, and spawns it detached via /bin/sh -c or cmd. Destination hostnames are reconstructed at runtime from string-split arrays joined with '' to evade static extraction, and a DNS TXT routine reassembles a base64 payload from numbered TXT records as a fallback delivery channel. The package is advertised as a security interface library; t

Which versions of bpm-ng-security are malicious?

The following npm versions of bpm-ng-security are flagged malicious: 35.8.7. Treat any of these as compromised.

How do I remediate bpm-ng-security if I installed it?

Remove bpm-ng-security from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed bpm-ng-security — how do I know if it already compromised me?

If bpm-ng-security was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is bpm-ng-security part of a known attack campaign?

Yes — bpm-ng-security is associated with the IN-MAL-2026-015257 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bpm-ng-security across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-ng-security (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-ng-security across your stack and pipelines.

Malicious package

bpm-ng-securitynpm

bpm-ng-security is a confirmed malicious npm package (MAL-2026-13122) that executes malicious code on install (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-ng-security (npm)

MAL-2026-13122

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bpm-ng-security

What this malware does

On require('bpm-ng-security'), index.js loads bridge.js whose top-level bootstrap fetches a platform-specific binary from anonymous Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, cf99-9b3, cf101-adf, cf102-baf) with a DNS TXT covert-channel fallback under dl.wel1.ru, writes it to /tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmods 0755, and spawns it detached via /bin/sh -c or cmd. Destination hostnames are reconstructed at runtime from string-split arrays joined with '' to evade static extraction, and a DNS TXT routine reassembles a base64 payload from numbered TXT records as a fallback delivery channel. The package is advertised as a security interface library; the fetched binary is opaque and unrelated to that purpose.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

959e08ecff1873b99af8a10419ff5417e716d582ba50e870f0e636d0ba523312

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-ng-security (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-ng-security across your stack and pipelines.
If you installed it — respond
Remove bpm-ng-security from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bpm-ng-security was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bpm-ng-security before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. bpm-ng-security on npm has been identified as a malicious package (version 35.8.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015257

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bpm-ng-security-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database