dolyame-ui-textnpm
dolyame-ui-text is a confirmed malicious npm package (MAL-2026-13193) that opens a backdoor for remote access (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-text (npm)
What this malware does
The package is published under a name suggesting a React UI text component, but its main entry (index.js) require()s./init on module load, which acts as a binary dropper. init.js reconstructs C2 hostnames at runtime from string-split arrays (resolving to oob-worker.cf*.workers.dev and *.dl.wel1.ru), downloads a platform-specific payload over HTTPS with a DNS-TXT base64 fallback channel (chunk-count read from c.<domain>, chunks reassembled from N.<domain>), writes the payload to /tmp (Unix) or %TEMP% (Windows) under decoy names such as.cache<hex> and dotnet_diag<hex>.exe, chmods it to 0755, and spawns it detached via /bin/sh -c or cmd. A second dropper implementation in lib/telemetry.js, cover-labeled as an 'Analytics SDK', base64-decodes an embedded payload buffer, uses bracket-property obfuscation to hide chmodSync, and spawns the dropped file via /bin/sh -c. No published functionality relates to a UI text component; the delivered code, its obfuscation, and its execution path have no benign explanation.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-text (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-text across your stack and pipelines.
If you installed it — respond
dolyame-ui-text establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dolyame-ui-text 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-text 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-text-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.