Which versions of dolyame-ui-group are malicious?

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

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

Remove dolyame-ui-group 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.

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

If dolyame-ui-group 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.

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

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-group (version 35.9.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-group across your stack and pipelines.

Malicious package

dolyame-ui-groupnpm

dolyame-ui-group is a confirmed malicious npm package (MAL-2026-13158) that executes malicious code on install (malicious version 35.9.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-group (npm)

MAL-2026-13158

Immediate action

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

npm uninstall dolyame-ui-group

What this malware does

On require() of the package's main entry, loader.js runs a platform-detecting downloader that fetches an executable from obfuscated hostnames reconstructed at runtime via array-join splits (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT covert-channel fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. The downloaded bytes are written to a temp path with cover-story names (dotnet_diag<rand>.exe on Windows,.cache_<rand> on POSIX), chmod 0755, and spawned detached via /bin/sh -c or cmd. A second co-shipped dropper module lib/telemetry.js, styled as an analytics SDK, contains the same base64-decode -> write -> chmod 755 -> spawn("/bin/sh", ["-c", filePath+" &"]) chain. Sensitive API names are hidden via string concatenation (require("child_"+"process"), fs["chmod"+"Sync"], os"host"+"name") to defeat static grep. Fetch-and-execute of an opaque, unversioned, non-publisher binary from anonymous workers.dev infrastructure at library-load time is arbitrary code execution on the installer's host.

Malicious versions

1 flagged

35.9.7

Indicators of compromise (SHA-256)

714598919807b4143a734772e690ff94aa986fb6cf61bd99026e7f7bc93f4cf2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-group (version 35.9.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-group across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-group 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-group 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-group 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

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

Campaign

IN-MAL-2026-015617

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-group-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