Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bnpl-blocks-mobile-bnpl-reviewsnpm

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

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

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

What this malware does

On require() of the package, index.js loads bootstrap.js which selects a platform-specific URL, downloads an executable from obfuscated Cloudflare Workers mirrors (hostnames assembled at runtime via string-splitting to oob-worker.cf*.workers.dev), writes it to /var/tmp or %TEMP% under a disguised filename such as dotnet_diag<hex>.exe or.cache_<hex>, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. A DNS-TXT covert channel under c.*.dl.wel1.ru reconstructs a base64 payload as fallback delivery. Execution is gated once per host via a /tmp/.analytics_state stamp. The delivery infrastructure is not the package publisher's, the fetched bytes are unsigned and unverified, the destination path and filename are disguised, and execution is detached — the shape is a supply-chain dropper, not a legitimate runtime install.

Malicious versions

1 flagged
35.5.3

Indicators of compromise (SHA-256)

d7f199feae1ae38b3dfd2c94cf56ad56ef7ef0fe4e0172a64ef76ddf401bcbcb

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-mobile-bnpl-reviews (version 35.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-reviews across your stack and pipelines.

  2. If you installed it — respond

    Remove bnpl-blocks-mobile-bnpl-reviews 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-reviews was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks bnpl-blocks-mobile-bnpl-reviews before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-015378

References

Credits

  • Amazon Inspector · finder

Detect & block this

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