bnpl-blocks-atom-bnpl-action-cardnpm
bnpl-blocks-atom-bnpl-action-card is a confirmed malicious npm package (MAL-2026-12862) that executes malicious code on install (malicious version 35.4.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-action-card (npm)
What this malware does
On require() of the package, index.js loads _loader.js which selects a platform-specific payload path, fetches bytes from one of three runtime-assembled Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a chunked-base64 DNS-TXT fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the bytes to /tmp or Windows TEMP under disguised names (.cache_<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns the file detached via /bin/sh or cmd. Destination hostnames and the child_process / chmodSync identifiers are constructed at runtime via array-join and string concatenation to hide the endpoints from static inspection, a marker file .analytics_state is dropped, and env-var opt-outs are framed as telemetry to cover the drop-and-execute behavior. lib/telemetry.js ships a second, equivalent dropper in the tarball (chunked-base64 assembly, chmod 0755, cp.spawn('/bin/sh', ['-c', filePath + ' &'], {detached:true})). The fetched binary is opaque, unpinned, unsigned, and not tied to the package version.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-action-card (version 35.4.7). 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-action-card across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-action-card 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-action-card 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-action-card 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-action-card-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.