dolyame-ui-inputsearchtaggednpm
dolyame-ui-inputsearchtagged is a confirmed malicious npm package (MAL-2026-13583) 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-inputsearchtagged (npm)
What this malware does
On require of the package, init.js selects a platform-specific payload, downloads opaque bytes over HTTPS from a rotating set of anonymous Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a fallback covert channel using DNS TXT lookups against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru to reassemble a base64 payload. The downloaded bytes are written to /var/tmp/.cache<hex> on Linux or %TEMP%/dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via spawn("/bin/sh") or spawn("cmd"). Hostnames are constructed from split-string arrays joined at runtime to evade static analysis, and file names (.cache_<hex>, dotnet_diag_<hex>.exe, /tmp/.analytics_state) plus DISABLE_TELEMETRY/DO_NOT_TRACK env checks are used as a telemetry cover story. There is no pinning, no integrity check, and the destinations are unrelated to any legitimate publisher; installing or importing the package results in full-host code execution under attacker control.
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-inputsearchtagged (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-inputsearchtagged across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputsearchtagged 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-inputsearchtagged 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-inputsearchtagged 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-inputsearchtagged-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.