anthropic-toolkit

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (90ec82c6478e3a82eac71597b1c1fffc17d1b138e11e1a2aeadec7c00344c65e)
anthropic-toolkit@0.1.1 is a typosquat against the @anthropic-ai/sdk ecosystem. The package ships no library code — its declared `main` (`dist/index.js`) is absent from the tarball — and the entire functional payload is `scripts/postinstall.js`, which runs automatically on `npm install`. On install the script collects host and user identifiers (`os.hostname()`, `os.userInfo()`, `os.platform()`, cwd), parses `~/.gitconfig` and `~/.config/git/config` for `user.email`, walks `.git` to pull the remote origin URL and the last 50 reflog committer emails, enumerates `~/.ssh/*.pub` to extract key-comment emails, reads `~/.aws/config` for profile names, reads `~/.config/gh/hosts.yml` for the authenticated GitHub user, reads `~/.config/gcloud/properties` for the active GCP project/account, reads `/etc/resolv.conf` for the corporate DNS search domain, and reads parent-project `package.json` metadata plus CI provider env. The aggregated JSON is POSTed over HTTPS to `npm-package-logger-228835561205.europe-west1.run.app`. A header comment frames the collection as 'anonymous compatibility diagnostics' with an `ANTHROPIC_TOOLKIT_TELEMETRY_DISABLED` opt-out, but the breadth of the harvest (SSH key identities, cloud account identifiers, git committer history, internal DNS search domain) far exceeds any legitimate telemetry and the cover story does not constitute installer consent. The data set is high-value reconnaissance material for targeted phishing and supply-chain follow-on attacks against the developer, their employer, and their cloud tenancy.

## Source: ghsa-malware (cb5daf1146f26d40e4f4c5b19850e7fe69c228e4097ababcb3f085d481e88de4)
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.

Compromised versions (22)

• 1.0.1
• 0.5.0
• 0.3.1
• 0.2.0
• 0.6.0
• 0.2.1
• 1.3.0
• 1.2.1
• 0.9.0
• 0.1.1
• 1.2.0
• 0.1.0
• 0.4.0
• 1.1.1
• 0.4.1
• 1.0.0
• 0.3.0
• 0.7.0
• 1.1.0
• 0.5.1
• 0.8.0
• 1.3.1

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.