dolyame-ui-buttonstore
This report shows the evidence for dolyame-ui-buttonstore@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-13554 confirms this npm version as malicious.
Advisory
MAL-2026-13554
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dolyame-ui-buttonstore (npm)
Details
dolyame-ui-buttonstore@35.8.1 is a dropper. index.js unconditionally requires setup.js on load, which selects a per-platform binary path, fetches opaque bytes over HTTPS from hosts whose names are assembled at runtime by joining split character arrays (resolved destinations include oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), writes them to a hidden file under /tmp or %TEMP% (e.g..cache_<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns the file detached via /bin/sh -c or cmd with stdio ignored. A DNS TXT-record fallback reassembles a base64 payload from subdomains under dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) when HTTPS fails. Package metadata claims 'Common TypeScript definitions' and the name mimics the 'dolyame' brand, but the tarball ships only the dropper plus a 76KB lib/telemetry.js sibling; author field is empty. The runtime-constructed destinations, hidden staging path, detached exec, and DNS-TXT fallback are intentional evasion.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The downloader-and-executor is concrete malware behavior disguised as analytics, but the package entrypoint appears blocked by a syntax error in lib/telemetry.js. Treat it as an inert staged payload carrier rather than a confirmed active import-time compromise.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Importing the package entrypoint; direct execution of setup.js would also activate it.
Impact
Arbitrary attacker-supplied native code execution.
Mechanism
remote binary download, drop, and detached execution
AI rationale
The downloader-and-executor is concrete malware behavior disguised as analytics, but the package entrypoint appears blocked by a syntax error in lib/telemetry.js. Treat it as an inert staged payload carrier rather than a confirmed active import-time compromise.
Evidence
index.jssetup.jslib/telemetry.jspackage.json/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.dev
Independent scan evidence
public snapshotAI called this Suspicious at 93.0% confidence as Malware with low false-positive risk.
Evidence for AI warning decision
- index.js imports setup.js on package import.
- setup.js fetches platform-specific binary payloads from obfuscated hosts.
- setup.js decodes DNS TXT payload fallback and writes it to /var/tmp or Windows Temp.
- setup.js chmods the payload and launches it detached via shell/child_process.
Evidence against
- package.json has no lifecycle hooks.
- lib/telemetry.js contains a duplicated class declaration, so index.js likely fails parsing before setup.js is reached.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L2727Trigger-reachable chain: manifest.main -> index.js -> lib/telemetry.js
L27:
L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
lib/telemetry.jsView on unpkg · L27491L492: fork() {
L493: const child = new Scope();
Findings
2 Critical2 High2 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitylib/telemetry.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to dolyame-ui-buttonstore@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-buttonstore@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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.