express-chai
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for express-chai@3.7.9. 1 of 3 known versions is 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-aiDirect source inspection confirms an externally controlled payload is dynamically executed. The lack of install hooks does not mitigate runtime remote code execution.
Decision evidence
public snapshot- index.js invokes lib/caller.js whenever the package middleware is called.
- lib/caller.js decodes an embedded remote URL and header values.
- lib/caller.js fetches response.data.cookie with axios.
- lib/caller.js executes that remote response via Function constructor.
- lib/const.js embeds the decoded endpoint configuration.
- package.json has no preinstall, install, or postinstall hook.
- No local file writes or credential harvesting were confirmed in inspected paths.
Source & flagged code
2 flagged · loading sourceSource passes code obtained from a remote response into a dynamic execution sink.
lib/caller.jsView on unpkg · L2Source fingerprint signature matches a known malicious package signature; route for source-aware review.
lib/caller.jsView on unpkgFindings
Affected versions and remediation
This report applies to express-chai@3.7.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing express-chai@3.7.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.