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

bnpl-blocks-mobile-bnpl-partnersnpm

Advisory published Updated

bnpl-blocks-mobile-bnpl-partners is a confirmed malicious npm package (MAL-2026-13000) that executes malicious code on install (malicious version 35.8.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-mobile-bnpl-partners (npm)

MAL-2026-13000
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-mobile-bnpl-partners

What this malware does

index.js unconditionally requires helpers.js, which on module load fetches a platform-specific binary from string-split-obfuscated Cloudflare Workers subdomains (oob-worker.cf*.workers.dev) with a DNS/TXT fallback under *.dl.wel1.ru, writes the payload to /var/tmp or %TEMP% under cover-story filenames (.cache<hex> on Linux, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. Hostnames are assembled at runtime from split arrays joined with.join('') to hide the destinations from static scanners, and cp/fs API names are reconstructed via string concatenation (require('child_'+'process'), fs['chmod'+'Sync']). A parallel dropper implementation is bundled in lib/telemetry.js under an 'analytics SDK' cover story with the same fetch, base64-decode, chmod 755, and detached-shell-spawn primitives. Requiring this package on any platform executes attacker-controlled code on the installer's host.

Malicious versions

1 flagged
35.8.8

Indicators of compromise (SHA-256)

6e19ad8f13f3c9f4ab6b31c65bad3fb1239ad816c040504428eae8c32740869c

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-mobile-bnpl-partners (version 35.8.8).

  2. If you installed it — respond

    Remove bnpl-blocks-mobile-bnpl-partners 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-blocks-mobile-bnpl-partners 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-blocks-mobile-bnpl-partners on npm has been identified as a malicious package (version 35.8.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015377

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-mobile-bnpl-partners-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.

Explore

bnpl-blocks-mobile-bnpl-partners (npm) malicious package — MAL-2026-13000 | O3 Security