dolyame-ui-inputautocompletenpm
dolyame-ui-inputautocomplete is a confirmed malicious npm package (MAL-2026-13574) 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-inputautocomplete (npm)
What this malware does
On require/import, bootstrap.js selects a platform-specific path (/pkg/package, /pkg/package.exe, /pkg/loader_mac, /pkg/package-arm64) and downloads an opaque native binary over HTTPS from author-controlled hosts whose names are reconstructed at runtime from string-split arrays: oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, and oob-worker.cf101-adf.workers.dev. A fallback path reassembles a base64 payload from enumerated DNS TXT records under sdk.dl.wel1.ru (c./0./1./... subdomain enumeration). The fetched bytes are written to /tmp/.cache<rnd> on Unix or %TEMP%/dotnet_diag_<rnd>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd. Any process that require()s the package immediately executes attacker-controlled native code with the installer's privileges; the string-splitting, filename masquerading as diagnostic caches, and DNS-TXT reassembly channel are active anti-analysis techniques rather than legitimate SDK behavior.
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-inputautocomplete (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-inputautocomplete across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputautocomplete 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-inputautocomplete 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-inputautocomplete 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-inputautocomplete-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.