What Happened
Attackers repeatedly changed the files that AOMEI Backupper fetches from the vendor's own update servers, in windows of five to ten minutes at a time between May and July 2026, so that any copy of the Windows backup program that checked for an update during one of those windows would download and run a backdoor. Google Threat Intelligence Group, Mandiant, and ManageEngine's Threat Analysis
Why It Matters
Attackers reportedly tampered with AOMEI Backupper update files for short periods between May and July 2026, causing some Windows clients checking for updates during those windows to download and execute a backdoor. The incident concerns compromise of a conventional software-update supply chain, not an AI-specific system. RealGround analysis: organizations using AI agents or AI-enabled software should inventory third-party dependencies, monitor vendor update integrity, and assess update-channel controls; the direct relevance to the allowed AI risk categories is limited.
RealGround Analysis
This signal maps to AI supply chain. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.
Recommended Actions
- Restrict AI agent tool permissions and production write paths.
- Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
- Add human approval workflows for high-impact or state-changing actions.
- Run prompt injection and indirect prompt injection tests against affected workflows.
- Document the owner, control gap, and remediation deadline for this risk class.
Source
https://thehackernews.com/2026/10/attackers-tampered-with-aomei.html