bnpl-blocks-atom-bnpl-feedbacknpm
bnpl-blocks-atom-bnpl-feedback is a confirmed malicious npm package (MAL-2026-12875) that executes malicious code on install (malicious version 35.7.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-feedback (npm)
What this malware does
On require('bnpl-blocks-atom-bnpl-feedback'), index.js loads bridge.js which selects a platform-specific asset, downloads an unsigned binary via HTTPS from string-split-obfuscated Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, cf101-adf, cf102-baf, cf103-070.workers.dev) with a base64-over-DNS-TXT covert-channel fallback resolving under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names (.cache<rnd> on Unix, dotnet_diag_<rnd>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh or cmd. The package's stated purpose is a 'data mapper' and index.js exports a trivial no-op class with no dependencies, contradicting the network-dropper behavior implemented in _bridge.js. Hostnames are reconstructed at runtime from split string arrays joined with empty separators to evade static matching.
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-feedback (version 35.7.5). 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-feedback across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-feedback 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-feedback 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-feedback 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-feedback-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.