dolyame-ui-inputcolornpm
dolyame-ui-inputcolor is a confirmed malicious npm package (MAL-2026-13507) 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-inputcolor (npm)
What this malware does
index.js unconditionally requires./loader on load. loader.js assembles attacker hostnames at runtime via array.join to hide them from static scanners (e.g., ["oob-w","orker",".cf","101-adf.workers.","de","v"].join("")), selects an OS-specific endpoint, and fetches a binary payload over HTTPS from one of four oob-worker.cf10[0-3]-*.workers.dev hosts. On HTTPS failure, it falls back to a DNS-TXT covert channel: it queries chunked TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, base64-concatenates the chunks, and reconstitutes the payload buffer. The bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmodded to 0755, and spawned detached via /bin/sh -c or cmd. Module names, API names, and hostnames are reconstructed via string concatenation and dynamic property access (require("child_" + "process"), fs["chmod" + "Sync"], os["host" + "name"]) to defeat plain-text matching. The dropper fires on every require() of this package, granting the operator of those hosts arbitrary code execution on any machine that installs or imports it.
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-inputcolor (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-inputcolor across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputcolor 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-inputcolor 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-inputcolor 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-inputcolor-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.