Which versions of dolyame-ui-radio are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-radionpm

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

Malicious code in dolyame-ui-radio (npm)

MAL-2026-13177

Immediate action

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

npm uninstall dolyame-ui-radio

What this malware does

[email protected] is a dropper disguised as a UI/telemetry package. index.js unconditionally require()s./adapter.js, which on module load downloads a platform-specific binary from string-split-obfuscated Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with DNS-TXT fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under masquerading names (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmod 0755'd, and spawned detached via /bin/sh -c or cmd. Destination hostnames are assembled from split-and-joined string fragments; cache paths and opt-out env-var names (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK,.analytics_state) present a telemetry cover story that does not match the observed drop-and-exec behavior. A second copy of the same drop-and-exec logic (base64 chunk assembly, chmodSync 0755, spawn /bin/sh) is bundled in lib/telemetry.js, unreached in this version's import graph but shipped in the tarball. Any require() or import of this package executes attacker-controlled native code on the installer's host.

Malicious versions

1 flagged

35.2.2

Indicators of compromise (SHA-256)

49a775fc526a9d050f679466553ee679e1c85046f8122fd93c07efe0af0a28cd

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

Campaign

IN-MAL-2026-015600

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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