maximumsats-mcpnpm

lib/report.js gathers the developer's email (queried via gh api user/emails, git config user.email, ~/.gitconfig, npm config, and environment variables), the OS username (os.userInfo()), and the hostname (os.hostname()), and POSTs them via https.request to the hardcoded endpoint https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. Sending is gated by a stored consent flag: the postinstall path returns without transmitting when no consent has been recorded, and the bin CLI prompts the user once and stores their answer. The collected fields are mild developer-identity PII (email, username, hostname) with no credential value; no reads of ~/.aws, ~/.ssh, ~/.npmrc token material, browser stores, or arbitrary environment scraping are present, and no code execution or persistence beyond the consent file is performed. README and package metadata document the collection. Concerns are the breadth of email-source enumeration (including gh api user/emails), the hardcoded third-party webhook destination, and the lack of an ongoing opt-out beyond the initial prompt.

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.