dolyame-ui-stateutils
This report shows the evidence for dolyame-ui-stateutils@35.8.1, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13511 confirms this npm version as malicious.
Advisory
MAL-2026-13511
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dolyame-ui-stateutils (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to dolyame-ui-stateutils@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-stateutils@35.8.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.