registry / dolyame-ui-skeleton / 35.2.5

dolyame-ui-skeleton@35.2.5

visual components

AI Security Review

scanned 10d ago · by lpm-firewall-ai

Importing the package automatically loads _vendor.js. It retrieves a platform-specific executable payload, stores it in a temporary directory, and starts it detached.

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 remote code executes under the importing user's account.

Mechanism

Remote payload download/DNS fallback followed by detached execution.

Attack narrative

The main entrypoint silently requires _vendor.js. On import, it fetches a platform-specific binary from obfuscated workers.dev hosts, falls back to DNS TXT payload reconstruction from .ru domains, writes the result to a temporary file, marks it executable on Unix, and spawns it detached. This is concrete remote code execution unrelated to a UI skeleton package.

Rationale

Source inspection confirms an import-time staged payload downloader and executor, not merely telemetry. No lifecycle hook is needed because index.js triggers it whenever the package is loaded.

Evidence

package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe

Network endpoints7

oob-worker.cf101-adf.workers.dev

Package advertises itself as a visual/UI components library but ships a load-time binary dropper. index.js unconditionally requires./_vendor.js, which on require() downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to a hidden cache path, chmods 0755, and spawns it detached via /bin/sh or cmd. Destination hostnames are reconstructed at runtime by joining string fragments (e.g. ["oob-worker.cf101-adf",".workers.dev"].join("") and ['sdk.dl.wel','1.r','u'].join("")) to evade static analysis. A fallback delivery path issues DNS TXT queries against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru (c.<domain> for chunk count, then N.<domain> for base64-encoded chunks), reassembles the chunks, and executes the resulting binary — a covert channel that bypasses HTTPS egress filtering. Filenames such as analytics_state, dotnet_diag_*.exe, and.cache_* serve as cover for the dropped payload. There is no legitimate need for a UI component package to fetch and execute native binaries, obfuscate its destinations, or use DNS TXT for content delivery.

dolyame-ui-skeleton@35.2.5

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code