Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-ai-assistantnpm

bpm-foundation-ai-assistant is a confirmed malicious npm package (MAL-2026-13100) that executes malicious code on install (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-ai-assistant (npm)

MAL-2026-13100
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bpm-foundation-ai-assistant

What this malware does

index.js unconditionally requires./loader on package load. loader.js assembles Cloudflare Workers hostnames from string-array joins (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT fallback to *.dl.wel1.ru, downloads a platform-specific binary via https.get, writes it to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag<hex>.exe, chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. Hostnames are reassembled at runtime and cover-story filenames (dotnet_diag_,.cache_,.analytics_state) are used to blend with system paths. A parallel dropper module in lib/telemetry.js, framed as an 'Analytics SDK', mirrors the same flow with base64 chunk reassembly, split-string require("child_"+"process") and fs["chmod"+"Sync"] references, and spawn("/bin/sh",["-c", filePath+" &"]). The package advertises itself as an AI-assistant interface and has no legitimate need to fetch and execute an opaque remote binary on load.

Malicious versions

1 flagged
35.6.2

Indicators of compromise (SHA-256)

13f246c1580a9d0a9035c63c1781c411db9cae7a812f175f6b7ad18a3f2336aa

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove bpm-foundation-ai-assistant 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.

  3. Did it already run?

    If bpm-foundation-ai-assistant 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.

  4. How O3 protects you

    O3 blocks bpm-foundation-ai-assistant 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-ai-assistant on npm has been identified as a malicious package (version 35.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015283

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-ai-assistant-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
bpm-foundation-ai-assistant (npm) malicious package — MAL-2026-13100 | O3 Security