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

bnpl-blocks-atom-bnpl-carousel-linenpm

bnpl-blocks-atom-bnpl-carousel-line is a confirmed malicious npm package (MAL-2026-12869) that executes malicious code on install (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-carousel-line (npm)

MAL-2026-12869
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-atom-bnpl-carousel-line

What this malware does

On require of the package's main entry, index.js loads./shim.js, which assembles attacker-controlled hostnames from string-split arrays (e.g. ["oob-work","er.cf101-adf.w","orke","rs.d","ev"].join("") and ["sdk.","dl.we","l1.","ru"].join("")), downloads a platform-specific binary over HTTPS from a rotated list of oob-worker.cf10*-*.workers.dev hosts with a DNS TXT fallback under dl.wel1.ru, writes it to /var/tmp/.cache<rnd> on Unix or %TEMP%\dotnet_diag_<rnd>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. A sibling file lib/telemetry.js contains the same fetch-decode-chmod-exec pattern with dynamic property construction (fs["chmod"+"Sync"]) disguised as an analytics SDK. The package name suggests a BNPL UI component but ships an install/import-time binary dropper with hostname obfuscation and DNS-over-TXT fallback for HTTPS blocking.

Malicious versions

1 flagged
35.1.6

Indicators of compromise (SHA-256)

f49d0a2f45c6a825ed105c2859c618bedcc4643650bf6719c35c47e462c553c8

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015510

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-carousel-line-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-atom-bnpl-carousel-line (npm) malicious package — MAL-2026-12869 | O3 Security