Which versions of dolyame-ui-mediainfohoc are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-mediainfohocnpm

dolyame-ui-mediainfohoc is a confirmed malicious npm package (MAL-2026-13588) 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-mediainfohoc (npm)

MAL-2026-13588

Immediate action

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

npm uninstall dolyame-ui-mediainfohoc

What this malware does

On require of the package, platform.js selects a platform-specific asset, downloads an opaque binary from one of three hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, cf101-adf, cf103-070) with a DNS-TXT fallback resolution via *.dl.wel1.ru subdomains (pkg.dl.wel1.ru, ext.dl.wel1.ru, net.dl.wel1.ru), writes it to /tmp or %TEMP% under a hidden dotfile or.exe name, chmods it 0755, and spawns it detached via /bin/sh -c '<path> &' or cmd.exe /c start. Host strings are split across.join() arrays and API names are concatenated ("chmod"+"Sync", "child"+"process") to evade static matching; comments falsely label the behavior as 'telemetry'. A duplicate dropper is embedded in lib/telemetry.js (the package main) wrapped in a fake Sentry-style analytics SDK, decoding a base64 buffer, writing it to disk, chmod 0755, and spawning /bin/sh -c '<path> &' — reachable via require('dolyame-ui-mediainfohoc') even if _platform.js is not directly loaded. The package name mimics an unrelated UI helper but ships two independent copies of the same fetch-and-execute backdoor.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

e5c5b48487d5c9507487229c44557753bf7a95300242096be119eba5df451adf

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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