Which versions of dolyame-ui-stateutils are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-stateutilsnpm

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

Malicious code in dolyame-ui-stateutils (npm)

MAL-2026-13511

Immediate action

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

npm uninstall dolyame-ui-stateutils

What this malware does

On require()/import, index.js loads loader.js which fetches an opaque platform-specific binary from one of three obfuscated Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64 fallback distribution channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The payload is written to /tmp or %TEMP% under names disguised as system tooling (dotnet_diag<hex>.exe,.cache_<hex>), chmodded 0755 on POSIX, and detached-spawned via /bin/sh -c or cmd.exe. Both the Workers hostnames and the DNS resolver domains are assembled at runtime via.join("") over fragmented string arrays to evade static analysis. Package.json describes the package as a 'Monitoring and observability SDK' and offers DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK environment gates, but the package name (dolyame-ui-stateutils) is unrelated to any monitoring product and the cover story does not correspond to the actual on-import behavior. A rate-limiting cache is kept at /tmp/.analytics_state to throttle re-fetches.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

cdcb488491701865d9106e75e576785ff3b4f1d9687e456eb69f1ff69d8a393f

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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