chai-assertions-plus
Extends Chai with additional assertion methods for common testing patterns.
This report shows the evidence for chai-assertions-plus@6.0.6. 2 of 2 known versions are blocked or flagged. 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-aiThis is a concrete import-time remote code execution chain controlled by an external endpoint, with no legitimate assertion-library purpose. The package should be blocked.
Decision evidence
public snapshot- `index.js` imports `./lib/initializeCaller` at module load.
- `lib/initializeCaller.js` immediately decodes a hidden URL and header values.
- It performs `axios.get` and takes `response.data.cookie` as code.
- It executes that server-controlled value via `new Function("require", response)`.
- The remote request retries five times while swallowing errors.
- The package's Pino-derived files do not match its claimed Chai assertion purpose.
- `package.json` has no preinstall, install, or postinstall hook.
- No AI-agent configuration or control-surface mutation was found in inspected JavaScript.
Source & flagged code
5 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
lib/initializeCaller.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to chai-assertions-plus@6.0.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-assertions-plus@6.0.6. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.