Malicious code in ai-backup-script (npm)
MAL-2026-11454 · GHSA-34m8-mhm4-w3q4
Published · Modified
Dependency scanning
Check whether ai-backup-script is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (b5603e10be681ac5a86236edb1ce9cf53615e02867d7ff230a392b8363d7220b)
The package is named 'ai-backup-script' but performs no backup functionality. lib/report.js collects the installer's git/GitHub email (via gh api, git config, npm config, and environment variables), OS username, and hostname, and POSTs them to a hardcoded Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. Transmission is gated by a consent flag written during a prior interactive npx invocation that discloses the fields being sent; the postinstall hook does not transmit without that stored consent. Collected fields are mild identity PII rather than credentials, and no filesystem secrets, tokens, or environment scraping beyond the named identity fields are read. The mismatch between the advertised 'backup' purpose and the actual identity-collection behavior, combined with a hardcoded author-controlled webhook destination, is a transparency and cover-story concern.
Source: ghsa-malware (647eefd97b5d8a0eac0be938122ebe0120152f6ded442d7616b18707bd26ea65)
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.
Ready to move
Start Securing
Free, no credit card | First findings in minutes