Which versions of dolyame-ui-focusstatehoc are malicious?

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

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

dolyame-ui-focusstatehoc is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

dolyame-ui-focusstatehocnpm

dolyame-ui-focusstatehoc is a confirmed malicious npm package (MAL-2026-13570) that steals credentials and exfiltrates sensitive data (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-focusstatehoc (npm)

MAL-2026-13570

Immediate action

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

npm uninstall dolyame-ui-focusstatehoc

What this malware does

On require of the package's main entry (index.js), compat.js and lib/telemetry.js run a bootstrap routine that downloads a platform-specific binary (linux_x64, linux_arm64, darwin, win32.exe) from a shuffled list of obfuscated Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev), with a DNS-TXT fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The binary is written to /tmp or %TEMP% under a disguised name (.cache<hex> on unix, dotnet_diag_<hex>.exe on Windows), chmod 755, and spawned detached via cp.spawn("/bin/sh", ["-c", filePath + " &"], {detached:true, stdio:"ignore"}).unref(). No version pinning, no hash or signature verification. Destination hosts and sensitive API names are reconstructed at runtime via string-split concatenation (e.g. ["oob-worker.cf100-416.w","orkers.dev"].join(""), require("child_"+"process"), fs["chmod"+"Sync"], os"host"+"name") to evade static string matching. The behavior is framed with an 'analytics/telemetry' cover story and opt-out env vars. lib/telemetry.js additionally assembles a base64-encoded payload (Buffer.from(chunks, "base64")) and executes it via the same spawn/chmod chain, providing a second load-time RCE path.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

98b117a5b8b618c0597bcc422e68216cd3626389417aec2940febf447c033a88

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-focusstatehoc (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-focusstatehoc across your stack and pipelines.
If you installed it — respond
dolyame-ui-focusstatehoc is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dolyame-ui-focusstatehoc 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-focusstatehoc 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-focusstatehoc 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-017009

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database