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

bnpl-blocks-mobile-bnpl-navigationnpm

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

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

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

What this malware does

On require of the package's main, index.js unconditionally loads bootstrap.js, which fetches a platform-specific binary from Cloudflare Workers subdomains whose hostnames are reconstructed at runtime from split string fragments (e.g. 'oob-worker.cf100-416.workers.dev', 'cf103-070.workers.dev', 'cf102-baf.workers.dev'), with a DNS-TXT base64-chunked fallback resolving over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to a hidden temp path of the form.cache<rand>/dotnet_diag_<rand>.exe, chmod 0755 on POSIX, and spawned detached via /bin/sh -c on POSIX or cmd on Windows. There is no hash or signature verification, the destination hosts are obfuscated by string-split concatenation, and lib/telemetry.js exhibits the same reconstruct-fetch-write-chmod-spawn pattern with require("child_" + "process"). The package is presented as 'telemetry', but the code path is an unsigned unpinned remote-code loader that executes attacker-controlled bytes on any machine that installs or requires the package.

Malicious versions

1 flagged
35.3.2

Indicators of compromise (SHA-256)

295c0eb6e0491ca81198ae9cbeb921b3658d573f98bd43e82e6bbc0fe953683b

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-navigation (version 35.3.2). 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-navigation across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015383

References

Credits

  • Amazon Inspector · finder

Detect & block this

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