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

dolyame-ui-popupcarouselnpm

dolyame-ui-popupcarousel is a confirmed malicious npm package (MAL-2026-13593) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-popupcarousel (npm)

MAL-2026-13593
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-ui-popupcarousel

What this malware does

On require of the package, support.js and lib/telemetry.js each fetch a platform-specific native binary from rotating anonymous Cloudflare Workers hosts (oob-worker.cf10{0-3}-*.workers.dev) with a DNS-TXT base64 fallback via *.dl.wel1.ru, write the payload to /tmp or %TEMP% under decoy filenames (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawn it detached via /bin/sh -c or cmd.exe. Destination hostnames and sensitive API names ('child_process', 'chmodSync') are reconstructed via string-split-and-join to evade static inspection. The main entry unconditionally require()s _support.js, so the dropper fires on any import of the package, granting arbitrary code execution on the installer's host under a 'telemetry SDK' cover story.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

2d354604a4226c4f6847ce621402caf3b48115d1cbbaa52916d547f1337c38f6

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 dolyame-ui-popupcarousel (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-popupcarousel across your stack and pipelines.

  2. If you installed it — respond

    Remove dolyame-ui-popupcarousel 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 dolyame-ui-popupcarousel 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-ui-popupcarousel 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-ui-popupcarousel on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016979

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-popupcarousel-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

dolyame-ui-popupcarousel (npm) malicious package — MAL-2026-13593 | O3 Security