A threat actor breached TeamUpdraft’s infrastructure over the weekend of October 17–18, 2026. Consequently, stolen UpdraftCentral connection keys are now being used to backdoor an estimated 400,000 WordPress websites worldwide.
What Happened: UpdraftCentral Keys Compromised in TeamUpdraft Breach
TeamUpdraft, the developer behind the popular UpdraftPlus backup plugin, detected unauthorized access to its customer database. Also, the attacker accessed password hashes, two-factor authentication settings, and connection keys for UpdraftCentral, UpdraftVault, and UpdraftClone services.
However, payment details were not stored by the vendor. Furthermore, UpdraftPlus plugin files and self-hosted UpdraftCentral instances remain unaffected. The company responded by closing the access route, signing out every account, and replacing compromised keys and credentials.
Technical Details of the UpdraftCentral Attack
The attack exploits stolen UpdraftCentral connection keys to send remote management commands to connected WordPress sites. Moreover, attackers have been observed installing malicious backdoor plugins disguised as WordPress maintenance and optimization tools.
According to Patchstack, the attacks started on October 18, 2026, at 15:32 UTC. Furthermore, researchers logged at least 99 malicious backdoor plugins with distinct names. For example, plugins masquerading as “Site Health Cache” were used to execute arbitrary code and create administrator accounts.
Nethemba reported that three of its own WordPress sites were targeted through UpdraftCentral. In addition, two sites had malicious plugins successfully installed. The attacker did not exploit any server weakness. Instead, they used valid private dashboard keys through the UpdraftCentral remote management channel.
Attack Prerequisites
- A site using UpdraftPlus with an active UpdraftCentral or Migrator connection key
- The key was generated before the October 17–18 breach window
- The site is reachable via the UpdraftCentral cloud management dashboard
Business and Operational Impact
This incident carries a massive blast radius. An estimated 10 percent of UpdraftPlus sites have an UpdraftCentral or Migrator key. Therefore, roughly 400,000 WordPress installations are potentially exposed.
Successful compromise enables attackers to:
- Execute arbitrary PHP code on affected WordPress sites
- Create new administrator accounts with full privileges
- Log in as existing administrators without credentials
- Deploy webshells and additional malware payloads
- Pivot into hosting environments and downstream networks
For managed service providers and agencies using UpdraftCentral to manage client sites, the impact is especially severe. Moreover, a single compromised key could expose an entire client portfolio.
Mitigation and Recommendations
Immediate Actions for Defenders
- Update UpdraftPlus to version 1.26.13 (free) or 2.26.13 (Premium) or later immediately.
- Log into each WordPress site and delete all UpdraftCentral connection keys from Settings → UpdraftPlus Backups → Advanced Tools → UpdraftCentral → Manage existing keys.
- Rotate storage credentials for any remote backup destinations accessed through UpdraftCentral.
- Inspect logs and files for indicators of compromise provided by TeamUpdraft, Patchstack, and Nethemba.
- If compromise is confirmed, restore sites from clean backups before the October 18 attack window.
- Change the TeamUpdraft account password, revoke all sessions, and reset two-factor authentication.
Detection Guidance
Administrators should review installed plugins for any unfamiliar maintenance or optimization tools. Also, monitor user account lists for unexpected administrator accounts. Furthermore, check web server access logs for unusual requests from UpdraftCentral cloud endpoints.
Bottom line: Update UpdraftPlus immediately and rotate all UpdraftCentral connection keys. Even if your site shows no signs of compromise, assume keys generated before October 19 are exposed.
Incident Summary
| CVE ID / Incident: | UpdraftCentral Key Compromise (TeamUpdraft Security Incident, October 2026) |
| Affected Systems: | WordPress sites using UpdraftPlus with UpdraftCentral, UpdraftVault, or UpdraftClone connection keys |
| Disclosure Date: | October 20, 2026 |
| Patch Status: | UpdraftPlus 1.26.13 / 2.26.13 released; key revocation recommended |
| Attack Start: | October 18, 2026, 15:32 UTC |
| Estimated Exposure: | ~400,000 WordPress sites |
References
- TeamUpdraft, “Security Incident October 2026,” October 20, 2026, https://teamupdraft.com/blog/security-incident-october-2026/, accessed October 21, 2026.
- Patchstack, “UpdraftCentral Key Compromise: WordPress Backdoors,” October 20, 2026, https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/, accessed October 21, 2026.
- Nethemba, “UpdraftCentral Backdoor Analysis,” October 20, 2026, https://nethemba.com/updraftcentral-backdoor-analysis/, accessed October 21, 2026.
- BleepingComputer, “Stolen UpdraftCentral keys used to backdoor WordPress sites,” October 20, 2026, https://www.bleepingcomputer.com/news/security/stolen-updraftcentral-keys-used-to-backdoor-wordpress-sites/, accessed October 21, 2026.