dolyame-ui-react-wrappernpm
Advisory published Updated
dolyame-ui-react-wrapper is a confirmed malicious npm package (MAL-2026-13180) that executes malicious code on install (malicious version 35.4.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-react-wrapper (npm)
What this malware does
On require, index.js loads helpers.js which runs setup() at module load. The setup routine reconstructs mirror hostnames at runtime by joining split string fragments (e.g. 'oob-worker.cf101-adf.workers.dev', 'oob-worker.cf100-416.workers.dev', 'oob-worker.cf103-070.workers.dev') and DNS-discovery domains ('sdk.dl.wel1.ru', 'ext.dl.wel1.ru', 'pkg.dl.wel1.ru', 'net.dl.wel1.ru') with a DNS TXT base64 fallback, downloads a platform-specific binary via https.get, writes it to /tmp or the Windows Temp directory under disguised names such as '.cache<hex>' and 'dotnet_diag_<hex>.exe', chmods it 0755, and spawns it detached through '/bin/sh -c' or 'cmd'. The package name presents as a UI React wrapper for an unrelated payments brand, unrelated to the actual behavior, and string obfuscation of hostnames serves only to defeat scanners.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for dolyame-ui-react-wrapper (version 35.4.2).
If you installed it — respond
Remove dolyame-ui-react-wrapper 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-react-wrapper 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-react-wrapper-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.