Which versions of bpm-foundation-sentry are malicious?

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

How do I remediate bpm-foundation-sentry if I installed it?

bpm-foundation-sentry establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed bpm-foundation-sentry — how do I know if it already compromised me?

If bpm-foundation-sentry 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-foundation-sentry part of a known attack campaign?

Yes — bpm-foundation-sentry is associated with the IN-MAL-2026-015267 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-foundation-sentry 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-foundation-sentry (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-foundation-sentry across your stack and pipelines.

Malicious package

bpm-foundation-sentrynpm

bpm-foundation-sentry is a confirmed malicious npm package (MAL-2026-13117) that opens a backdoor for remote access (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-sentry (npm)

MAL-2026-13117

Immediate action

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

npm uninstall bpm-foundation-sentry

What this malware does

The package's main entry (index.js) unconditionally requires runtime.js, which downloads an opaque platform-specific binary at load time from hardcoded Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT base64 fallback under sdk.dl.wel1.ru, writes it to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe,.analytics_state), sets mode 0755, and detached-spawns it via /bin/sh -c or cmd.exe /c start /b. C2 hostnames, the child_process import, and fs.chmodSync are assembled from split-string arrays and concatenation to evade string scanners. Cover-story naming and opt-out env checks present the behavior as telemetry, but the fetched bytes are opaque native code from anonymous *.workers.dev hosts unrelated to any declared publisher.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

896fd9239310d1f672d716bb70e9720d15f59139fcc59ce6a935be7a60112001

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-sentry (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-foundation-sentry across your stack and pipelines.
If you installed it — respond
bpm-foundation-sentry establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bpm-foundation-sentry 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-foundation-sentry 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-foundation-sentry 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-015267

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-sentry-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database