bnpl-molecule-mobile-bnpl-onboardingnpm
bnpl-molecule-mobile-bnpl-onboarding is a confirmed malicious npm package (MAL-2026-13025) that typosquats a legitimate package to trick installs (malicious version 35.7.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-molecule-mobile-bnpl-onboarding (npm)
What this malware does
On require of the package, index.js loads runtime.js which selects a platform-keyed asset (linux/darwin/win32), downloads an opaque binary from one of three string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT-record base64 fallback via wel1.ru subdomains, writes the payload to /var/tmp or %TEMP% under a masquerading filename (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods it 0755, and detached-spawns it via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are reconstructed by joining split fragments (e.g. ["oob-worker.cf1","00-416.wo","rkers",".d","ev"].join("")) to evade static analysis, and a decoy no-op logger writes empty strings to stderr. The package name impersonates a BNPL onboarding module but ships no such functionality.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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-onboarding (version 35.7.8). 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-onboarding across your stack and pipelines.
If you installed it — respond
bnpl-molecule-mobile-bnpl-onboarding is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-molecule-mobile-bnpl-onboarding, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bnpl-molecule-mobile-bnpl-onboarding 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-onboarding 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-onboarding-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.