Which versions of dolyame-ui-controlgroup are malicious?

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

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

dolyame-ui-controlgroup is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-controlgroup, 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-controlgroup — how do I know if it already compromised me?

If dolyame-ui-controlgroup 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-controlgroup part of a known attack campaign?

Yes — dolyame-ui-controlgroup is associated with the IN-MAL-2026-017016 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-controlgroup 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-controlgroup (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-controlgroup across your stack and pipelines.

Malicious package

dolyame-ui-controlgroupnpm

dolyame-ui-controlgroup is a confirmed malicious npm package (MAL-2026-13563) that typosquats a legitimate package to trick installs (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-controlgroup (npm)

MAL-2026-13563

Immediate action

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

npm uninstall dolyame-ui-controlgroup

What this malware does

On require() of dolyame-ui-controlgroup, _compat.js selects a per-OS/arch URL and downloads a native binary from string-split-obfuscated hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-over-TXT fallback under sdk.dl.wel1.ru, writes it to a temp file with a hidden/randomized name (dotnet-diag-lookalike), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. The declared main lib/telemetry.js duplicates the dropper via a base64-decoded buffer written to disk, chmod 755, and /bin/sh -c spawn, so the payload fires from the main module even if the _compat require is removed. Hostnames and dangerous API identifiers (child_process, chmodSync) are assembled at runtime via .join("") and dynamic property access to evade string search. The download hosts, endpoints, and destination filenames are unrelated to the package's advertised monitoring/observability purpose.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

099af2a758510302726d266aeefb46cb91473a6a42c9484e068f465ea1509e84

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-controlgroup (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-controlgroup across your stack and pipelines.
If you installed it — respond
dolyame-ui-controlgroup is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-controlgroup, 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-controlgroup 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-controlgroup 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-controlgroup on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017016

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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