bnpl-blocks-independent-bnpl-itemsnpm
bnpl-blocks-independent-bnpl-items is a confirmed malicious npm package (MAL-2026-12958) that executes malicious code on install (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-items (npm)
What this malware does
On require() of this package, index.js loads runtime.js which selects a platform-specific asset, fetches an opaque binary from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) assembled at runtime via string-array.join to evade static matching, writes it to /tmp or %TEMP% under a cover-story name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmods 0755, and spawns it detached via /bin/sh -c or cmd. A TTL lockfile named.analytics_state masquerades the persistence as telemetry. If HTTPS egress is blocked, _runtime.js falls back to a DNS-TXT covert channel under author-controlled subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), reassembling a base64 payload from numbered TXT records and executing it. No hash or signature verification is performed on the fetched bytes. The README describes only a trivial abstraction class, unrelated to any of the observed network or execution behavior.
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-independent-bnpl-items (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-independent-bnpl-items across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-items 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-independent-bnpl-items 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-independent-bnpl-items 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-independent-bnpl-items-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.