dolyame-ui-group
visual components
This report shows the evidence for dolyame-ui-group@35.9.7, 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.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time staged-payload execution chain unrelated to the advertised UI toolkit. It enables an attacker controlling the endpoints or DNS records to execute arbitrary code.
Decision evidence
public snapshot- index.js imports _loader.js on every package require.
- _loader.js downloads platform payloads from four workers.dev hosts.
- _loader.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded data is written under /var/tmp or Windows Temp, chmodded, then spawned detached.
- No payload hash/signature is verified despite the integrity comment.
- lib/telemetry.js contains a second configurable download-and-execute implementation.
- package.json has no lifecycle scripts.
- The public UI class itself is minimal; malicious execution is hidden in its import side effect.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to dolyame-ui-group@35.9.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-group@35.9.7. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.