If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (fbb99516f251bbd13baae5273239a6a04acefea76ddf1a7b06f4b5a328339dae)
Package republishes the `chai-spies` Chai plugin source verbatim (including original author header) under the near-identical name `chai-spycore`. `package.json` declares six runtime dependencies — `fast-deep-equal`, `eventemitter3`, `lodash.clonedeep`, `chai-guard`, `is-plain-object`, `just-extend` — but none of these are `require()`d anywhere in `lib/spy.js` or `index.js`. The legitimate `chai-spies` ships with zero runtime dependencies, so the additional deps are pulled into the installer's tree on `npm install chai-spycore` without serving any function in the package's own code. The non-mainstream `chai-guard` dependency is the most suspicious of the set and is the likely vehicle for any indirect code execution against the installer. Routing to human review to assess the name-confusion claim against `chai-spies` and to inspect `chai-guard`'s contents.
Source: ghsa-malware (fc0a99e30b6e4bd6566b0a720a8b30f21a776ec86f3aa1f02c618fb91de0256a)
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.