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

bnpl-blocks-mobile-bnpl-headernpm

Advisory published Updated

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

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

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

What this malware does

On require() of the package, index.js loads bridge.js which fetches an OS-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-over-TXT base64 fallback to *.wel1.ru. The retrieved bytes are written to a hidden path in /var/tmp or %TEMP% under masquerading names (.cache<rand> on Unix, dotnet_diag_<rand>.exe on Windows), chmodded to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Destination hostnames are reconstructed at runtime from split string fragments joined with.join(""), and the drop is gated by DISABLE_TELEMETRY / DO_NOT_TRACK environment checks to present as opt-out telemetry. A freshness marker is written to /tmp/.analytics_state. The package presents itself as a mobile BNPL SDK; none of the fetch-write-execute behavior relates to that stated purpose.

Malicious versions

1 flagged
35.2.8

Indicators of compromise (SHA-256)

3f511a9eac93e0ef06eeec5ab7ec22330cb092c4fda952ec540f4a9be3fc522f

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-mobile-bnpl-header (version 35.2.8).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015388

References

Credits

  • Amazon Inspector · finder

Detect & block this

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