dolyame-ui-loadernpm
Advisory published Updated
dolyame-ui-loader is a confirmed malicious npm package (MAL-2026-13166) that executes malicious code on install (malicious version 35.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-loader (npm)
What this malware does
On require('dolyame-ui-loader'), index.js triggers shim.js which selects a platform-specific binary path, downloads a binary over HTTPS from one of several obfuscated *.workers.dev hosts (reassembled at runtime via string-array.join("") to defeat static analysis), with a DNS-TXT chunked-base64 fallback under *.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and executed detached via spawn("/bin/sh",...) or spawn("cmd",...). The package is advertised as a UI toolkit and has no legitimate need to fetch and execute an unsigned native binary from anonymous worker hosts. Cover-story identifiers ('analytics_state', 'dotnet_diag_', 'Cache validation') and telemetry-opt-out env-var gates (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) are used to disguise the dropper as benign telemetry.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for dolyame-ui-loader (version 35.1.5).
If you installed it — respond
Remove dolyame-ui-loader 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-loader was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-loader-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.