dolyame-ui-tablemobilenpm
dolyame-ui-tablemobile is a confirmed malicious npm package (MAL-2026-13601) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-tablemobile (npm)
What this malware does
On require() of dolyame-ui-tablemobile, index.js loads bootstrap.js which selects a platform-specific payload path, fetches bytes from one of three Cloudflare Workers hosts assembled at runtime via string-splitting (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with DNS-TXT chunked fallback via subdomains of dl.wel1.ru. The downloaded bytes are written to /var/tmp/.cache<hex> (POSIX) or %TEMP%\dotnet_diag_<hex>.exe (Windows) under disguised names, chmod'd 0755, and spawned detached via /bin/sh or cmd. The package main lib/telemetry.js contains a mirrored base64-decode -> temp-write -> chmod 0755 -> /bin/sh spawn chain framed as an 'analytics extension', so the payload also runs when consumers require the declared main. Additional evasion is present: require is called as require("child_"+"process"), fs["chmod"+"Sync"], and os"host"+"name", and destination hostnames are reconstructed at runtime from array joins. The delivered payload is opaque native code from third-party infrastructure unrelated to any documented purpose of a UI table component.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-tablemobile (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-tablemobile across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-tablemobile 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-tablemobile was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dolyame-ui-tablemobile before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-tablemobile-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.