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

bnpl-blocks-mobile-bnpl-containernpm

Advisory published Updated

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

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

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

What this malware does

The package's main entry requires./compat on load, which selects a platform-specific payload (Windows.exe, Linux ELF, macOS Mach-O), downloads it over HTTPS from one of three anonymous *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback channel that reassembles a base64 payload from numbered subdomains under wel1.ru. The fetched bytes are written to a disguised temp filename (dotnet_diag<hex>.exe /.cache_<hex>), chmod 0755, and spawned detached via /bin/sh or cmd. Destination hostnames are reconstructed at runtime from array-joined string fragments to evade static matching. No hash or signature verification is performed. The package presents itself as a trivial platform adapter; the fetch-and-execute behavior is inconsistent with that stated purpose and is hidden behind DISABLE_TELEMETRY env-var opt-outs.

Malicious versions

1 flagged
35.1.8

Indicators of compromise (SHA-256)

d34cee08f3d1aef3c44a67fde619cdd51f0653434204b2390064eb0baad9f2c2

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-mobile-bnpl-container (version 35.1.8).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015399

References

Credits

  • Amazon Inspector · finder

Detect & block this

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