bnpl-blocks-atom-bnpl-checkboxnpm
bnpl-blocks-atom-bnpl-checkbox is a confirmed malicious npm package (MAL-2026-13527) that executes malicious code on install (malicious version 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-checkbox (npm)
What this malware does
On require() of the package main, polyfill.js runs an async bootstrap that reconstructs network destinations from string-split fragments (require("child"+"process"), array-join of hostname fragments), fetches a platform-specific binary payload via https.get from Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the bytes to a temp path under a disguised filename, chmods 0755, and spawns it detached via cp.spawn('/bin/sh',['-c', filePath+' &'],{detached:true}). No version pinning, no hash/signature verification, and destinations are unrelated to the package's advertised purpose. lib/telemetry.js contains a dormant second copy of the same drop-and-spawn shape (base64 chunk decoding, chmod 0755, detached /bin/sh spawn), currently unreachable from index.js. The 'analytics' framing and split-string obfuscation of both the child_process import and the hostnames are cover-story evasion of static analysis.
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-checkbox (version 35.6.1). 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-checkbox across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-checkbox 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-checkbox 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-checkbox 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-checkbox-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.