dolyame-ui-scrollnpm
dolyame-ui-scroll is a confirmed malicious npm package (MAL-2026-13181) that executes malicious code on install (malicious version 35.4.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-scroll (npm)
What this malware does
On require() of the package main, init.js selects a platform-specific asset and downloads an opaque binary over HTTPS from a rotating set of author-controlled Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev). Destination hostnames are reconstructed at runtime via array-join string splitting to defeat static inspection. The downloaded bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 755'd on POSIX, and executed detached via spawn('/bin/sh','-c',...) or spawn('cmd', ['/c','start',...]). If HTTPS retrieval fails, the code falls back to a DNS-TXT covert channel against *.dl.wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), reassembles a base64-chunked payload from TXT records, and executes the reconstructed binary. No signature or hash verification is performed, and the fetch-and-execute behavior is unrelated to the package's stated UI-components 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-scroll (version 35.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-scroll across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-scroll 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-scroll 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-scroll 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-scroll-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.