dolyame-ui-carouselnpm
dolyame-ui-carousel is a confirmed malicious npm package (MAL-2026-13141) that executes malicious code on install (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-carousel (npm)
What this malware does
On require of the package's main entry, _shim.js selects a platform-specific payload path and downloads a native binary from one of three Cloudflare Workers hosts whose names are assembled by string-array joins to evade static matching: oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf101-adf.workers.dev. A DNS TXT chunked-base64 covert-channel fallback is implemented against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to a hidden/disguised path in /tmp or %TEMP% (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. A stamp file gates re-execution. Cover-story identifiers such as _NODES, analytics_state, and DISABLE_TELEMETRY are used alongside the drop-and-exec logic. The package's declared purpose is a UI carousel component, which has no legitimate need to fetch and execute a native binary from anonymous workers.dev endpoints at import time.
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-carousel (version 35.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-carousel across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-carousel 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-carousel 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-carousel 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-carousel-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.