What does the dolyame-ui-inputrange malware do?

On require of dolyame-ui-inputrange, _init.js reconstructs a rotating list of Cloudflare Workers hostnames via split-string joins (e.g. ["oob-worke","r.cf101-adf.workers.de","v"].join("")) plus a DNS-TXT fallback under *.dl.wel1.ru, downloads a platform-specific binary, writes it to /tmp or %TEMP% under disguised names (.cache_ , dotnet_diag_ .exe), sets mode 0755 via bracket-property assembly (fs["chmod"+"Sync"]), and spawns it detached via cp.spawn("/bin/sh", ["-c", filePath+" &"], {detached:true}).unref(). No native source is shipped in the tarball and the fetched bytes are opaque. lib/telemetry.js, re-exported by the package's main entry, duplicates the same dropper primitives (b

Which versions of dolyame-ui-inputrange are malicious?

The following npm versions of dolyame-ui-inputrange are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate dolyame-ui-inputrange if I installed it?

Remove dolyame-ui-inputrange 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.

I already installed dolyame-ui-inputrange — how do I know if it already compromised me?

If dolyame-ui-inputrange 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.

Is dolyame-ui-inputrange part of a known attack campaign?

Yes — dolyame-ui-inputrange is associated with the IN-MAL-2026-016997 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-ui-inputrange across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputrange (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-inputrange across your stack and pipelines.

Malicious package

dolyame-ui-inputrangenpm

dolyame-ui-inputrange is a confirmed malicious npm package (MAL-2026-13581) 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-inputrange (npm)

MAL-2026-13581

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-ui-inputrange

What this malware does

On require of dolyame-ui-inputrange, init.js reconstructs a rotating list of Cloudflare Workers hostnames via split-string joins (e.g. ["oob-worke","r.cf101-adf.workers.de","v"].join("")) plus a DNS-TXT fallback under *.dl.wel1.ru, downloads a platform-specific binary, writes it to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), sets mode 0755 via bracket-property assembly (fs["chmod"+"Sync"]), and spawns it detached via cp.spawn("/bin/sh", ["-c", filePath+" &"], {detached:true}).unref(). No native source is shipped in the tarball and the fetched bytes are opaque. lib/telemetry.js, re-exported by the package's main entry, duplicates the same dropper primitives (base64-decoded chunks written to disk, chmod 755, /bin/sh -c spawn) behind an "Analytics SDK" cover story, ensuring execution persists even if init.js is stripped. Runtime string reassembly of module names (require("child"+"process")) and destination hosts, plus opt-out env-var gates (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a TTL cache file, are used to evade static analysis and hide repeat executions.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

aae096235cf72db7f2e9908e53fa5a6e7c87718539a9e3452e0e34f7345ca80f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputrange (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-inputrange across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputrange 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-inputrange 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-inputrange 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

No. dolyame-ui-inputrange on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016997

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-inputrange-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database