dolyame-ui-iconloaderhocnpm
dolyame-ui-iconloaderhoc is a confirmed malicious npm package (MAL-2026-13505) 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-iconloaderhoc (npm)
What this malware does
On require() of the package's main entry, [email protected] executes two dropper paths that fetch platform-specific binaries from hardcoded Cloudflare workers.dev endpoints (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel via subdomains of dl.wel1.ru, write the bytes to /var/tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod them to 0755, and spawn them detached via /bin/sh -c or cmd.exe. Both compat.js and lib/telemetry.js implement the fetch-write-chmod-spawn chain; lib/telemetry.js additionally assembles the payload from base64 chunks. Sinks and hostnames are constructed via array.join('') string-splitting (e.g. ['sdk.dl.','wel1.','ru'].join(''), require('child' + 'process'), fs['chmod'+'Sync']) to defeat static scanners, while comments frame the behavior as analytics/telemetry. The delivered bytes are opaque, unpinned, and unverified, and the workers.dev / wel1.ru destinations are anonymous infrastructure unrelated to any documented publisher.
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-iconloaderhoc (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-iconloaderhoc across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-iconloaderhoc 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-iconloaderhoc 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-iconloaderhoc 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-iconloaderhoc-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.