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

bnpl-blocks-desktop-bnpl-info-slidernpm

bnpl-blocks-desktop-bnpl-info-slider is a confirmed malicious npm package (MAL-2026-12930) that executes malicious code on install (malicious version 35.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-desktop-bnpl-info-slider (npm)

MAL-2026-12930
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-desktop-bnpl-info-slider

What this malware does

index.js loads support.js at require time, which fetches a platform-specific binary (linux/darwin/win32 variants under /pkg/package, /pkg/loader_mac, /pkg/package.exe) from three Cloudflare workers.dev hosts reassembled at runtime from string-array fragments: oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev. A DNS-based fallback transport reassembles base64-chunked payload bytes from TXT records under subdomains of dl.wel1.ru (count via c.<domain>, chunks via i.<domain>) to bypass HTTPS egress controls. The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe,.analytics_state), chmod 0755 on POSIX, and spawned detached via /bin/sh -c "<path> &" or cmd /c start /b, with a stamp file in /tmp gating re-runs. Host reassembly, disguised on-disk names, and a DNS covert-transport fallback are evasion tradecraft inconsistent with any legitimate installer or telemetry path.

Malicious versions

1 flagged
35.1.3

Indicators of compromise (SHA-256)

a8dabd39ff50be1e1295dea75e71b63acd26c7617be87af38df3cdbaaee53302

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015458

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-desktop-bnpl-info-slider-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-desktop-bnpl-info-slider (npm) malicious package — MAL-2026-12930 | O3 Security