bnpl-blocks-storiesnpm
bnpl-blocks-stories is a confirmed malicious npm package (MAL-2026-13018) that executes malicious code on install (malicious version 35.2.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-stories (npm)
What this malware does
On require() of the package, index.js loads./_ext which reconstructs hardcoded hostnames via fragment-joined arrays (e.g. oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev) and a DNS-TXT fallback under *.wel1.ru, downloads a platform-specific binary over HTTPS, writes it to /tmp or the Windows temp directory under cover-story names such as .cache_XXXX and dotnet_diag_XXXX.exe, chmods it 0755, and spawns it detached via /bin/sh -c '<path> &' or cmd.exe. A second, structurally identical dropper is shipped as lib/telemetry.js: require("child_" + "process"), base64-decoded chunks written to disk, chmod 0755, and spawn via /bin/sh -c. Destination hostnames are assembled at runtime via .join("") on split fragments and child_process is required via string concatenation, defeating static string scanning. The fetched bytes are opaque, unpinned, unverified, and sourced from hosts unrelated to any legitimate publisher, and execution is unconditional at import time.
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-stories (version 35.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-stories across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-stories 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-stories 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-stories 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-stories-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.