dolyame-ui-inputsearchnpm
dolyame-ui-inputsearch is a confirmed malicious npm package (MAL-2026-13582) that typosquats a legitimate package to trick installs (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-inputsearch (npm)
What this malware does
[email protected] is a dropper disguised as a UI input search component. On require, index.js loads./vendor.js, which assembles a mirror list of Cloudflare workers.dev endpoints (oob-worker.cf103-070.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev) from string-concatenation-split literals, with a DNS-TXT fallback resolving base64-encoded download data via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. A platform-specific binary is downloaded, written to a hidden path (/var/tmp/.cache<hex> on Unix, TEMP/dotnet_diag_<hex>.exe on Windows), chmod 0755 on Unix, then spawned detached via /bin/sh -c or cmd. Endpoints and filenames are split-literal obfuscated and gated behind cover-story flags named analytics_state and DISABLE_TELEMETRY, and the dropped filename impersonates.NET diagnostics tooling. The purpose of the fetched binary is opaque; the delivery mechanism has no hash or signature verification, no pinning, and no publisher-matched host. The purpose (dropper of an anonymous remote binary) is unrelated to the advertised UI input search functionality.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputsearch (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-inputsearch across your stack and pipelines.
If you installed it — respond
dolyame-ui-inputsearch is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-inputsearch, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-ui-inputsearch 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-inputsearch 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-inputsearch-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.