NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dolyame-ui-stateutilsnpm

Advisory published Updated

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
  1. Find it

    Search your lockfiles and build artifacts for dolyame-ui-stateutils (version 35.8.1).

  2. 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.

  3. Did it already run?

    If dolyame-ui-stateutils was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

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.

Explore

dolyame-ui-stateutils (npm) malicious package — MAL-2026-13511 | O3 Security