What does the dolyame-ui-select malware do?

On require of the package, index.js loads _bridge.js, which reconstructs C2 hostnames from split string fragments (resolving to oob-worker.cf103-07.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf100-416.workers.dev), downloads a platform-specific binary from /pkg/package[.exe|-arm64|_mac], writes it to /var/tmp/.cache_ or %TEMP%\dotnet_diag_ .exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A DNS TXT covert channel over *.dl.wel1.ru (c. count + . base64 chunks) provides a fallback transport when HTTPS egress is blocked. Cover-story identifiers such as `analytics` and `dotnet_diag` disguise the payload, and a ~20455

Which versions of dolyame-ui-select are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-selectnpm

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

Malicious code in dolyame-ui-select (npm)

MAL-2026-13182

Immediate action

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

npm uninstall dolyame-ui-select

What this malware does

On require of the package, index.js loads bridge.js, which reconstructs C2 hostnames from split string fragments (resolving to oob-worker.cf103-07.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf100-416.workers.dev), downloads a platform-specific binary from /pkg/package[.exe|-arm64|mac], writes it to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A DNS TXT covert channel over *.dl.wel1.ru (c.<domain> count + <n>.<domain> base64 chunks) provides a fallback transport when HTTPS egress is blocked. Cover-story identifiers such as analytics and dotnet_diag disguise the payload, and a ~20455s persistence flag paces re-execution. A second, larger dropper variant with the same behavior ships as lib/telemetry.js (~81KB) under an analytics-sdk cover story, ready to be wired in.

Malicious versions

1 flagged

35.9.5

Indicators of compromise (SHA-256)

1d1d8b1348e86f0f476ab27b5d5cde1c6a4cfd519e74e526a82263c78a0aaf6b

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-select (version 35.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-select across your stack and pipelines.
If you installed it — respond
dolyame-ui-select 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-select 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-select 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-select on npm has been identified as a malicious package (version 35.9.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015594

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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