TeamUpdraft and UpdraftCentral key compromise

Compromised connection keys enabled access to customer WordPress sites.

Last modified

Summary

  • Environment: TeamUpdraft customer systems and UpdraftCentral-connected WordPress sites
  • Operational impact: Unauthorized customer-site changes; connection keys revoked
  • Financial impact: No total incident cost established in the reviewed evidence
  • Record status: Developing record. Reviewed October 21, 2026; updated as evidence emerges.

What happened

TeamUpdraft detected unauthorized website access during October 17–18, 2026. It later confirmed that attackers used customer-site connections to create administrator accounts and install malicious plugins. [1]

Impact

TeamUpdraft believed its customer database was accessed. It held contact and billing details, order history, password hashes, two-factor settings and service connection keys. The downstream extent remains unknown. [1]

The vendor said plugin downloads and self-hosted UpdraftCentral were unaffected. [1]

Timeline

  1. Disclosure and key revocation

    TeamUpdraft published its notice and released UpdraftPlus 1.26.13 and 2.26.13 to revoke connections.

    [1]
  2. Customer-site misuse confirmed

    Premium users were urged to check sites even without knowingly using UpdraftCentral.

    [1]
  3. Briefing updated

    This briefing was last reviewed and updated on October 21, 2026.

Threat Group & Attack Vector

The vendor identified a compromised key as its entry route. [1]

Patchstack’s analysis described valid signed commands delivering backdoors. The resulting privileged accounts could survive removal of the malicious plugin. [2]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

TeamUpdraft closed access, rotated keys, signed out accounts and notified authorities. Its dated updates specify the .13 releases; older .12 instructions remain lower on the page. The vendor still urges site review after disconnection. [1]