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

bnpl-blocks-atom-bnpl-image-popupnpm

bnpl-blocks-atom-bnpl-image-popup is a confirmed malicious npm package (MAL-2026-12877) that opens a backdoor for remote access (malicious version 35.9.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-image-popup (npm)

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

What this malware does

On require of the package, index.js loads compat.js, which reconstructs C2 hostnames from string-split arrays (e.g., ["oob-worker.cf101-adf.workers",".dev"].join("")) to build HTTPS endpoints on *.workers.dev and DNS fallback hosts under *.dl.wel1.ru. compat.js selects a platform-specific endpoint, downloads an opaque binary via https.get, writes it to /var/tmp on Unix or the Windows temp directory under a disguised name (e.g., dotnet_diag<rnd>.exe or.cache<rnd>), chmods it 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd /c start. A fallback loadViaDns routine retrieves the payload as chunked base64 from TXT records under *.dl.wel1.ru (a count is read from c.<domain>, then N sequential TXT records are concatenated and base64-decoded). Marker-file single-execution gating and TELEMETRY/DO_NOT_TRACK environment-variable kill switches are present to suppress re-execution and evade observation.

Malicious versions

1 flagged
35.9.6

Indicators of compromise (SHA-256)

893348e540e6c6a6cb856324bb2379d838bead9f4d2ceab1ae7c3509094871f6

Detection & response playbook

Backdoor / remote access
  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-image-popup (version 35.9.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-image-popup across your stack and pipelines.

  2. If you installed it — respond

    bnpl-blocks-atom-bnpl-image-popup establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

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

Campaign

IN-MAL-2026-015506

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-image-popup-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore