dolyame-ui-islandnpm
dolyame-ui-island is a confirmed malicious npm package (MAL-2026-13161) that typosquats a legitimate package to trick installs (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-island (npm)
What this malware does
On require() of dolyame-ui-island, index.js loads setup.js which downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT base64 fallback channel across numbered subdomains of wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). Hostnames are assembled at runtime via array.join() to defeat static analysis. The fetched bytes are written to a randomized tmp path mimicking a diagnostic tool (/var/tmp/.cache_<hex> or dotnet_diag_<hex>.exe), chmodded to 0755 on POSIX, and spawned detached via cp.spawn("/bin/sh",["-c",fp+" &"],{detached:true}).unref(). Cover-story comments in setup.js reference 'analytics_state' and 'Content-type negotiation'. The package name impersonates a payments-UI library, but the shipped code has no such 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-island (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-island across your stack and pipelines.
If you installed it — respond
dolyame-ui-island is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-island, 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-island 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-island 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-island-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.