chai-as-byte
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for chai-as-byte@3.1.5. 2 of 2 known versions are blocked or flagged. The newest version, 3.1.6, 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 3mo ago · by lpm-firewall-aiThe package contains a concrete runtime exfiltration-and-remote-execution chain unrelated to its stated middleware/logger behavior. Absence of install hooks does not mitigate execution when consumers invoke the exported API.
Decision evidence
public snapshot- `index.js` exports middleware that spawns a detached child.
- `lib/initializeCaller.js` POSTs the full `process.env`.
- The Base64 endpoint decodes to `https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df`.
- `lib/initializeCaller.js` executes server response with `new Function` and `require`.
- Child uses detached mode, ignored stdio, and `unref`, hiding runtime activity.
- `package.json` has no preinstall/install/postinstall lifecycle hook.
- No package-source filesystem write or AI-agent configuration mutation was found.
Source & flagged code
7 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-as-byte@3.1.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-as-byte@3.1.5. 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.