dolyame-ui-mixinsnpm
dolyame-ui-mixins is a confirmed malicious npm package (MAL-2026-13168) that executes malicious code on install (malicious version 35.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-mixins (npm)
What this malware does
On require of dolyame-ui-mixins, index.js loads./ext, which selects a platform-specific asset path (linux_x64, linux_arm64, darwin, win32) and downloads an opaque native binary over HTTPS from one of three Cloudflare workers.dev hosts whose names are reconstructed by array-join to evade static inspection (e.g. ["oob-worker.cf103","-070.wo","rkers.d","ev"].join("") yielding oob-worker.cf103-070.workers.dev, plus oob-worker.cf100-416.workers.dev and oob-worker.cf102-baf.workers.dev). A DNS TXT covert-channel fallback resolves base64 chunks from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp (or the Windows TEMP directory) under disguised filenames of the form.cache<hex> or dotnet_diag_<hex>.exe, chmod'd 0755 via fs["chmod"+"Sync"], and spawned detached through /bin/sh -c or cmd.exe with.unref(). There is no version pin, no hash or signature verification, and no relationship between the fetched binary and the package's stated purpose of providing UI mixins. A second, parallel dropper is shipped in lib/telemetry.js under an 'Analytics SDK' cover story, using require("child_"+"process"), base64 DNS-chunk assembly, chmod 0755, and /bin/sh -c spawn against the same infrastructure pattern.
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-mixins (version 35.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-mixins across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-mixins 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-mixins 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-mixins 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-mixins-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.