registry / Remote code execution / dolyame-ui-clickable
dolyame-ui-clickable
visual components
This report shows the evidence for dolyame-ui-clickable@35.6.2, 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 import-time execution chain is directly present in source and downloads then launches untrusted remote content. No lifecycle hook is required for the package to execute the payload when used.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary attacker-supplied native code can execute under the importing process user.
Mechanism
Remote payload download, temporary-file drop, chmod, and detached shell execution.
Attack narrative
The public entrypoint silently loads _init.js during import. That code selects a platform payload endpoint, retrieves a binary from obfuscated Workers hosts or DNS TXT records, writes it to a temporary path, makes it executable on Unix, and starts it detached through a shell or cmd.exe. This is a concrete remote-code-execution chain without user action beyond importing the package.
AI rationale
The import-time execution chain is directly present in source and downloads then launches untrusted remote content. No lifecycle hook is required for the package to execute the payload when used.
Evidence
package.jsonindex.js_init.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devsdk.dl.wel1.ruext.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 ./_init on every package import.
- _init.js downloads platform-specific binary content over HTTPS or DNS TXT.
- _init.js writes the downloaded payload to /var/tmp or Windows Temp, chmods it, then launches it detached.
- Remote hosts and .ru DNS payload domains are obfuscated with string concatenation.
- Package manifest has no declared dependency or feature justifying the import-time downloader.
Evidence against
- package.json contains no npm lifecycle scripts.
- _init.js has telemetry opt-out environment checks, but they do not make execution user-invoked.
- lib/telemetry.js is not imported by the public entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_init.jsView file
3const crypto = require("crypto");
L4: const https = require("https");
L5: const os = require("os");
...
L48: const TTL = 22802;
L49: const _l = (...a) => process.stderr.write("");
L50:
...
L62: const isWin = _p("platform") === "win32";
L63: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L64: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L96: try {
L97: require("dns").resolveTxt(d, (e, rr) => {
L98: if (e || !rr || !rr.length) return r("");
Critical
3Trigger-reachable chain: manifest.main -> index.js -> _init.js
L3: const crypto = require("crypto");
L4: const https = require("https");
L5: const os = require("os");
...
L48: const TTL = 22802;
L49: const _l = (...a) => process.stderr.write("");
L50:
...
L62: const isWin = _p("platform") === "win32";
L63: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L64: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L96: try {
L97: require("dns").resolveTxt(d, (e, rr) => {
L98: 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.
_init.jsView on unpkg · L3124
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_init.js
CriticalTrigger Reachable Dangerous Capability_init.js
HighChild Process_init.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-ui-clickable@35.6.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-clickable@35.6.2. 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.