Which versions of bpm-foundation-linters are malicious?

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

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

Remove bpm-foundation-linters 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-foundation-linters — how do I know if it already compromised me?

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

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

Malicious package

bpm-foundation-lintersnpm

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

Malicious code in bpm-foundation-linters (npm)

MAL-2026-13112

Immediate action

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

npm uninstall bpm-foundation-linters

What this malware does

On require() of the package, index.js loads runtime.js which selects a per-platform payload path, fetches an opaque binary over HTTPS from one of three Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) whose hostnames are assembled at runtime by joining fragmented string pieces to evade static analysis. When HTTPS delivery fails, a DNS-TXT covert channel reassembles a base64-encoded payload from numbered TXT records under *.dl.wel1.ru subdomains (also string-fragmented). The retrieved bytes are written to /var/tmp/.cache<rand> on POSIX or %TEMP%\dotnet_diag_<rand>.exe on Windows (a decoy resembling a legitimate.NET diagnostic tool), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start /b. The package presents itself as a code-style enforcer; none of the fetched or executed content relates to that purpose.

Malicious versions

1 flagged

35.3.9

Indicators of compromise (SHA-256)

b7753fe48a070f467d11a5dfef041b6919ff9914df1484d0ef0e59c95f583961

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-foundation-linters (version 35.3.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-linters across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-linters 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-foundation-linters 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-linters 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-linters on npm has been identified as a malicious package (version 35.3.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015266

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-linters-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