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

bnpl-blocks-mobile-bnpl-separatornpm

Advisory published Updated

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

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

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

What this malware does

On require of the package, index.js loads bootstrap.js which fetches a platform-specific binary payload over HTTPS from author-controlled hosts whose names are assembled at runtime by joining split string fragments (resolving to *.workers.dev subdomains), with a fallback that reassembles a base64-chunked payload from DNS TXT records under *.dl.wel1.ru. The fetched binary is written to /tmp/.cache<rnd> on Unix or %TEMP%/dotnet_diag_<rnd>.exe on Windows, chmod'd 0755, and spawned detached via /bin/sh -c or cmd. A stamp file named.analytics_state and env-var checks for DISABLE_TELEMETRY/ANALYTICS_OPT_OUT are used as a telemetry-themed cover. The destination hosts are not the package's publisher infrastructure, the fetched bytes are opaque and unpinned, and execution occurs at import time on every consumer machine.

Malicious versions

1 flagged
35.5.2

Indicators of compromise (SHA-256)

6a76b1d07f3d0357fa471ba2b1e5a0052b1b789f96763446a20e19cf7ac7ab11

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-mobile-bnpl-separator (version 35.5.2).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015387

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-mobile-bnpl-separator-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-blocks-mobile-bnpl-separator (npm) malicious package — MAL-2026-13004 | O3 Security