# MAL-2026-11454: Malicious code in ai-backup-script (npm)


- **Type:** Malicious package
- **Package:** `ai-backup-script` (npm)
- **Published:** 31 Jul 2026
- **Also known as:** GHSA-34m8-mhm4-w3q4

## What is MAL-2026-11454?

MAL-2026-11454 is a malicious package in ai-backup-script, published on 31 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-11454?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11454 is a malicious package: ai-backup-script (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11454/ (Markdown: https://insights.sbomify.com/MAL-2026-11454/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11454

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11454/
Summaries are generated and may contain mistakes; the official description above is the record.