Which versions of dolyame-ui-table are malicious?

The following npm versions of dolyame-ui-table are flagged malicious: 35.5.4. Treat any of these as compromised.

How do I remediate dolyame-ui-table if I installed it?

Remove dolyame-ui-table from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dolyame-ui-table — how do I know if it already compromised me?

If dolyame-ui-table was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dolyame-ui-table part of a known attack campaign?

Yes — dolyame-ui-table is associated with the IN-MAL-2026-015592 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-ui-table across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-ui-table (version 35.5.4).

Malicious package

dolyame-ui-tablenpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

dolyame-ui-table is a confirmed malicious npm package (MAL-2026-13189) that executes malicious code on install (malicious version 35.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-table (npm)

MAL-2026-13189

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-ui-table

What this malware does

On require of the package's main entry, _compat.js reconstructs Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev, cf100-416.workers.dev, cf101-adf.workers.dev, cf103-070.workers.dev) and a DNS-TXT fallback discovery host (sdk.dl.wel1.ru) from split string arrays joined at runtime, downloads a platform-specific binary via https.get, writes it under /tmp or %TEMP% with disguised names (dotnet_diag_<rand>.exe,.cache_<rand>), chmods 0o755, and spawns it detached via /bin/sh -c or cmd. Staging paths and destinations are runtime-assembled to evade literal string matching, and the payload uses cover-story naming resembling system diagnostics. The package presents itself as a UI table toolkit, which has no need for native binary downloads or subprocess execution.

Malicious versions

1 flagged

35.5.4

Indicators of compromise (SHA-256)

ed24a0ae9dfa9dd545fde1200d967a5625a2daf28ada90efb2ad78fe5bfdc73e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dolyame-ui-table (version 35.5.4).
If you installed it — respond
Remove dolyame-ui-table from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dolyame-ui-table was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-ui-table on npm has been identified as a malicious package (version 35.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015592

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-table-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database