dolyame-ui-steppernpm
dolyame-ui-stepper is a confirmed malicious npm package (MAL-2026-13185) that typosquats a legitimate package to trick installs (malicious version 35.7.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-stepper (npm)
What this malware does
On require('dolyame-ui-stepper'), index.js unconditionally loads shim.js, which assembles hostnames from split string fragments (resolving to oob-worker.cf{101-adf,99-9b3,100-416,103-070}.workers.dev, with a DNS-TXT base64 fallback via {sdk,ext,pkg,net}.dl.wel1.ru), fetches a platform-matched native binary over https.get, writes it to a temporary path under a disguised name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on POSIX), chmods 0o755, and spawns it detached via /bin/sh -c '<file> &' or cmd.exe /c start /b. A duplicate dropper implementation using the same primitives (base64 chunk assembly, chmod 755, detached spawn) is also staged in lib/telemetry.js under an 'Analytics SDK' cover story, though not reachable from the current main. The destination hosts are obfuscated via string-splitting, the dropped filename impersonates a Microsoft diagnostic tool, and the fetch-and-execute path fires on every import with no user interaction.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-stepper (version 35.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-stepper across your stack and pipelines.
If you installed it — respond
dolyame-ui-stepper is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-stepper, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-ui-stepper 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-stepper 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-stepper-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.