tsihealth-client (npm) · Malicious Code
Affects tsihealth-clientSource GCVE Database
Malicious package : remove tsihealth-client and rotate any secrets on hosts that installed it.
Data as of 12 Aug 2026, 16:10 UTC
Malicious package
Published to npm · OSV MAL-2026-13404
What to do
Remove tsihealth-client from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtsihealth-client | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (554372f29af60ad8e6e5a33171a736baddcc652772b0452c81a4010d3f1e5218) index.js is a top-level self-decoding IIFE that XOR-decodes a URI-encoded payload keyed on the enclosing function's own source and eval()s the result at module load; the decoder aborts with 'the code has been tampered!' if the source is modified, and a banner asks readers not to crack it. The decoded payload is opaque and cannot be audited without executing it. The package's own metadata and typings describe the runtime behavior: package.json advertises it as a 'client (provider) for the tsi-vpsremote control server' that 'stays alive to run commands pushed from the server', keywords include 'shell', 'ssh', 'remote-control', and 'agent', and index.d.ts exports a ProviderHandle exposing a ChildProcess named `shell`. Calling the exported provider(url) at runtime therefore establishes a persistent connection to a remote server that drives a local ChildProcess on the host running the package — a network-to-shell control channel with full-host command execution for whoever controls the paired server URL. ## Source: ghsa-malware (3437dfe049006b09ad2f66c94d934907ac32e7272a22ad75694179e136ac90a8) 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.
References
- npmjs.com/package/tsihealth-client/v/1.0.1 (opens in a new tab)
- npmjs.com/package/tsihealth-client/v/1.0.2 (opens in a new tab)
- npmjs.com/package/tsihealth-client/v/1.0.0 (opens in a new tab)
- npmjs.com/package/tsihealth-client/v/1.0.3 (opens in a new tab)
- npmjs.com/package/tsihealth-client/v/1.0.4 (opens in a new tab)
- github.com/advisories/GHSA-jcwv-5jc7-grp5 (opens in a new tab)