dolyame-ui-draghocnpm
dolyame-ui-draghoc is a confirmed malicious npm package (MAL-2026-13567) 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-draghoc (npm)
What this malware does
On require(), index.js loads loader.js which selects a platform-specific asset path, fetches an unsigned binary over HTTPS from hostnames reassembled at runtime via array joins (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), writes it to a hidden temp file (/tmp/.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. A DNS-TXT covert-channel fallback under sdk.dl.wel1.ru concatenates numbered TXT records and base64-decodes them into the payload buffer to bypass HTTP-URL blocklists. A parallel dropper exists in lib/telemetry.js reachable from the package's main entry, using dynamic property access (fs['chmod'+'Sync'], require('child_'+'process')) as anti-analysis obfuscation and following the same fetch->chmod->detached spawn pattern. No signature or hash verification is performed on the downloaded binary. The package advertises itself as core infrastructure utilities but ships only a binary retriever.
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-draghoc (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-draghoc across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-draghoc 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-draghoc 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-draghoc 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-draghoc-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.