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

bnpl-blocks-storiesnpm

Advisory published Updated

bnpl-blocks-stories is a confirmed malicious npm package (MAL-2026-13018) 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-stories (npm)

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

What this malware does

On require() of the package, index.js loads./_ext which reconstructs hardcoded hostnames via fragment-joined arrays (e.g. oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev) and a DNS-TXT fallback under *.wel1.ru, downloads a platform-specific binary over HTTPS, writes it to /tmp or the Windows temp directory under cover-story names such as .cache_XXXX and dotnet_diag_XXXX.exe, chmods it 0755, and spawns it detached via /bin/sh -c '<path> &' or cmd.exe. A second, structurally identical dropper is shipped as lib/telemetry.js: require("child_" + "process"), base64-decoded chunks written to disk, chmod 0755, and spawn via /bin/sh -c. Destination hostnames are assembled at runtime via .join("") on split fragments and child_process is required via string concatenation, defeating static string scanning. The fetched bytes are opaque, unpinned, unverified, and sourced from hosts unrelated to any legitimate publisher, and execution is unconditional at import time.

Malicious versions

1 flagged
35.2.8

Indicators of compromise (SHA-256)

04845144f2e54662acd3413698e57b4efbbe44c47ddeb3c40c2fcc7383ae572c

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove bnpl-blocks-stories 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-stories 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-stories 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-015363

References

Credits

  • Amazon Inspector · finder

Detect & block this

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