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

bnpl-apinpm

Advisory published Updated

bnpl-api is a confirmed malicious npm package (MAL-2026-12860) that executes malicious code on install (malicious version 35.9.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-api (npm)

MAL-2026-12860
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-api

What this malware does

The package presents itself as an empty API stub (index.js exports a no-op BnplApi and unconditionally require("./_support") on load). _support.js assembles download hostnames via array-join string splitting (["oob-worke","r.cf103-070.w","or","kers",".d","ev"].join("")) to reconstruct three anonymous Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), fetches a platform-specific native executable, writes it to /tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via spawn("/bin/sh",...) / spawn("cmd",...). If HTTPS retrieval fails, a DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru reassembles a base64-encoded binary from numbered TXT records and executes it the same way. lib/telemetry.js also loads child_process via require("child_"+"process") to evade static scanners. The package has no legitimate functionality; its only on-load effect is running an opaque attacker-controlled binary on the installer's host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
35.9.5

Indicators of compromise (SHA-256)

2eda2ee8ac0f1ffdce814e7ca4bb7e1c1ca52beebb7048b18a64d8e13e87abf4
7fbe1d12c0d2de7bf53cba5a61e26fbbfcf66ea9dec49d0f0dfbdd1d8a12fbf3

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-api (version 35.9.5).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015520GHSA-fgxc-644c-34qm

References

Credits

  • Amazon Inspector · finder

Detect & block this

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