chai-as-hardened
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for chai-as-hardened@7.0.9, the only known version.
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-aiSource inspection confirms a concrete remote-code-execution chain, not merely suspicious primitives. The lack of install hooks limits the trigger to package use but does not reduce the impact of arbitrary runtime payload execution.
Decision evidence
public snapshot- `index.js` spawns detached Node child when exported middleware is invoked.
- `lib/initializeCaller.js` decodes an obscured remote URL and issues an Axios GET.
- The remote response field is compiled with `Function.constructor` and executed with `require`.
- The request retries silently up to five times; detached child uses ignored stdio.
- `package.json` has no lifecycle hooks, so activation is runtime rather than install-time.
- No package lifecycle scripts (`preinstall`, `install`, or `postinstall`) are declared.
- No AI-agent configuration or persistence-control paths were found in inspected runtime source.
Source & flagged code
3 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
lib/initializeCaller.jsView on unpkg · L2Source fingerprint signature matches a known malicious package signature; route for source-aware review.
index.jsView on unpkgFindings
Affected versions and remediation
This report applies to chai-as-hardened@7.0.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-as-hardened@7.0.9. 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.