dolyame-ui-progresscircle
This report shows the evidence for dolyame-ui-progresscircle@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-13510 confirms this npm version as malicious.
Advisory
MAL-2026-13510
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dolyame-ui-progresscircle (npm)
Details
The package's main entry unconditionally loads _ext.js, which on require/import downloads a platform-specific executable over HTTPS from hardcoded Cloudflare workers.dev hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT chunked fallback resolving to *.dl.wel1.ru, writes it to /tmp or %TEMP% under decoy names such as.cache_<uid> or dotnet_diag_<uid>.exe, chmods it 0755 on Unix, and spawns it detached via /bin/sh -c or cmd.exe /c start. Host names and sensitive API references (child_process, os.hostname, fs.chmodSync) are reassembled from split string arrays to evade static matching. lib/telemetry.js contains a redundant loader that base64-decodes embedded chunks, writes them to disk, chmods 0755, and detached-spawns the resulting binary. The package presents itself as a UI progress-circle / monitoring SDK but ships no functionality matching that description.
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-progresscircle@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-progresscircle@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.