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

dolyame-boxy-atom-bnpl-popupnpm

dolyame-boxy-atom-bnpl-popup is a confirmed malicious npm package (MAL-2026-13289) that steals credentials and exfiltrates sensitive data (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-atom-bnpl-popup (npm)

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

What this malware does

On require(), compat.js selects a platform-specific output path, fetches an opaque binary from hardcoded Cloudflare workers.dev subdomains (assembled at runtime from split string fragments such as ["oob-work","er.cf100-416",".worker","s.dev"].join("")) with a DNS TXT fallback under dl.wel1.ru, writes it to /tmp or %TEMP% under a decoy name (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods it to 0755, and spawns it detached via cp.spawn("/bin/sh",["-c", filePath+" &"], {detached:true}) or spawn("cmd",...). Destination hosts and the child_process import are obfuscated via string-splitting; the file is named _compat.js and gated behind opt-out env vars (DISABLE_TELEMETRY) as cover. A second parallel dropper is shipped in lib/telemetry.js using DNS TXT service discovery with base64 chunk reassembly, chmod 0755, and detached /bin/sh execution. Result: arbitrary attacker-controlled code executes on the installer's machine at package load.

Malicious versions

1 flagged
35.9.3

Indicators of compromise (SHA-256)

26bfa012ebc79b0bf89d9eff7b1b0279bba4df11c76f80f6e81171f67d0dd7e5

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-atom-bnpl-popup (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-atom-bnpl-popup across your stack and pipelines.

  2. If you installed it — respond

    dolyame-boxy-atom-bnpl-popup is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

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

Campaign

IN-MAL-2026-015707

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore