Malicious code in tanksync (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-17209
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (45dcd24fc5596e9273938687d6878a8927fcdf9ffd63982034556e84c3339065) The package's advertised API downloads a JavaScript file over HTTPS and executes it via spawn('node', [payloadPath], {detached: true}).unref(), leaving the worker running after client.close(). The default fetch target is hardcoded to https://api.helloworld.com/api/realtime-data?key=abc, which is a placeholder-shaped host that does not match the publisher's declared domain (spawnrealm.com). The purported integrity check computes HMAC-SHA256 using a symmetric key ('tanksync-secret-key') baked into the shipped source, so any party who reads the package can produce a valid signature for arbitrary payloads; the default expected signature is the placeholder 'abc123def456'. The trigger is a user-invoked API call rather than an install or import lifecycle hook, but fetching and executing arbitrary remote JavaScript is the package's entire declared purpose, and the detached worker continues running after the client is closed. ## Source: ghsa-malware (f372677522463b96bc07edb8801faa745412fd42431192c488a67e8feddd4e4c) 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
- 28 Sep 2026 05:54:47 UTC
- Source modified
- 30 Sep 2026 01:00:06 UTC
- Observed 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
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.