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

bnpl-blocks-desktop-large-bnpl-reviewsnpm

bnpl-blocks-desktop-large-bnpl-reviews is a confirmed malicious npm package (MAL-2026-12946) that executes malicious code on install (malicious version 35.8.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-desktop-large-bnpl-reviews (npm)

MAL-2026-12946
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-desktop-large-bnpl-reviews

What this malware does

On require() of the package, index.js loads bridge.js which detects OS/arch and downloads a platform-specific binary from Cloudflare Workers hosts whose names are reconstructed at runtime by joining split string arrays (e.g. 'oob-wo'+'rker.cf103-070'+'.workers.de'+'v'). If HTTPS mirrors fail, a DNS-TXT covert channel against hosts like sdk.dl.wel1.ru reassembles a base64 payload from a count record plus indexed TXT chunks. The fetched bytes are written to a masquerading path in /var/tmp or %TEMP% (.cache<hex>, dotnet_diag_<hex>.exe), chmodded 0755 on POSIX, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or the equivalent cmd invocation on Windows. There is no hash, signature, or publisher verification on the downloaded content. The package presents itself as a 'bnpl blocks' UI component, which does not correspond to fetching and executing an opaque native binary. Destination hosts are non-publisher anonymous workers.dev endpoints and a.ru DNS covert channel.

Malicious versions

1 flagged
35.8.2

Indicators of compromise (SHA-256)

d52a16c390437bd38f791fca1380253d0e4e3056a1b1efd2af35f4fa95e22e28

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 bnpl-blocks-desktop-large-bnpl-reviews (version 35.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-desktop-large-bnpl-reviews across your stack and pipelines.

  2. If you installed it — respond

    Remove bnpl-blocks-desktop-large-bnpl-reviews 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 bnpl-blocks-desktop-large-bnpl-reviews 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 bnpl-blocks-desktop-large-bnpl-reviews 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-desktop-large-bnpl-reviews on npm has been identified as a malicious package (version 35.8.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015445

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-desktop-large-bnpl-reviews-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.

Explore

bnpl-blocks-desktop-large-bnpl-reviews (npm) malicious package — MAL-2026-12946 | O3 Security