chai-tracker (npm) · Malicious Code
Affects chai-trackerSource GCVE Database
Malicious package : remove chai-tracker and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:15 UTC
Malicious package
Published to npm · OSV MAL-2026-13704
What to do
Remove chai-tracker 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 |
|---|---|---|
| npmchai-tracker | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The chai-tracker npm package contains malicious code that executes arbitrary code on the host system when the package is loaded. It mimics the legitimate chai-spies package but depends on an attacker-controlled package named dbconnectify pinned to 'latest'. Upon loading, chai-tracker spawns a detached child process that runs code from dbconnectify, allowing silent execution of arbitrary commands. This malicious behavior is disguised within chai method registration, making it difficult to detect during normal use.
References
- npmjs.com/package/chai-tracker/v/1.2.1 (opens in a new tab)
- npmjs.com/package/chai-tracker/v/1.1.0 (opens in a new tab)
- npmjs.com/package/chai-tracker/v/1.1.1 (opens in a new tab)
- npmjs.com/package/chai-tracker/v/1.1.2 (opens in a new tab)
- npmjs.com/package/chai-tracker/v/1.1.3 (opens in a new tab)
- github.com/advisories/GHSA-xvr2-rmx5-mrv3 (opens in a new tab)