dolyame-ui-colorsnpm
dolyame-ui-colors is a confirmed malicious npm package (MAL-2026-13147) that executes malicious code on install (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-colors (npm)
What this malware does
[email protected] is advertised as a React UI color library but its main entry requires./shim.js on load, which acts as a platform-aware binary dropper. shim.js selects a platform-specific endpoint and fetches an opaque binary over HTTPS from one of four Cloudflare Workers hosts whose names are assembled at runtime by splitting and rejoining string fragments (e.g. "oob-worker.cf103-070.wo"+"rk"+"ers."+"dev"): oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev. A DNS-TXT covert-channel fallback reassembles a base64 payload from numbered TXT records under c.<domain> for the hosts sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmod 755'd, and spawned detached via spawn("/bin/sh", ["-c", fp+" &"], {detached:true}).unref() (or a cmd equivalent on Windows). A ~6.5-hour lock file throttles re-runs to reduce visibility. The stated React-component purpose is a cover story; the destinations, drop paths, and execution shape indicate deliberate supply-chain attack code.
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-colors (version 35.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-colors across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-colors 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-colors 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-colors 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-colors-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.