registry / Malware / chai-tracker

chai-tracker

Spies for the Chai assertion library.

This report shows the evidence for chai-tracker@1.2.1. 5 of 6 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

This package appears in our research on the fake chai plugin campaign, with how it works, the full package list and what to do if you installed it.

AI Security Review

scanned 3mo ago · by lpm-firewall-ai

The Node import path contains an unconditional, unrelated detached-process launch and database connector invocation. This is concrete unauthorized runtime behavior, not an inert scanner signal.

Static reason

No blocking static signals were detected.; source fingerprint signature matched known malicious package; routed for review

Trigger

Requiring chai-tracker through its Node main entry.

Impact

Unconsented background execution and externally defined database/network behavior.

Mechanism

Import-time detached child-process launch invoking dbconnectify.

Attack narrative

index.js loads lib/spy.js. While registering Chai assertions, lib/spy.js unconditionally calls assertConnection(), which spawns a detached Node child executing code that requires dbconnectify and calls queryDBConnect(). This behavior is unrelated to a testing spy library and is hidden by the stale browser bundle, which lacks the routine.

AI rationale

The Node import path contains an unconditional, unrelated detached-process launch and database connector invocation. This is concrete unauthorized runtime behavior, not an inert scanner signal.

Evidence

package.jsonindex.jslib/spy.jschai-tracker.js

Decision evidence

public snapshot

AI called this Malicious at 98.0% confidence as Malware with low false-positive risk.

Evidence for block

lib/spy.js:751 invokes assertConnection during plugin import.
lib/spy.js:397-411 spawns detached child Node process.
Child code loads dbconnectify and calls queryDBConnect().
package.json adds unrelated dbconnectify and axios peer dependencies.
Browser bundle chai-tracker.js omits the injected connection routine.

Evidence against

No package lifecycle scripts.
No explicit endpoint or credential harvesting appears in shipped source.

Behavioral surface

Source

ChildProcess

Supply chainNo supply-chain packaging signals triggered.

Manifest

WildcardDependency

scanned 4 file(s), 42.6 KB of source

Source & flagged code

1 flagged

lib/spy.jsView file

•matchType = malicious_source_fingerprint_signature signature = db3db3d6428d9018 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = chai-tracker@1.1.3 matchedPath = lib/spy.js matchedIdentity = npm:Y2hhaS10cmFja2Vy:1.1.3 similarity = 1.000 shingleOverlap = 2 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

lib/spy.jsView on unpkg

Source & flagged code

1 flagged · loading source

lib/spy.jsView file

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

lib/spy.jsView on unpkg

Findings

1 High1 Medium1 Low

HighKnown Malware Source Fingerprint Signaturelib/spy.js

MediumWildcard Dependency

LowScripts Present

Affected versions and remediation

This report applies to chai-tracker@1.2.1.

The versions list below shows the verdict for each recorded version.

Avoid installing chai-tracker@1.2.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-09-23 03:45:05.869Z (UTC).

Source advisory published: 2026-08-10 12:29:01.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

6 known versions

0.0.1-securitylatestClean—AllowPublishedSep 23, 2026, 2:50 AM 1.2.1shownMaliciousMalwareBlockPublishedJul 22, 2026, 11:11 AM 1.1.3MaliciousMalwareBlockPublishedJul 22, 2026, 11:02 AM 1.1.2MaliciousMalwareBlockPublishedJul 17, 2026, 2:07 AM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Behavioral surface

Source & flagged code

Related packages

Other malware packages