Malicious code in dolyame-ui-inputcolor (npm)
The npm package dolyame-ui-inputcolor contained malicious code that executed on every require(), downloading and executing arbitrary binary payloads via HTTPS or DNS-TXT covert channels. The dropper used obfuscation techniques to evade static analysis and granted remote code execution to the attacker.
- Disclosed
- Last updated
- Blast radius
- Any system that installed or imported the malicious dolyame-ui-inputcolor package
- Ecosystems
- Attack vectors
- Affected entities
- dolyame-ui-inputcolornpm package containing malicious code
The npm package dolyame-ui-inputcolor was found to contain malicious code in its index.js file. Upon loading, the package unconditionally requires a hidden _loader.js module that assembles attacker-controlled hostnames at runtime using array.join() to evade static scanners.
The _loader.js module fetches binary payloads over HTTPS from four oob-worker.cf10[0-3]-*.workers.dev hosts. If HTTPS fails, it falls back to a DNS-TXT covert channel, querying chunked records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, then base64-concatenating the chunks to reconstitute the payload.
The downloaded payload is written to /tmp or %TEMP% under disguised names (.cache_ on Unix, dotnet_diag_.exe on Windows), made executable (chmod 0755), and spawned detached via /bin/sh -c or cmd. The malicious code uses string concatenation and dynamic property access to reconstruct module names, API calls, and hostnames, defeating plain-text pattern matching.
The dropper executes on every require() of the package, granting the attacker arbitrary code execution on any machine that installs or imports it. The incident was identified and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- dolyame-ui-inputcolor
- Domains
- oob-worker.cf101-adf.workers.dev
- sdk.dl.wel1.ru
- ext.dl.wel1.ru
- pkg.dl.wel1.ru
- net.dl.wel1.ru
Remediation
- Immediately uninstall dolyame-ui-inputcolor from all systems
- Audit all systems that previously installed or imported this package for signs of compromise
- Review process execution logs and network connections for activity to the identified domains (oob-worker.cf10[0-3]-*.workers.dev, sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru)
- Check /tmp and %TEMP% directories for suspicious files matching patterns .cache_* or dotnet_diag_*.exe
- Update npm dependencies and verify no other malicious packages are present
- Consider re-imaging affected systems if compromise is suspected
Sources
- GitHub Advisory GHSA-2h8h-gwgx-mwxw · GitHub Advisory Database
Cite this entry
"Malicious code in dolyame-ui-inputcolor (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-dolyame-ui-inputcolor-npm-1jgy7g
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package