bnpl-blocks-atom-desktop-bnpl-highlighted-textnpm
bnpl-blocks-atom-desktop-bnpl-highlighted-text is a confirmed malicious npm package (MAL-2026-12902) that executes malicious code on install (malicious version 35.2.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-desktop-bnpl-highlighted-text (npm)
What this malware does
On require() of the package, index.js loads platform.js, which assembles destination hostnames at runtime from split-string arrays to hide them from static inspection. The resolved hosts are Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, cf100-416.workers.dev, cf101-adf.workers.dev, cf103-070.workers.dev) with a DNS-TXT covert-channel fallback over subdomains of wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The code fetches a platform-specific binary, writes it under a disguised filename to /tmp (.cache<rand>) on POSIX or %TEMP% (dotnet_diag_<rand>.exe) on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd with stdio ignored and unref(). A second file, lib/telemetry.js (81KB), ships in the tarball and contains parallel dropper logic (HTTPS+DNS transport, base64 chunk decoding, /bin/sh spawn, fs["chmod"+"Sync"] with 0755) that is not currently referenced by index.js but is present and activatable. The destinations are non-publisher, the payload is opaque and unpinned, the filenames are disguised, the destinations are obfuscated, and execution is detached — the shape of a second-stage dropper granting arbitrary code execution on any host that installs or requires the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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-highlighted-text (version 35.2.3). 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-highlighted-text across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-desktop-bnpl-highlighted-text 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-atom-desktop-bnpl-highlighted-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.
How O3 protects you
O3 blocks bnpl-blocks-atom-desktop-bnpl-highlighted-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bnpl-blocks-atom-desktop-bnpl-highlighted-text-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.