dolyame-ui-skeletonnpm
dolyame-ui-skeleton is a confirmed malicious npm package (MAL-2026-13183) that executes malicious code on install (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-skeleton (npm)
What this malware does
Package advertises itself as a visual/UI components library but ships a load-time binary dropper. index.js unconditionally requires./vendor.js, which on require() downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to a hidden cache path, chmods 0755, and spawns it detached via /bin/sh or cmd. Destination hostnames are reconstructed at runtime by joining string fragments (e.g. ["oob-worker.cf101-adf",".workers.dev"].join("") and ['sdk.dl.wel','1.r','u'].join("")) to evade static analysis. A fallback delivery path issues DNS TXT queries against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru (c.<domain> for chunk count, then N.<domain> for base64-encoded chunks), reassembles the chunks, and executes the resulting binary — a covert channel that bypasses HTTPS egress filtering. Filenames such as analytics_state, dotnet_diag.exe, and.cache_ serve as cover for the dropped payload. There is no legitimate need for a UI component package to fetch and execute native binaries, obfuscate its destinations, or use DNS TXT for content delivery.
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-skeleton (version 35.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-skeleton across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-skeleton 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-skeleton 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-skeleton 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-skeleton-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.