dolyame-ui-navigationnpm
dolyame-ui-navigation is a confirmed malicious npm package (MAL-2026-13170) that executes malicious code on install (malicious version 35.7.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-navigation (npm)
What this malware does
The package advertises itself as a UI navigation toolkit, but its main entry (index.js) require()s./compat.js, which on load fetches a platform-specific executable from hardcoded Cloudflare Workers hosts assembled via array-join to evade static analysis (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) and falls back to DNS-TXT resolution against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded payload is written to /var/tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755, and spawned detached via /bin/sh -c on POSIX or cmd /c start /b on Windows. lib/telemetry.js contains a parallel write-chmod-spawn pipeline under WorkerHost/NativeProfiler class names with base64-decoded buffer chunks, dynamically concatenated require("child_"+"process"), and fs["chmod"+"Sync"] string-split property access. State is persisted to.analytics_state to blend with system files. The behavior fires on require() of the package, so any consumer that installs and imports dolyame-ui-navigation executes the attacker-controlled binary on their host.
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-navigation (version 35.7.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-navigation across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-navigation 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-navigation 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-navigation 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-navigation-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.