chai-as-soul
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for chai-as-soul@2.3.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 2mo ago · by lpm-firewall-aiThe import-time payload combines host-data collection and outbound Axios submission with concealed detached process execution. The absence of lifecycle hooks limits the trigger to runtime import, but does not remove the concrete malicious behavior.
Decision evidence
public snapshot- index.js imports lib/config during normal module load.
- lib/config.js is a heavily obfuscated 4 MB payload that loads fs, os, and child_process.
- The payload collects host, OS, username, message, data, and timestamp fields, then sends them with Axios.
- The payload invokes detached, hidden child-process execution.
- package.json has no preinstall, install, or postinstall hook.
- No plaintext network endpoint is recoverable without executing the obfuscated payload.
Source & flagged code
7 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/config.jsView on unpkg · L1A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
lib/config.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to chai-as-soul@2.3.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-as-soul@2.3.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.