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

bnpl-blocks-shops-apinpm

Advisory published Updated

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

Malicious code in bnpl-blocks-shops-api (npm)

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

What this malware does

index.js is the declared main entry and unconditionally requires./setup.js on load. setup.js reconstructs attacker-controlled endpoints via string-split obfuscation (e.g. ['oob-work','er.cf102-b','af.w','orkers','.de','v'].join('')) to build URLs at oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, and oob-worker.cf102-baf.workers.dev, with a DNS TXT chunked-base64 fallback via {sdk,ext,pkg,net}.dl.wel1.ru. Platform-specific binaries are downloaded to /tmp or %TEMP% under disguised names (e.g. dotnet_diag_.exe,.cache_), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Dangerous API names are also fragmented (require('child_'+'process'), fs['chmod'+'Sync'], os['host'+'name']) to evade scanners. The fetched bytes are unpinned, unverified, and unrelated to the package's advertised SDK purpose; any consumer that requires this package triggers full-host code execution.

Malicious versions

1 flagged
35.2.5

Indicators of compromise (SHA-256)

209f1c0883ce38bd482d809b83edd85e8d3db75a379909e1b47ee24562c49526

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-shops-api (version 35.2.5).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015365

References

Credits

  • Amazon Inspector · finder

Detect & block this

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