dolyame-ui-actionnpm
dolyame-ui-action is a confirmed malicious npm package (MAL-2026-13134) that executes malicious code on install (malicious version 35.6.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-action (npm)
What this malware does
On require('dolyame-ui-action'), index.js loads support.js which downloads a platform-specific binary over HTTPS from Cloudflare Workers hosts whose names are reconstructed at runtime from split string arrays (e.g. joined fragments producing 'oob-worker.cf'-style workers.dev hosts), with a DNS TXT base64 fallback under *.dl.wel1.ru. The fetched bytes are written to /var/tmp or the Windows TEMP directory under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod'd to 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or the Windows cmd equivalent. _support.js is loaded from index.js via a silent try { require('./support'); } catch() {} wrapper. lib/telemetry.js (81KB, labeled 'Analytics SDK') bundles parallel dropper primitives — base64 buffer decode, a masked fs['chmod'+'Sync'] to 0755, and cp.spawn('/bin/sh', ['-c', filePath + ' &'], {detached:true}) — providing an alternate execution path in the same tarball. The destination hostnames are obfuscated by fragment-join reconstruction, the loader is wrapped in a swallow-all try/catch, and the delivered binary is opaque and unpinned.
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-action (version 35.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-action across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-action 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-action 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-action 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-action-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.