chai-redirection
chai-redirection
This report shows the evidence for chai-redirection@0.0.3. 3 of 3 known versions are blocked or flagged. The newest version, 0.0.4, is blocked. 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 4mo ago · by lpm-firewall-aiSource inspection confirms unconsented import-time background execution and remote dynamic code execution unrelated to the advertised chai assertions. This is concrete malicious behavior, not a noisy scanner finding.
Decision evidence
public snapshot- index.js runs callCallerAsOrigin() at import time, spawning detached node lib/caller.js with stdio ignored.
- lib/caller.js fetches https://jsonkeeper.com/b/O3JR0 and executes res.data.cookie via new Function with require.
- lib/caller.js also builds DEV_API_CHECK_DOMAIN + aspath + token and executes error.response.data.token on 404 via Function.constructor.
- package.json main is index.js, so requiring the chai plugin triggers the background payload.
- Dependencies include axios/request/sqlite3 unrelated to visible chai assertion functionality.
- package.json has no npm lifecycle hooks, so payload is import-time rather than install-time.
- Visible exported API contains chai assertion helpers for JWT/password/URL/email/string validation.
- No AI-agent control-surface writes found in inspected files.
Source & flagged code
5 flagged · loading sourceSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
index.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to chai-redirection@0.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-redirection@0.0.3. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.