Which versions of ai-backup-script are malicious?

The following npm versions of ai-backup-script are flagged malicious: 0.0.2, 1.0.0, 1.0.2. Treat any of these as compromised.

How do I remediate ai-backup-script if I installed it?

ai-backup-script 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.

I already installed ai-backup-script — how do I know if it already compromised me?

If ai-backup-script was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ai-backup-script part of a known attack campaign?

Yes — ai-backup-script is associated with the GHSA-34m8-mhm4-w3q4, IN-MAL-2026-011316, IN-MAL-2026-012920, IN-MAL-2026-013309 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ai-backup-script across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ai-backup-script (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ai-backup-script across your stack and pipelines.

Malicious package

ai-backup-scriptnpm

ai-backup-script is a confirmed malicious npm package (MAL-2026-11454) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.2, 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ai-backup-script (npm)

MAL-2026-11454

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ai-backup-script

What this malware does

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.

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

3 flagged

0.0.21.0.01.0.2

Indicators of compromise (SHA-256)

647eefd97b5d8a0eac0be938122ebe0120152f6ded442d7616b18707bd26ea65

1b53034bc50515b0974263ff0216ebcacc77914381a4fae6a52cc8b25aa15d0c

b5603e10be681ac5a86236edb1ce9cf53615e02867d7ff230a392b8363d7220b

0565052251b4a50ac1b038ea22a217f37dde7d989ead8a4d2e522dd48016eace

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ai-backup-script (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ai-backup-script across your stack and pipelines.
If you installed it — respond
ai-backup-script 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 ai-backup-script was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ai-backup-script before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ai-backup-script on npm has been identified as a malicious package (versions 0.0.2, 1.0.0, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-34m8-mhm4-w3q4IN-MAL-2026-011316IN-MAL-2026-012920IN-MAL-2026-013309

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ai-backup-script-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database