chai-sdk (npm) · Malicious Code
Affects chai-sdkSource GCVE Database
Malicious package : remove chai-sdk and rotate any secrets on hosts that installed it.
Data as of 10 Jul 2026, 09:29 UTC
Malicious package
Published to npm · OSV MAL-2026-6931
What to do
Remove chai-sdk 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-sdk | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9192d163b3814064c95a23cb11e218732346628f3109517aab7697c2dcb6d016) On require, index.js spawns a detached background node process that runs lib/initializeCaller.js. That module axios.get()s a base64-obfuscated URL (decodes to https://amethyst-lorrin-26.tiiny.site/index.json) and passes the response's `cookie` field to `new Function('require',...)` which is then invoked with the real `require`, giving the remote operator arbitrary Node.js execution inside the installer's process. The URL is stored as a base64 blob decoded via atob() and wrapped in a function named `initializeCaller` with comments framing it as routine middleware — deliberate cover for the exfiltration/execution primitive. The package is published as `chai-sdk` but its entrypoint exports an object named `pino` with pino's DEFAULT_LEVELS, messageKey, and mirror files (lib/proto.js, lib/multistream.js, lib/redaction.js), masquerading as the popular pino logger so consumers integrate it as a benign logging dependency. Import-time fetch is from an anonymous, mutable tiiny.site host with no pinning, hash, or signature — whatever JavaScript the operator serves runs with the consumer's Node privileges. ## Source: ghsa-malware (73f55ea2148f54488c6dd557e27e14ff69b4368dac55afc8cb336fc3bc59c853) 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.