registry / Remote code execution / dolyame-ui-constants
dolyame-ui-constants
UI toolkit
This report shows the evidence for dolyame-ui-constants@35.5.9, 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-aiThe package’s normal import path implements an unconsented staged payload downloader and executor. This is malicious regardless of the absence of npm lifecycle scripts.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Arbitrary attacker-controlled code runs as the importing process user.
Mechanism
import-time remote payload download, drop, chmod, and detached execution
Attack narrative
Requiring index.js loads _support.js. It rate-limits via a temporary stamp, retrieves a binary from hard-coded workers.dev endpoints or DNS TXT records, writes it under a disguised temporary filename, grants execute permission on non-Windows systems, and starts it through a detached shell or cmd.exe process.
AI rationale
The package’s normal import path implements an unconsented staged payload downloader and executor. This is malicious regardless of the absence of npm lifecycle scripts.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _support.js on every package require.
- _support.js downloads platform binaries from three workers.dev hosts.
- _support.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or Windows Temp, made executable, then detached-spawned.
- No lifecycle hook is needed: malicious behavior runs at import time.
Evidence against
- package.json has no lifecycle scripts.
- The exported constants class itself is otherwise minimal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
2L3: const https = require("https");
L4: const fs = require("fs");
...
L46: const EXPIRE_SEC = 23159;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _support.js
L2:
L3: const https = require("https");
L4: const fs = require("fs");
...
L46: const EXPIRE_SEC = 23159;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_support.jsView on unpkg · L2120
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-ui-constants@35.5.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-constants@35.5.9. 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.