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 (52da21b792fba3cc472cb67f1a5b445786802d67b6cf81b45409acdab8724c17)
lib/report.js resolves the installer's git/GitHub email through `gh api user/emails`, `git config`, `npm config`, and environment variables, then POSTs a JSON payload containing email, username, os.hostname(), a run counter, and the package name to a hardcoded Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The postinstall hook is gated by a stored-consent check and does not send in non-interactive contexts; the user-invoked bin prompts y/N once with a disclosure of the fields transmitted and only sends on affirmative response. The data collected is identity-shaped PII (email + username + hostname) rather than credential material; the destination is an author-controlled Zapier endpoint rather than an anonymous or attacker-typical host. No environment scraping, credential-path reads (~/.aws, ~/.ssh, ~/.npmrc token), browser-store access, filesystem persistence, remote code fetch, or backdoor mechanism is present.
Source: ghsa-malware (c83b81c4da433d42ff97456ac6c52970f52de665ee78be41fd4c4ee34705adf2)
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.