Which versions of chai-tracker are malicious?

The following npm versions of chai-tracker are flagged malicious: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.1. Treat any of these as compromised.

How do I remediate chai-tracker if I installed it?

chai-tracker is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-tracker, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed chai-tracker — how do I know if it already compromised me?

If chai-tracker was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is chai-tracker part of a known attack campaign?

Yes — chai-tracker is associated with the IN-MAL-2026-017261, IN-MAL-2026-017263, IN-MAL-2026-017265, IN-MAL-2026-017264, IN-MAL-2026-017262 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find chai-tracker across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-tracker (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-tracker across your stack and pipelines.

Malicious package

chai-trackernpm

chai-tracker is a confirmed malicious npm package (MAL-2026-13704) that typosquats a legitimate package to trick installs (malicious versions 1.1.0, 1.1.1, 1.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-tracker (npm)

MAL-2026-13704

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall chai-tracker

What this malware does

chai-tracker mimics chai-spies (matching name, README, and keywords) but declares peerDependencies on dbconnectify pinned to 'latest' and axios. The exported chai plugin function, invoked when a consumer calls chai.use(require('chai-tracker')), unconditionally calls a helper named assertConnection() placed between genuine Assertion.overwriteMethod definitions. Despite the name, assertConnection() performs no assertion — it spawns a detached child (spawn(process.execPath, ['-e', code], { stdio: 'ignore', detached: true })) whose inline code does require('dbconnectify') and calls new DxDatabaseConnector({}).queryDBConnect(). Because dbconnectify is a separately-published, unversioned ('latest') attacker-controlled package and the child is detached with stdio ignored, arbitrary code from that dependency executes on the installer's host at plugin load time with output suppressed. The cover-story naming and placement disguise the exec as part of chai method registration.

Malicious versions

5 flagged

1.1.01.1.11.1.21.1.31.2.1

Indicators of compromise (SHA-256)

12a7bbd6d78534877f788d24df2bcc7b62ec10c5b56b2bd218d7cb25edb4b8ca

3ab2d9f276d6fb4a594c7e8b395c390ce7d73828e4756214a008a7e981a64539

86283c9d77d09bb74e1740b9e82054c894450ed060e09afc5aae14cc973e8660

94d712ff478a98bdc7c5b7b2fb76a0c79fb85378ffc15741aa1e77688e515718

d61869c26ad8015b88350d312fa37f5e18d536794ce5d8c46bf4239b2154b1a9

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-tracker (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-tracker across your stack and pipelines.
If you installed it — respond
chai-tracker is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-tracker, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If chai-tracker was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks chai-tracker before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. chai-tracker on npm has been identified as a malicious package (versions 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017261IN-MAL-2026-017263IN-MAL-2026-017265IN-MAL-2026-017264IN-MAL-2026-017262

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-tracker-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database