tinkoff-terminal-kit-carouselnpm
tinkoff-terminal-kit-carousel is a confirmed malicious npm package (MAL-2026-11549) that executes malicious code on install (malicious version 20.6.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-terminal-kit-carousel (npm)
What this malware does
On require() of the package, index.js loads _adapter.js, which selects a platform-specific endpoint, fetches an opaque binary over HTTPS from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev), writes the bytes to /tmp or %TEMP% under a hidden/decoy filename (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh or cmd.exe. Hostnames are assembled at runtime from split string arrays joined together to evade static analysis, and a cooldown marker file (.analytics_state) suppresses re-execution. If the HTTPS fetch fails, loadViaDns retrieves base64-encoded chunks from TXT records under tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site, reassembles them into a binary, and executes it via the same path. No source is shipped for the executed payload, no hash or signature is verified, and no user consent is obtained. The package name resembles the Tinkoff Investments brand but the code has no relation to any documented Tinkoff SDK.
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-terminal-kit-carousel (version 20.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-terminal-kit-carousel across your stack and pipelines.
If you installed it — respond
Remove tinkoff-terminal-kit-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 tinkoff-terminal-kit-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 tinkoff-terminal-kit-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 tinkoff-terminal-kit-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.