Malicious code in tinkoff-terminal-kit-carousel (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-11549
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d67091b6d7ee752850793817e0bf77d92b3bc16bff12d5348e81c1cb39cf6423) 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. ## Source: ghsa-malware (a1fcbbe4920d181adab68dba9f228acce164681e72d96a0de5b177be3d16bbae) 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.
- Source published
- 4 Aug 2026 22:06:56 UTC
- Source modified
- 26 Aug 2026 01:21:08 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.