taiga-ui-proprietary-navigationnpm
taiga-ui-proprietary-navigation is a confirmed malicious npm package (MAL-2026-12474) that opens a backdoor for remote access (malicious version 20.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in taiga-ui-proprietary-navigation (npm)
What this malware does
Package advertises itself as Taiga UI proprietary navigation components but ships adapter.js, which is required by index.js at module load. On require, adapter.js selects a platform-specific endpoint, fetches an opaque binary from string-split-obfuscated Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT fallback channel (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), writes it to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd. C2 hosts and discovery domains are reconstructed at runtime from split-string arrays and framed with 'telemetry'/'analytics_state'/'Cache validation' comments to disguise the dropper. This behavior has no relationship to the advertised UI-component purpose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for taiga-ui-proprietary-navigation (version 20.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging taiga-ui-proprietary-navigation across your stack and pipelines.
If you installed it — respond
taiga-ui-proprietary-navigation establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If taiga-ui-proprietary-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 taiga-ui-proprietary-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 taiga-ui-proprietary-navigation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.