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

bnpl-blocks-component-story-namenpm

bnpl-blocks-component-story-name is a confirmed malicious npm package (MAL-2026-12907) that executes malicious code on install (malicious version 35.2.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-component-story-name (npm)

MAL-2026-12907
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-component-story-name

What this malware does

On require of this package, index.js loads polyfill.js which downloads a platform-specific executable from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT covert-channel fallback that reassembles base64 payload chunks from numeric subdomains of sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (dotnet_diag.exe,.cache_), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are assembled at runtime by joining split string fragments to evade static string scanners. Requiring the package yields arbitrary remote code execution on the installer's host.

Malicious versions

1 flagged
35.2.7

Indicators of compromise (SHA-256)

a797e2310dd4df10e11e104dad3fbb135621e9997a5425f480c3c884da59ca6d

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-component-story-name (version 35.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-component-story-name across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015476

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-component-story-name-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bnpl-blocks-component-story-name (npm) malicious package — MAL-2026-12907 | O3 Security