chai-as-init (npm) · Malicious Code
Affects chai-as-initSource GCVE Database
Malicious package : remove chai-as-init and rotate any secrets on hosts that installed it.
Data as of 7 Jul 2026, 12:28 UTC
Malicious package
Published to npm · OSV MAL-2026-2891
What to do
Remove chai-as-init from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmchai-as-init | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
chai-as-init is a malicious npm package that when imported downloads a C2 dropper from https://api.npoint[.]io/c2e881b8bc0fe2121454 and executes it (similar to malware in to chai-await-test). --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (86a5e85d8d41d2f731104422d3a8e4a73d02354250782e45389d28acc2332854) Package name impersonates chai-as-promised and ships a README copied from pino as cover. The exported middleware spawns a detached node child running lib/initializeCaller.js, which decodes a base64-encoded URL (https://ipcheck-hashed.vercel.app/api/auth/b4dadd6a26d820d08596) and POSTs the full process.env (`{...process.env }`) — including any AWS/GCP/CI/npm tokens — to that endpoint with header `x-secret-header: secret`. The HTTP response body is then passed to `new Function('require', response.data)` and invoked with `require`, giving the remote operator arbitrary code execution with full Node privileges on any host that imports the package and invokes the middleware. Combination of name impersonation, copied README cover, base64-obfuscated C2, bulk env exfiltration, and dynamic remote-code evaluation is the canonical supply-chain RCE shape. ## Source: ghsa-malware (c0ce99e61fda9a489c749cea51adcf66648c56d26ee18a7aa4f0100db30615f9) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
References
- indece.com/en-US/blog/7df041ba-feb1-4d87-918b-7fc2c709d805 (opens in a new tab)
- npmjs.com/package/chai-as-init/v/1.4.6 (opens in a new tab)
- npmjs.com/package/chai-as-init/v/1.4.5 (opens in a new tab)
- npmjs.com/package/chai-as-init/v/1.4.7 (opens in a new tab)
- github.com/advisories/GHSA-7cq2-px9f-cq3g (opens in a new tab)