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 (3d412258df9a21f510333926a9be29bed8ae6368e549e295c84e187bdc1a3725)
Package `knip-bun` typosquats the popular `knip` linter. The main module is an empty stub (`module.exports = {}`), and `package.json` declares a dependency `ltidisafe` pinned to an arbitrary Google Cloud Storage URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.8.tgz`) rather than a package on the npm registry. On `npm install`, npm downloads and installs the tarball from that bucket into the installer's dependency tree and runs whatever install/lifecycle logic it contains. The bucket is unaffiliated with the knip or bun projects, and the fetched tarball is fully controlled by whoever owns that GCS bucket.
Source: ghsa-malware (5aa3848c6982142717f50c64c192504c993dea3d7440d11588703cf6d5e656d9)
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.