chai-sdk
This document describes the management of vulnerabilities for the project and all modules within the organization.
This report shows the evidence for chai-sdk@1.4.8. 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 4mo ago · by lpm-firewall-aiStatic inspection confirms a concrete runtime remote-code-execution chain from package API invocation to hidden network fetch and dynamic execution. Absence of install hooks reduces install-time impact but does not mitigate the malicious runtime payload loader.
Decision evidence
public snapshot- index.js exports middleware that spawns detached node process running lib/initializeCaller.js on invocation.
- lib/initializeCaller.js performs axios.get to Base64-hidden URL https://amethyst-lorrin-26.tiiny.site/index.json.
- lib/initializeCaller.js executes response.data.cookie with new Function("require", ...), enabling arbitrary remote code execution.
- package.json main is index.js and no lifecycle hooks are needed; attack triggers at runtime when package API is used.
- Package contents appear copied from pino docs/code while manifest name is chai-sdk, increasing deception context.
- package.json has no preinstall/install/postinstall lifecycle scripts.
- No local credential harvesting or file writes are visible in inspected static source before remote payload execution.
Source & flagged code
5 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-sdk@1.4.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing chai-sdk@1.4.8. 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.