Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in dolyame-ui-tableinline (npm)

The npm package dolyame-ui-tableinline contained malicious code that executes arbitrary native binaries on installation. The package downloads platform-specific executables from obfuscated Cloudflare Workers mirrors and executes them with full system privileges, enabling remote code execution on any machine that installs or imports it.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system installing or importing the dolyame-ui-tableinline package
Ecosystems
Attack vectors
Affected entities
  • dolyame-ui-tableinlinenpm package containing malicious code

The npm package dolyame-ui-tableinline was found to contain malicious code that achieves full-host remote code execution. Upon requiring the package, index.js loads init.js which fetches platform-specific native binaries from obfuscated Cloudflare Workers mirrors. Hostnames are reconstructed at runtime using string-array.join("") to evade static detection, with a DNS TXT-record fallback to sdk.dl.wel1.ru.\n\nThe downloaded binary is written to a disguised path under /tmp or %TEMP% (e.g., dotnet_diag.exe, .cache_), given execute permissions (chmod 0755 on POSIX), and spawned detached via /bin/sh -c or cmd /c start /b. A TTL marker file is used to rate-limit re-execution. A second dropper mechanism (base64 buffer decoded, chmod 755, spawned via /bin/sh -c) is duplicated in lib/telemetry.js, the declared main module, wrapped in a fake SDK scaffold.\n\nThe attack uses camouflage techniques including opt-out environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and cover-story file names (dotnet_diag_*, .analytics_state) to disguise malicious activity. The unpinned opaque native payloads, anonymous author-controlled hosts, obfuscated destination reconstruction, and detached background execution constitute a complete compromise vector for any machine that installs or imports the package.\n\nThe incident was identified and credited to the OpenSSF malicious-packages project.

Indicators of compromise

Packages
  • dolyame-ui-tableinline
Domains
  • sdk.dl.wel1.ru

Remediation

  • Immediately uninstall dolyame-ui-tableinline from all systems
  • Audit npm package.json and lock files for any dependency on dolyame-ui-tableinline
  • Scan systems that installed this package for suspicious processes, network connections, and files in /tmp or %TEMP% directories matching patterns like dotnet_diag_* or .cache_*
  • Review system logs for unexpected child process spawning via /bin/sh or cmd.exe
  • Consider full system forensics and credential rotation on affected machines
  • Update npm dependencies and use npm audit to identify similar malicious packages

Sources

  1. GitHub Advisory GHSA-vj97-3mjp-3ggc · GitHub Advisory Database

Cite this entry

"Malicious code in dolyame-ui-tableinline (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-dolyame-ui-tableinline-npm-13ylji

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. activecritical

    Malware in @ai-vertical/ai-agent

    Malware was discovered in the npm package @ai-vertical/ai-agent. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

    npmAI agents & skillsCompromised package
  2. resolvedcritical

    Malicious code in depcruise-wrap-stream-in-html (npm)

    depcruise-wrap-stream-in-html@99.9.1 is a malicious npm package that mimics an internal helper of dependency-cruiser. It is a hollow package that downloads and executes arbitrary code from a Google Cloud Storage bucket during installation.

    npmCompromised packageDependency confusionTyposquatting
  3. containedcritical

    Malicious code in akamaijs-sensor (npm)

    The npm package akamaijs-sensor contained malicious code that executed arbitrary JavaScript via hidden Unicode-encoded bytes and established a command-and-control channel through a Google Calendar dead-drop. The package was designed to run attacker-authored code in the consumer's Node process when the sensor() API was called.

    npmCompromised packageMalicious commit
  4. containedcritical

    Malicious code in gunzip-js (npm)

    The npm package gunzip-js version 99.9.1 was identified as malicious by the OpenSSF Package Analysis project. The malicious version communicates with a domain associated with malicious activity.

    npmCompromised package