Which versions of dolyame-ui-popover are malicious?

The following npm versions of dolyame-ui-popover are flagged malicious: 35.8.7. Treat any of these as compromised.

How do I remediate dolyame-ui-popover if I installed it?

dolyame-ui-popover 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.

I already installed dolyame-ui-popover — how do I know if it already compromised me?

If dolyame-ui-popover 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.

Is dolyame-ui-popover part of a known attack campaign?

Yes — dolyame-ui-popover is associated with the IN-MAL-2026-015598 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-ui-popover across my projects, lockfiles, and CI pipelines?

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

Malicious package

dolyame-ui-popovernpm

dolyame-ui-popover is a confirmed malicious npm package (MAL-2026-13174) that opens a backdoor for remote access (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-popover (npm)

MAL-2026-13174

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-ui-popover

What this malware does

On require() of the package, index.js loads ext.js which selects an OS/arch-specific endpoint and downloads a binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT chunked base64 fallback under *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under deceptive filenames (.cache<hex>, dotnet_diag_<hex>.exe,.analytics_state), chmodded 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. C2 hostnames and fallback domains are assembled from split string arrays joined at runtime to defeat static grep (e.g. ["oob-worker.cf1","00-416.workers.dev"].join("") and ['sdk','.dl.wel1','.r','u'].join("")). A cache-stamp guard prevents re-execution. A co-shipped lib/telemetry.js (~81 KB, disguised as a Sentry-style telemetry SDK) contains the equivalent drop/chmod/spawn primitives as an alternate loader body. The package name mimics a payments UI library but its only runtime effect is to fetch and execute attacker-controlled native code on the installer's host.

Malicious versions

1 flagged

35.8.7

Indicators of compromise (SHA-256)

5ed3996792c8c70963eee2871d056f13b90e873087ff77be677c7cb359058b9f

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-popover (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-popover across your stack and pipelines.
If you installed it — respond
dolyame-ui-popover 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.
Did it already run?
If dolyame-ui-popover 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.
How O3 protects you
O3 blocks dolyame-ui-popover 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-popover on npm has been identified as a malicious package (version 35.8.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015598

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-popover-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database