Last checked: October 27, 2026. TeamUpdraft says its investigation is still ongoing. Check the vendor's incident page for updates before acting.

TeamUpdraft disclosed unauthorized access to teamupdraft.com after detecting an incident over October 17–18, 2026. The accessed customer database included account details and connection keys for UpdraftCentral, UpdraftVault, and UpdraftClone. According to the vendor, an attacker used a compromised connection to create WordPress accounts and install malicious plugins on connected sites.

UpdraftPlus 1.26.13 (free) and 2.26.13 (Premium) revoke older UpdraftCentral keys, closing that connection route. That update is important, but it cannot undo a user or plugin that may already have been added. Site owners still need to determine which instructions apply and inspect affected sites.

First: which Updraft products do you use?

Use the first item that describes you, then complete any additional items for other products you use.

  • Free UpdraftPlus only, with no teamupdraft.com account: TeamUpdraft says no incident-specific action is required. Confirm the plugin is current and continue normal backup checks.
  • Any teamupdraft.com account: Type the site address into your browser yourself. Change that account password, change it anywhere else it was reused, reset two-factor authentication, and be alert for phishing.
  • UpdraftPlus Premium: Inspect every site for unexpected users, roles, plugins, and activity, even if you never knowingly used UpdraftCentral.
  • UpdraftCentral cloud: Treat every listed site as needing direct inspection. Log into each WordPress dashboard directly rather than through Central, verify the patched plugin version, and do not reconnect until the site has been checked.
  • Self-hosted UpdraftCentral: TeamUpdraft says the self-hosted product was not affected by this incident. Still complete the account and Premium steps if they apply to you.
  • UpdraftVault: Reconnect Vault from the WordPress dashboard, save the settings, and run a manual backup to prove that remote backups are working again.
  • UpdraftClone: Replace any client key you created or shared. Old keys no longer work; no action is needed if you never created one.

If you do not know which services are connected, open your teamupdraft.com account and compare its listed sites with the sites you actually manage. TeamUpdraft specifically recommends investigating any site you did not knowingly connect after October 19.

WordPress site audit checklist

Complete this review from each site's own WordPress dashboard. If you manage many sites, record the site URL, reviewer, time checked, findings, and actions so none are missed.

1. Confirm the connection fix

  • Verify UpdraftPlus is version 1.26.13 (free), 2.26.13 (Premium), or later.
  • In Settings > UpdraftPlus > Advanced Tools > UpdraftCentral, confirm the old connection is gone. Delete an unexpected or old connection key if it remains.
  • Do not assume automatic updates completed successfully on every site. Record the version you actually see.

2. Review every user and role

  • Open Users > All Users and compare the list with people who should have access.
  • Pay special attention to unfamiliar Administrator and Editor accounts. TeamUpdraft reports seeing unexpected Editor roles as part of this incident.
  • Check for familiar usernames with a role or email address that changed unexpectedly.
  • Record the username, email, role, and creation information available before changing a suspicious account. WordPress's roles documentation explains the access each standard role receives.

3. Inspect regular and must-use plugins

  • Review Plugins > Installed Plugins for unfamiliar, recently added, or unexpectedly activated software.
  • Check the Must-Use tab when it is present. Must-use plugins load automatically and are separate from the ordinary active-plugin list.
  • Ask your host or developer to inspect wp-content/mu-plugins directly if the dashboard does not show enough detail.
  • Record plugin names, folders, timestamps, and screenshots before removal when compromise is suspected. WordPress's plugin-management documentation explains the normal plugin locations and controls.

4. Check activity outside the dashboard

The WordPress dashboard is only one view of the site. Ask your host or technical team to review:

  • WordPress security or activity logs for unfamiliar logins, user changes, plugin installations, and file changes.
  • Hosting access logs for unfamiliar IP addresses or unusual administrative requests around October 17 onward.
  • File-change or deployment records for new or modified PHP files, especially under wp-content/plugins, wp-content/mu-plugins, and the active theme.
  • Scheduled tasks, redirects, and injected content that your normal dashboard review might miss.

Do not enable verbose debugging on a live site simply to investigate this incident. WordPress warns that its debugging tools are intended for local or staging environments; use existing host and security logs where possible.

5. Rotate access that could still expose the site

After documenting suspicious evidence—or immediately if no compromise is found—use a known-clean device to:

  • Change passwords for all WordPress administrators.
  • Replace a reused teamupdraft.com password everywhere it was used and reset the account's two-factor authentication.
  • Rotate remote-storage credentials if a site may have been accessed through UpdraftCentral.
  • Reconnect UpdraftCentral only after the site passes review, so the new connection key is created from a trusted state.

6. Prove that backups work

UpdraftVault sites were disconnected as part of the vendor's response. In Settings > UpdraftPlus > Settings, reconnect Vault, save the settings, and run a manual backup.

For any storage provider, verify the new backup appears in the expected remote destination and includes the database, plugins, themes, uploads, and other files your recovery plan requires. A green schedule alone is not proof that a recoverable backup arrived.

If you find something suspicious

Do not start by deleting everything you do not recognize. That can destroy evidence, hide the timeline, and make a reliable cleanup harder.

  1. Limit access. Contact the host or incident-response provider, restrict administrative access where practical, and avoid using the suspected WordPress dashboard for unrelated work.
  2. Preserve evidence. Save relevant logs, screenshots, user and plugin details, and a protected snapshot of the current site. Keep that snapshot separate from known-good backups.
  3. Rotate credentials from a clean device. Include hosting, WordPress administrators, Updraft accounts, remote storage, and any other secrets confirmed to be exposed.
  4. Determine the last known-good state. A backup from before October 17 may help, but verify its date and integrity before restoration.
  5. Clean or restore with qualified help. Remove unauthorized users and code, patch the original access path, and scan the full account—not only the visible WordPress files.
  6. Verify after recovery. Test logins, forms, checkout, scheduled jobs, backups, DNS, redirects, and monitoring. Watch logs closely for renewed activity.

TeamUpdraft advises users who find suspicious activity to contact its support team and consider restoring a pre-incident backup. Restoration should be part of a documented response: restoring first without preserving evidence or rotating exposed credentials can return the site to service without removing the attacker's access.

A completed response should leave evidence

For each site, you should be able to answer:

  • Which Updraft products and account connections applied?
  • Which UpdraftPlus version was verified, and when?
  • Who reviewed users, roles, regular plugins, must-use plugins, and logs?
  • Were account, administrator, connection, or remote-storage credentials rotated?
  • Was Vault or other remote storage reconnected?
  • Did a manual backup complete and arrive at the expected destination?
  • If suspicious activity was found, where are the preserved evidence and recovery notes?

That record is useful even when the review finds nothing. It turns “we updated the plugin” into a defensible check of the account, the site, and the backups.

Need help checking a WordPress site?

Arcane Web Design can help review WordPress users, plugins, connections, and hosting evidence; coordinate credential rotation; and verify that backups complete after remediation.

Email Nick at nick@arcane-web-design.com or use our contact form for help with a WordPress security review.

Nick Adams - Founder of Arcane Web Design
Nick Adams | Founder of Arcane Web Design

With a decade of web design and development experience, Nick Adams has a proven track record of creating impactful digital solutions for businesses across various sectors. He's honed his skills in web design, front-end development, back-end development, web accessibility, and has helped companies improve foot traffic through improved search engine rankings. He's won several awards in graphic and web design. Read more