NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bnpl-blocks-atom-desktop-bnpl-dangerously-htmlnpm

Advisory published Updated

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

Malicious code in bnpl-blocks-atom-desktop-bnpl-dangerously-html (npm)

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

What this malware does

On require of the package, index.js loads./ext.js, which reassembles C2 hostnames from split string fragments (e.g. 'oob-worker.cf10x-*.workers.dev' built via array.join) and downloads a platform-specific binary over HTTPS. If the primary fetch fails, the payload is reassembled from DNS TXT records under *.dl.wel1.ru. The retrieved bytes are written to /var/tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd /c start, with a marker file to suppress re-execution. Cover-story env-var checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and filenames mimicking a telemetry/diagnostics SDK conceal the loader. The download destinations are anonymous, unpinned, unauthenticated, obfuscated, and unrelated to the package's declared publisher; the payload is opaque native code executed with the user's privileges on every require.

Malicious versions

1 flagged
35.9.9

Indicators of compromise (SHA-256)

d67ae3d6b9d42c80691f5be62d2b59d087b9457657a5fa12d4881c2db7c1aa5d

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-desktop-bnpl-dangerously-html (version 35.9.9).

  2. If you installed it — respond

    bnpl-blocks-atom-desktop-bnpl-dangerously-html 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-dangerously-html was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bnpl-blocks-atom-desktop-bnpl-dangerously-html on npm has been identified as a malicious package (version 35.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015486

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-desktop-bnpl-dangerously-html-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-dangerously-html (npm) malicious package — MAL-2026-12901 | O3 Security