dolyame-ui-react-wrappernpm
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-react-wrapper (version 35.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-react-wrapper across your stack and pipelines.
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 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-react-wrapper 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-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.