bnpl-blocks-atom-bnpl-imagenpm
bnpl-blocks-atom-bnpl-image is a confirmed malicious npm package (MAL-2026-12876) that executes malicious code on install (malicious version 35.2.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-image (npm)
What this malware does
On require() of the package, index.js loads runtime.js which downloads a platform-specific executable from attacker-controlled hosts whose names are reconstructed at runtime via split-string concatenation (oob-worker.cf1{01,02,03}*.workers.dev and {sdk,ext,pkg,net}.dl.wel1.ru), writes the payload to a temp directory under a disguised name (dotnet_diag<hex>.exe on Windows, hidden.cache_<hex> on Unix), chmods 0755 on Unix, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A DNS-TXT-over-base64 fallback channel is present. Env-var kill switches (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a /tmp/.analytics_state stamp implement session dedup and evasion. A second file lib/telemetry.js (not currently referenced from index.js) ships the same drop-and-exec primitive with split require("child_"+"process") obfuscation and base64-reconstructed payload chunks.
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-image (version 35.2.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-bnpl-image across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-image 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-image 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-image 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-image-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.