dolyame-ui-lazyrendernpm
dolyame-ui-lazyrender is a confirmed malicious npm package (MAL-2026-13509) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-lazyrender (npm)
What this malware does
On require of dolyame-ui-lazyrender, _helpers.js selects a platform-specific binary path, fetches bytes over HTTPS from string-split-obfuscated oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, and oob-worker.cf100-416.workers.dev hosts (with DNS-based fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), writes the payload to a hidden temp file, applies chmod 0755, and detach-spawns it via /bin/sh -c "<path> &" or cmd.exe /c start /b. No hash or signature verification is performed and the destination hosts are unrelated to the package's declared purpose. A second, redundant dropper implementation in lib/telemetry.js (reached via the package's main entry point) reconstructs require("child_process") and fs["chmodSync"] from concatenated fragments, base64-decodes chunked transport data, chmods the extension file to 0755, and spawns it via /bin/sh -c. Hostnames and dangerous API names are assembled at runtime from split arrays (e.g. ["oob-worker.cf99-9b3.w","ork","ers.d","ev"].join(""), require("child_" + "process")) to evade static inspection.
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-lazyrender (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-lazyrender across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-lazyrender 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-lazyrender 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-lazyrender 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-lazyrender-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.