bnpl-blocks-atom-bnpl-navigation-arrownpm
bnpl-blocks-atom-bnpl-navigation-arrow is a confirmed malicious npm package (MAL-2026-12881) that executes malicious code on install (malicious version 35.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-navigation-arrow (npm)
What this malware does
Requiring this package executes platform.js, which detects the host OS/arch, fetches an opaque binary from one of four author-controlled Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT base64 fallback resolved via subdomains of wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), writes it to /var/tmp/.cache<hex> on Unix or TEMP/dotnet_diag_<hex>.exe on Windows disguised as a system artifact, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. All destination hostnames, resolver domains, and even the child_process module name are assembled from split string literals (e.g. ["oob-worke","r.cf103-07","0.worke","rs.de","v"].join(""), require("child_" + "process")) to evade signature-based scanners. A second copy of the dropper is bundled in lib/telemetry.js under an 'analytics SDK' cover story, containing the same base64 buffer construction, fs["chmod" + "Sync"] to 0755, and cp.spawn("/bin/sh", ["-c", filePath + " &"]) primitives.
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-bnpl-navigation-arrow (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-navigation-arrow across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-navigation-arrow 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-bnpl-navigation-arrow 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-bnpl-navigation-arrow 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-bnpl-navigation-arrow-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.