bnpl-blocks-atom-desktop-bnpl-dangerously-htmlnpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind 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-dangerously-html (version 35.9.9). 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-dangerously-html across your stack and pipelines.
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.
Did it already run?
If bnpl-blocks-atom-desktop-bnpl-dangerously-html 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-atom-desktop-bnpl-dangerously-html 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
Campaign
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.