bnpl-blocks-shops-apinpm
bnpl-blocks-shops-api is a confirmed malicious npm package (MAL-2026-13017) that executes malicious code on install (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-shops-api (npm)
What this malware does
index.js is the declared main entry and unconditionally requires./setup.js on load. setup.js reconstructs attacker-controlled endpoints via string-split obfuscation (e.g. ['oob-work','er.cf102-b','af.w','orkers','.de','v'].join('')) to build URLs at oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, and oob-worker.cf102-baf.workers.dev, with a DNS TXT chunked-base64 fallback via {sdk,ext,pkg,net}.dl.wel1.ru. Platform-specific binaries are downloaded to /tmp or %TEMP% under disguised names (e.g. dotnet_diag_.exe,.cache_), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Dangerous API names are also fragmented (require('child_'+'process'), fs['chmod'+'Sync'], os['host'+'name']) to evade scanners. The fetched bytes are unpinned, unverified, and unrelated to the package's advertised SDK purpose; any consumer that requires this package triggers full-host code execution.
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-shops-api (version 35.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-shops-api across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-shops-api 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-shops-api 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-shops-api 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-shops-api-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.