Malicious code in tinkoff-terminal-kit-test-commons (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-12281
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c68d83a8e515bebce3319c94274060bdfcef42f2ba45e96e87515c9cfd11e020) 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. ## Source: ghsa-malware (d74658ea213467fe61d91ef562769c8427b2346bd61e587f44c3f26f3b8972d3) 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
- 5 Aug 2026 09:01:18 UTC
- Source modified
- 26 Aug 2026 01:16:21 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.