bnpl-molecule-mobile-bnpl-selectornpm
bnpl-molecule-mobile-bnpl-selector is a confirmed malicious npm package (MAL-2026-13026) that executes malicious code on install (malicious version 35.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-molecule-mobile-bnpl-selector (npm)
What this malware does
On require() of the package, index.js loads adapter.js, which runs an asynchronous dropper: it selects a platform-specific asset, downloads an executable via https.get from one of three Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), writes the payload to /var/tmp/.cache<hex> with chmod 0755 on Unix or to the Windows temp directory as dotnet_diag_<hex>.exe (masquerading as a.NET diagnostic tool), and spawns it detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. Destination hostnames, the child_process require, and chmodSync are hidden behind array-join string splits (e.g. "child_"+"process", ["oob-worker.cf102-baf.wor","kers",".d","ev"].join("")). A DNS-over-TXT fallback resolves c.sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru for a chunk count, then reassembles a base64 payload from numbered TXT records under those subdomains and executes it identically, providing a covert transport that evades HTTP egress filtering. The dropper is framed with a fake "Analytics SDK" / DISABLE_TELEMETRY cover story. A second copy of the same dropper primitives is bundled under lib/telemetry.js (~81 KB) but is not required on the current execution path.
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-molecule-mobile-bnpl-selector (version 35.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-molecule-mobile-bnpl-selector across your stack and pipelines.
If you installed it — respond
Remove bnpl-molecule-mobile-bnpl-selector 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-molecule-mobile-bnpl-selector 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-molecule-mobile-bnpl-selector 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-molecule-mobile-bnpl-selector-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.