tinkoff-terminal-kit-carouselnpm

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.