dolyame-ui-tagnpm
dolyame-ui-tag is a confirmed malicious npm package (MAL-2026-13191) that executes malicious code on install (malicious version 35.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-tag (npm)
What this malware does
On require of the package, index.js loads./ext, which downloads a platform-specific binary from Cloudflare Workers hosts assembled at runtime from split string fragments (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT covert-channel fallback via subdomains of dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched binary is written under a decoy name (dotnet_diag.exe on Windows,.cache_ on Unix) to %TEMP%/ /tmp, chmodded 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or cp.spawn('cmd.exe', ['/c','start','/b',fp]). A second dropper of the same shape is present in lib/telemetry.js and uses split identifiers (require('child_' + 'process'), fs['chmod' + 'Sync']) to evade static analysis. Hostname obfuscation, DNS-TXT fallback for HTTPS-blocked environments, decoy filenames, detached execution, and a bundled backup dropper are consistent with a supply-chain attack delivering attacker-controlled code to installer machines on any install or require of the package.
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-tag (version 35.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-tag across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-tag 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-tag 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-tag 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-tag-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.