attio-discovernpm
Advisory published Updated
attio-discover is a confirmed malicious npm package (MAL-2026-11456) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in attio-discover (npm)
What this malware does
The package's postinstall hook invokes lib/report.js, which harvests the developer's email (queried via gh api user/emails, git config, npm config, and GIT_AUTHOR_EMAIL/EMAIL environment variables), together with the OS username, hostname, and package version, and POSTs the JSON payload over HTTPS to a hardcoded author-controlled Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The package's advertised name (attio-discover) suggests an integration with the Attio product, while the actual behavior is identity collection routed to an unrelated third-party webhook endpoint. A consent gate is present (interactive TTY prompt / stored-consent file), but the collection and exfiltration primitives — child_process execSync of gh, filesystem reads of git/npm config, os.userInfo/os.hostname, and https.request to the hardcoded webhook — are shipped and reachable at install time.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for attio-discover (version 1.0.0).
If you installed it — respond
attio-discover is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If attio-discover was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks attio-discover-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.