dolyame-ui-popupnpm
dolyame-ui-popup is a confirmed malicious npm package (MAL-2026-13175) that executes malicious code on install (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-popup (npm)
What this malware does
On require('dolyame-ui-popup'), index.js loads helpers.js which immediately fetches a platform-specific binary from string-split Cloudflare Workers mirrors (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT fallback across sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes it to a hidden path under /tmp or the Windows temp directory (.cache<hex>, dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. No hash or signature verification is performed and the destinations are assembled from split string fragments (['sdk.dl.w','el1.ru'].join(''); require('child_'+'process'); fs['chmod'+'Sync']) to defeat static analysis. lib/telemetry.js contains a second, structurally identical dropper labeled as an analytics SDK, using base64-over-DNS chunk assembly. The package advertises UI popup components but ships no UI code — the tarball's only effect on installation is fetching and executing an unverified remote binary under an attacker-controlled domain.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-popup (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-popup across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-popup 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.
Did it already run?
If dolyame-ui-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.
How O3 protects you
O3 blocks dolyame-ui-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-popup-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.