tinkoff-ui-actionnpm
Advisory published Updated
tinkoff-ui-action is a confirmed malicious npm package (MAL-2026-12051) that executes malicious code on install (malicious version 20.5.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-ui-action (npm)
What this malware does
On require of the package's main entry, compat.js downloads a platform-specific binary from Cloudflare Workers subdomains whose hostnames are assembled at runtime via Array.join to evade static analysis (e.g. oob-worker.cf*.workers.dev), with a DNS-TXT chunked-base64 fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to /tmp or %TEMP% under cover filenames such as dotnet_diag<hex>.exe and.cache_<hex>, chmodded 0755 on POSIX, and detached-spawned via /bin/sh -c '<path> &' or cmd.exe /c start /b <path>. lib/telemetry.js contains the same download-write-chmod-spawn pattern with obfuscated require("child_"+"process") and fs["chmod"+"Sync"] under an 'Analytics SDK' cover, providing a secondary payload runner. There is no hash or signature verification, no user consent, and the package is advertised as a React UI component library — a purpose unrelated to fetching and executing native binaries. Runtime string-splitting of both hostnames and dangerous API names is deliberate anti-analysis.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for tinkoff-ui-action (version 20.5.7).
If you installed it — respond
Remove tinkoff-ui-action 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 tinkoff-ui-action was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tinkoff-ui-action-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.