Which versions of dolyame-ui-label are malicious?

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

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

dolyame-ui-label establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

Yes — dolyame-ui-label is associated with the IN-MAL-2026-015612 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-label 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-label (version 35.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-label across your stack and pipelines.

Malicious package

dolyame-ui-labelnpm

dolyame-ui-label is a confirmed malicious npm package (MAL-2026-13162) that opens a backdoor for remote access (malicious version 35.7.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-label (npm)

MAL-2026-13162

Immediate action

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

npm uninstall dolyame-ui-label

What this malware does

dolyame-ui-label 35.7.8 is not a UI component library. On require() of the package, index.js loads helpers.js, which reconstructs C2 hostnames at runtime from split-string arrays (e.g. ["oob","-worker.cf102-baf.workers.dev"].join("") and ['sdk.dl.wel','1.','ru'].join("")) to evade static inspection. It selects a platform-specific endpoint among oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, and oob-worker.cf103-070.workers.dev, with a DNS-TXT base64 fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, downloads a native binary via https.get, writes it to /tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Cover-story comments frame the traffic as analytics/telemetry/CDN. The package's declared purpose (UI labels) has no legitimate need for a native binary drop, and the destinations are unrelated to any documented publisher, unpinned, and unverified.

Malicious versions

1 flagged

35.7.8

Indicators of compromise (SHA-256)

bdcede6d4d42bfed7f10577346b24e9af22655e50f8d454baab6f4999e6020f3

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-label (version 35.7.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-label across your stack and pipelines.
If you installed it — respond
dolyame-ui-label establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dolyame-ui-label 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-label 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-label on npm has been identified as a malicious package (version 35.7.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015612

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-label-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database