Glossary term
Backdoor
A backdoor is an undocumented way of gaining access to a computer system, and NIST says it is a potential security risk.
Quick links
Press Enter to search, Esc to close
Significant cyber incident
Between April and July 2026, attackers briefly tampered with the update files of the AOMEI Backupper installer, so that the backup program fetched and ran a backdoor.
In short
Between April and July 2026, attackers briefly tampered with the update files of the AOMEI Backupper installer, so that the backup program fetched and ran a backdoor. It is a software supply chain compromise: no flaw in the program was used. Google Threat Intelligence Group and Mandiant say each window lasted only 5 to 10 minutes, and they track the actor as UNC7017.
ManageEngine’s Threat Analysis Lab says its tools saw AOMEI Backupper install Radmin remote administration software on a customer computer on 28 May 2026. A second customer in another country showed the same chain. Together with Google Threat Intelligence Group and Mandiant it traced the cause to the backup program’s own update settings.
Google and Mandiant say attackers changed those settings on the vendor’s servers three times that they saw directly: on 28 May, 16 July and 20 July 2026. Each window lasted 5 to 10 minutes before the files went back to their real versions. Any copy of the program that checked for updates in that time could be sent to attacker files. Google says it is the first time it has met a software supply chain compromise with such short windows.
Google also reports that on 20 July the attackers added a hidden pop-up that could make computers send network login material to a server they controlled. Impacted organizations, it says, were in IT services, telecommunications and higher education across Australia, Brazil, India, Pakistan, Portugal, Singapore, South Africa, Spain, Switzerland, Türkiye and the United States.
Google and Mandiant say the tampering dates back to this month.
Tampering window of about 10 minutes. ManageEngine's tools see Radmin installed by AOMEI Backupper on a customer computer.
ManageEngine raises the alert with AOMEI.
Window of about 6 minutes, caught live by ManageEngine's monitor.
Mandiant notifies AOMEI and shares indicators.
Window of about 5 minutes. The attackers add a hidden pop-up that can send network login material to their server.
Google says AOMEI replied that it had taken corrective action.
Google Threat Intelligence Group and Mandiant publish their report.
ManageEngine's Threat Analysis Lab publishes its report.
This is a compromise of the software supply chain (T1195.002). No flaw in the program was used. Both researchers say the problem is that the update settings files were not cryptographically checked, and that the checksum that should prove a download is genuine sat in the same unsigned file as the download address.
Attributed by Google Threat Intelligence Group and Mandiant, 15 October 2026: they track the activity as UNC7017, a cluster that is not tied to a named group or country. ManageEngine's Threat Analysis Lab, which first found the activity, uses the same names in its report of 16 October 2026.
No government body has attributed or described these attacks in the sources we opened.
AOMEI has published no security notice that we could find. Its changelog (version 8.5.0 listed on 19 October 2026) and the pages we tried say nothing about the incident. What we know about its reaction comes from the researchers: Google says Mandiant told AOMEI on 17 July and AOMEI replied on 29 July that it had taken corrective action. ManageEngine says that on 7 June AOMEI first explained that the content had been intercepted and changed in transit, which the researchers say the evidence did not support, and that it has not verified AOMEI's fix.
This case is separate from CVE-2026-12780, a local driver flaw in the same product family.
The number of affected computers has not been published. Google says the targeting was opportunistic because every computer that checked for updates in a window was exposed, and that the real reach "likely extends more broadly" than the organizations it saw. ManageEngine says the backdoor could run commands and new code, but it saw no live session. Credential material may have leaked through the pop-up even on computers where the backdoor did not run.
The vendor address returned real files most of the time. Testing an alert later said nothing about what was delivered earlier.
The settings files and their checksum came from the same unsigned place. Both researchers advise signing configuration files, not only programs.
The pop-up system let remote content start programs. Google advises keeping promotional pop-ups away from core updates.
Computers that ran the file keep their scheduled task and backdoor until someone removes them.
Check whether any computer has a scheduled task named RadminComponentRuntime.
Check for Radmin software that nobody installed, and for unsigned libraries beside its launcher.
Review proxy and firewall logs from April to July 2026 for AOMEI Backupper update traffic to unusual hosts.
Check that file-sharing traffic (port 445) and WebDAV to outside addresses is blocked at the edge.
Where the credential pop-up may have run, reset passwords for accounts used on those computers.
Check which hosts each of your backup and remote tools may fetch updates from.
Google Threat Intelligence Group and Mandiant say attackers changed its update settings for 5 to 10 minutes at a time between April and July 2026, so that the program fetched a backdoor.
No. ManageEngine and Google say the update settings were not cryptographically checked, so no flaw was needed.
We found none. Google says AOMEI told Mandiant on 29 July 2026 that it had taken corrective action.
No. That is a separate local driver flaw. The update tampering used no vulnerability.
Not necessarily. Google says a computer that ran the file can keep the backdoor, so check for the scheduled task and unexpected Radmin software.
Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.