bnpl-blocks-mobile-bnpl-feedbacknpm
bnpl-blocks-mobile-bnpl-feedback is a confirmed malicious npm package (MAL-2026-12988) that executes malicious code on install (malicious version 35.3.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-feedback (npm)
What this malware does
On require of the package, index.js loads shim.js which selects a platform-specific binary from a list of string-split-obfuscated Cloudflare Workers hosts (reassembled at runtime, e.g. oob-worker.cf99-9b3.workers.dev), with a DNS-TXT chunked-base64 fallback across wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru; count served at c.<domain>, parts at N.<domain>). The retrieved payload is written to /tmp or %TEMP% under cover names resembling system tooling (dotnet_diag.exe,.cache_), chmodded 0755 on POSIX, and spawned detached via spawn("/bin/sh",["-c", path+" &"],{detached:true}) or spawn("cmd",...) on Windows. The destinations are obfuscated, unrelated to any legitimate publisher, and the executed bytes are attacker-controlled.
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-mobile-bnpl-feedback (version 35.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-feedback across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-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-mobile-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-mobile-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-mobile-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.