NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bnpl-molecule-mobile-bnpl-selectornpm

Advisory published Updated

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)

MAL-2026-13026
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-molecule-mobile-bnpl-selector

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

1 flagged
35.1.1

Indicators of compromise (SHA-256)

daf9828096a3c18e00ad577689ebcf4e4fa304a8702db4a0993063c95182530e

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-molecule-mobile-bnpl-selector (version 35.1.1).

  2. 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.

  3. Did it already run?

    If bnpl-molecule-mobile-bnpl-selector was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bnpl-molecule-mobile-bnpl-selector on npm has been identified as a malicious package (version 35.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015346

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bnpl-molecule-mobile-bnpl-selector (npm) malicious package — MAL-2026-13026 | O3 Security