Malicious code in dolyame-ui-inputrange (npm)
The npm package dolyame-ui-inputrange contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure. The package employed obfuscation techniques including string reassembly, DNS-TXT fallbacks, and environment variable gates to evade detection.
- Disclosed
- Last updated
- Blast radius
- Any npm consumer of dolyame-ui-inputrange
- Ecosystems
- Attack vectors
- Affected entities
- dolyame-ui-inputrangenpm package containing malicious code
The npm package dolyame-ui-inputrange was found to contain malicious code in its _init.js and lib/telemetry.js modules. Upon require, the package reconstructs Cloudflare Workers hostnames through string concatenation (e.g., joining split strings like ["oob-worke","r.cf101-adf.workers.de","v"]) and uses DNS-TXT lookups under *.dl.wel1.ru as a fallback mechanism.
The malicious code downloads platform-specific binaries from these attacker-controlled hosts and writes them to temporary directories (/tmp on Unix, %TEMP% on Windows) under disguised filenames such as .cache_ or dotnet_diag_.exe. The files are then made executable via chmod 0755 and spawned detached using /bin/sh -c, ensuring execution persists in the background.
The package employs multiple evasion techniques: runtime string reassembly of module names (e.g., require("child_"+"process")), opt-out environment variable gates (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK), and TTL-based caching to avoid repeated downloads. The telemetry module duplicates the same dropper primitives, ensuring execution even if _init.js is removed.
No legitimate native source code is included in the tarball; all downloaded binaries are opaque and attacker-controlled. The incident was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- dolyame-ui-inputrange
- Domains
- dl.wel1.ru
- cf101-adf.workers.de
Remediation
- Immediately remove dolyame-ui-inputrange from all projects and dependencies
- Audit npm package.json and lock files for any presence of dolyame-ui-inputrange
- Review process execution logs and network connections for suspicious activity from /tmp or %TEMP% directories
- Check for environment variables DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, or DO_NOT_TRACK that may have been set to mask execution
- Scan systems for binaries with disguised names (.cache_, dotnet_diag_.exe) in temporary directories
- Monitor DNS queries to *.dl.wel1.ru and connections to Cloudflare Workers subdomains (*.workers.de)
- Update npm packages and use npm audit to identify and remove malicious dependencies
- Consider using npm package integrity verification and allowlist policies to prevent similar packages
Sources
- GitHub Advisory GHSA-v43c-jqwv-832q · GitHub Advisory Database
Cite this entry
"Malicious code in dolyame-ui-inputrange (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-inputrange-npm-1pici4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package