Which versions of bpm-foundation-feedback are malicious?

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

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

bpm-foundation-feedback is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — bpm-foundation-feedback is associated with the IN-MAL-2026-015269 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-feedback 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-feedback (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-feedback across your stack and pipelines.

Malicious package

bpm-foundation-feedbacknpm

bpm-foundation-feedback is a confirmed malicious npm package (MAL-2026-13110) that steals credentials and exfiltrates sensitive data (malicious version 35.8.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-feedback (npm)

MAL-2026-13110

Immediate action

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

npm uninstall bpm-foundation-feedback

What this malware does

On require() of the package, adapter.js runs a setup() routine that detects the host OS and architecture, reconstructs Cloudflare Workers hostnames from split string arrays (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS TXT chunked fallback against *.dl.wel1.ru, fetches a platform-specific binary via https.get to /pkg/package..., writes it to /var/tmp or %TEMP% under a disguised name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods 0755, and spawns it detached and unref'd via cp.spawn('/bin/sh', ['-c', fp+' &']) or the Windows cmd equivalent. There is no version pinning, no hash or signature verification, and the fetched binary is unrelated to the package's stated 'persistence adapter' purpose. Destination hostnames are assembled at runtime from split string arrays to hide the literal C2 domains, and TELEMETRY opt-out environment variables are referenced as cover. index.js require('./_adapter') causes this to fire for any consumer of the package.

Malicious versions

1 flagged

35.8.8

Indicators of compromise (SHA-256)

a2628bc930d903e5a69d6827559867687193357682be11a6caed59a65941caaf

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-feedback (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-feedback across your stack and pipelines.
If you installed it — respond
bpm-foundation-feedback is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bpm-foundation-feedback 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-feedback 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-feedback on npm has been identified as a malicious package (version 35.8.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015269

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database