dolyame-ui-editornpm
dolyame-ui-editor is a confirmed malicious npm package (MAL-2026-13153) that executes malicious code on install (malicious version 35.6.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-editor (npm)
What this malware does
dolyame-ui-editor 35.6.6 is not a UI editor. index.js unconditionally requires./loader on module load. loader.js selects a platform-specific asset, obfuscates its destination hostnames via array.join() (e.g. 'oob-worker.cf99-9b3.workers.dev' and 'sdk.dl.wel1.ru'), fetches an opaque binary over HTTPS from a rotated list of Cloudflare Workers hosts with a DNS TXT-record fallback channel, writes it under /tmp/.cache<hex> or %TEMP%\dotnet_diag<hex>.exe with disguised names, chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start. child_process is loaded via require("child_"+"process") and chmodSync is accessed via fs["chmod"+"Sync"] to evade static scanners. lib/telemetry.js ships an 81KB mirror of the same drop-and-execute primitives (endpoint rotation, DNS-based service discovery, base64-decoded buffer, chmodSync 0755, detached /bin/sh spawn), staged for later activation. No hash or signature verification of the fetched payload; destinations are unrelated to any stated 'visual components' purpose and the fetched bytes are opaque. The package is a lure whose install/require executes attacker-controlled code on the installer's host.
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-editor (version 35.6.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-editor across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-editor 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-editor 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-editor 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-editor-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.