Which versions of dolyame-ui-island are malicious?

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

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

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.

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

If dolyame-ui-island was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — dolyame-ui-island is associated with the IN-MAL-2026-015616 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-island across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-ui-island (version 35.7.4).

Malicious package

dolyame-ui-islandnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-13161

Immediate action

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

npm uninstall dolyame-ui-island

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

1 flagged

35.7.4

Indicators of compromise (SHA-256)

4668c9441e4f15054a71b066764259aac91f52c51e48ff2656a63c9a09f96e5d

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for dolyame-ui-island (version 35.7.4).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015616

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database