bnpl-blocks-independent-bnpl-schemenpm
bnpl-blocks-independent-bnpl-scheme is a confirmed malicious npm package (MAL-2026-12968) that executes malicious code on install (malicious version 35.8.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-scheme (npm)
What this malware does
The package ships a loader (_loader.js) that assembles remote hostnames at runtime from string-split arrays (reconstructing subdomains of wel1.ru and a cloudflare workers.dev host) to evade static detection, issues an https.get to those endpoints, writes the response to disk, chmods it executable (0755), and spawns it via /bin/sh -c or cmd. A sibling module lib/telemetry.js (~81KB) presents itself as an 'analytics SDK' but contains the same dropper primitives (base64 chunk decode, chmodSync 0755, cp.spawn('/bin/sh',['-c', filePath+' &'])). Hostname reconstruction via array split/join combined with a fetch-write-chmod-exec chain is an obfuscated remote code delivery mechanism, not legitimate SDK behavior. The runtime-assembled destinations do not match any documented publisher endpoint, and the code path is reachable on load. Installing or loading this package results in execution of attacker-controlled code fetched from wel1.ru subdomains and a *.workers.dev host on the installer's machine.
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-scheme (version 35.8.4). 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-scheme across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-scheme 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-scheme 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-scheme 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-scheme-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.