Which versions of bnpl-blocks-block are malicious?

The following npm versions of bnpl-blocks-block are flagged malicious: 35.8.9. Treat any of these as compromised.

How do I remediate bnpl-blocks-block if I installed it?

Remove bnpl-blocks-block 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 bnpl-blocks-block — how do I know if it already compromised me?

If bnpl-blocks-block 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 bnpl-blocks-block part of a known attack campaign?

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

Malicious package

bnpl-blocks-blocknpm

bnpl-blocks-block is a confirmed malicious npm package (MAL-2026-12906) that executes malicious code on install (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-block (npm)

MAL-2026-12906

Immediate action

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

npm uninstall bnpl-blocks-block

What this malware does

On require of the package, index.js loads./compat.js which selects a platform-specific asset and downloads a binary from split-string-obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS-TXT covert-channel fallback under *.wel1.ru that reads a chunk count from c.<domain> and base64-reassembles the payload from numbered TXT records. The fetched bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> / dotnet_diag_<hex>.exe), chmod 0755, then executed detached via /bin/sh -c "<path> &" on POSIX or cmd.exe /c start on Windows. The package's public API (class BnplBlocksBlock with init/version/configure) is a hollow shell with no real implementation; the sole effect of installing or importing this package is running the remotely fetched binary on the installer's host.

Malicious versions

1 flagged

35.8.9

Indicators of compromise (SHA-256)

6112720c2d716ce25da42abf8ddd7ec3e27614102f343c283160f28d8b039ef7

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

Campaign

IN-MAL-2026-015474

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-block-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