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

bnpl-blocks-atom-desktop-bnpl-textnpm

bnpl-blocks-atom-desktop-bnpl-text is a confirmed malicious npm package (MAL-2026-12903) that opens a backdoor for remote access (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-desktop-bnpl-text (npm)

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

What this malware does

On require(), index.js unconditionally loads _polyfill.js, which selects a platform-specific asset path and fetches an opaque binary from one of three Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT fallback resolving subdomains of wel1.ru. The C2 hostnames are assembled at runtime from split string fragments joined with.join('') to evade literal string matching. The fetched bytes are written to /var/tmp or %TEMP% under a disguised name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows) mimicking a.NET diagnostic tool, chmod'd to 0755, and spawned detached via /bin/sh -c '<path> &' or cmd. Execution is gated by a stamp file and environment opt-outs to reduce observability. The package advertises a trivial text-abstraction layer with no legitimate need for a native binary or platform-specific asset delivery.

Malicious versions

1 flagged
35.2.5

Indicators of compromise (SHA-256)

007bafa1def88d10e8f2c247e0ab1d0872d2a4f33f4bb134fe46877f75aa9eca

Detection & response playbook

Backdoor / remote access

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

  2. If you installed it — respond

    bnpl-blocks-atom-desktop-bnpl-text establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

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

Campaign

IN-MAL-2026-015488

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-desktop-bnpl-text-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bnpl-blocks-atom-desktop-bnpl-text (npm) malicious package — MAL-2026-12903 | O3 Security