dolyame-ui-dataqanpm
dolyame-ui-dataqa is a confirmed malicious npm package (MAL-2026-13564) 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-dataqa (npm)
What this malware does
On require of index.js, the package loads polyfill.js and lib/telemetry.js which download a platform-specific native binary from Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT fallback to *.dl.wel1.ru. Destination hostnames and the child_process module name are assembled at runtime from split-string arrays to evade static scanners. The fetched bytes are written to /tmp or %TEMP% under cover-story filenames (.cache<rand>, dotnet_diag_<rand>.exe), chmodded to 0755, and spawned detached via /bin/sh -c '<path> &' or cmd. lib/telemetry.js contains a duplicate write-chmod-spawn path decoded from base64 buffers, ensuring execution if _polyfill.js is removed. The package presents itself as a UI/data-QA utility; the loader-dropper behavior does not match that stated purpose.
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-dataqa (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-dataqa across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-dataqa 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-dataqa 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-dataqa 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-dataqa-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.