tinkoff-terminal-kit-test-commonsnpm
tinkoff-terminal-kit-test-commons is a confirmed malicious npm package (MAL-2026-12281) that executes malicious code on install (malicious version 20.9.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-terminal-kit-test-commons (npm)
What this malware does
On require() of [email protected], index.js loads adapter.js which selects a platform-specific endpoint, downloads an opaque binary from one of four hardcoded Cloudflare workers.dev hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), writes it to /tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. No hash or signature verification is performed. The destination hostnames and a DNS-TXT fallback channel (*.dl.well1.site, reassembled from base64-encoded TXT record chunks) are constructed at runtime from split string fragments joined via Array.join(''), and the 'child_process' import is similarly assembled — deliberate obfuscation to evade static string scans. The fetch-write-chmod-spawn chain and the DNS-TXT covert transport are unrelated to any stated purpose of the package.
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-test-commons (version 20.9.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-terminal-kit-test-commons across your stack and pipelines.
If you installed it — respond
Remove tinkoff-terminal-kit-test-commons 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-test-commons 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-test-commons 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-test-commons-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.