Which versions of dolyame-ui-selectaccount are malicious?

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

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

dolyame-ui-selectaccount 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-selectaccount — how do I know if it already compromised me?

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

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

Malicious package

dolyame-ui-selectaccountnpm

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

Malicious code in dolyame-ui-selectaccount (npm)

MAL-2026-13598

Immediate action

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

npm uninstall dolyame-ui-selectaccount

What this malware does

On require() of the package, index.js loads bootstrap.js and the main-exported lib/telemetry.js, both of which implement the same download-and-execute dropper. The code selects a platform-tagged asset path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe) and fetches it from string-split, obfuscated hostnames of the form oob-worker.cf1XX-XXX.workers.dev, with a DNS-TXT chunked-base64 fallback over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp or the Windows TEMP directory under disguised names (.cache<rand> or dotnet_diag_<rand>.exe), chmodded to 0755 via fs["chmod"+"Sync"], and spawned detached with stdio ignored via cp.spawn("/bin/sh", ["-c", filePath + " &"], { detached: true, stdio: "ignore" }).unref() or cmd.exe /c start /b. Dangerous API names are assembled at runtime by string concatenation (require("child_" + "process")) and the destination hostnames are reconstructed with Array.join to hide the C2 from static inspection. The 'Analytics SDK' / 'telemetry' framing does not correspond to the code's actual behavior, which is unconditional retrieval and execution of an attacker-controlled native binary on the installer's host at import time. No integrity check, pinning, or signature verification is performed on the downloaded payload.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

4974c35a90cc1879876080c49f8fafc0f9be576e04e19597d364b55daa951363

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-selectaccount (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-selectaccount across your stack and pipelines.
If you installed it — respond
dolyame-ui-selectaccount 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-selectaccount 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-selectaccount 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-selectaccount 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-016966

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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