Skip to navigation

Threat reportSupply ChainTL-2026-3995

Stolen UpdraftCentral Keys Used to Backdoor WordPress Sites Following TeamUpdraft Breach

criticalACTIVE

TeamUpdraft's website and customer database were breached on 17-18 October 2026, exposing UpdraftCentral, UpdraftVault and UpdraftClone connection keys along with password hashes and 2FA settings. Attackers used the stolen keys to send correctly signed UpdraftCentral plugin.upload_plugin commands and deployed at least 99 backdoor plugins that create hidden administrator access on an estimated 400,000 exposed WordPress sites.

Key facts

IdentifiersTL-2026-3995, CVE-2026-10795
Also known asUpdraftCentral key compromise, TeamUpdraft security incident October 2026
SeverityCRITICAL
First disclosed
EPSSCVE-2026-10795: 3.6% (89.2th percentile)
Affected productsTeamUpdraft UpdraftPlus (UpdraftCentral remote management); TeamUpdraft UpdraftVault / UpdraftClone / TeamUpdraft customer accounts
Weaknesses (CWE)CWE-347, CWE-522
MalwarePHP
MITRE ATT&CK techniquesT1036.005 Match Legitimate Resource Name or Location, T1059 Command and Scripting Interpreter, T1070 Indicator Removal, T1071.001 Web Protocols, T1078 Valid Accounts, T1098 Account Manipulation, T1136.001 Local Account, T1195 Supply Chain Compromise, T1199 Trusted Relationship, T1505 Server Software Component, T1550 Use Alternate Authentication Material, T1552.004 Private Keys and 2 more in the attack flow
MotivationUNKNOWN
Target sectorstechnology, news - media, retail, education, government administration, small-business
Target regionsGlobal
Detection rules9 (1 shown free)
Sources9 cited sources

Detection coverage

As of 2026-10-24, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-3995 across Splunk SPL, Microsoft KQL and Sigma, covering 45 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: UpdraftCentral Stolen-Key Signed RPC Delivery (plugin.upload_plugin) — Exploitation

TL-2026-3995: finds POSTs to WordPress sites with the User-Agent 'WordPress/x.y; class-udrpc.php' that lacks the library version/URL of genuine UpdraftCentral dashboard traffic (WordPress/6.8.5; class-udrpc.php/2.0; https://teamupdraft.com). Attackers holding stolen TeamUpdraft connection keys sent signed plugin.upload_plugin commands this way to install backdoor plugins; flags known delivery IPs 43.250.53.42 and 2a09:bac5:4e21:2e3c::49b:9.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1199, T1078, T1552.004
  • Data sources: apache_nginx_access_logs, index=web sourcetype=access_combined
  • Severity: critical
  • Confidence: high

Splunk SPL

index=web sourcetype=access_combined method=POST
| where match(useragent, "^WordPress/[0-9.]+; class-udrpc\.php$")
| eval known_ioc_ip=if(clientip IN ("43.250.53.42","2a09:bac5:4e21:2e3c::49b:9","178.83.37.220","178.83.37.243","178.94.218.31"), 1, 0)
| stats count AS requests min(_time) AS first_seen max(_time) AS last_seen values(status) AS statuses values(uri_path) AS paths max(known_ioc_ip) AS known_ioc_ip BY host clientip useragent
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| table first_seen last_seen host clientip useragent requests statuses paths known_ioc_ip
| sort - known_ioc_ip - requests

Microsoft KQL

W3CIISLog
| where TimeGenerated > ago(24h)
| where csMethod == "POST"
| where csUserAgent matches regex @"^WordPress/[0-9.]+;[ +]class-udrpc\.php$"
| extend KnownIocIp = cIP in ("43.250.53.42", "2a09:bac5:4e21:2e3c::49b:9", "178.83.37.220", "178.83.37.243", "178.94.218.31")
| summarize Requests = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Statuses = make_set(scStatus), Uris = make_set(csUriStem, 10) by Computer, sSiteName, cIP, csUserAgent, KnownIocIp
| project FirstSeen, LastSeen, Computer, sSiteName, cIP, csUserAgent, Requests, Statuses, Uris, KnownIocIp
| order by KnownIocIp desc, Requests desc

Sigma

title: UpdraftCentral Signed RPC Delivery With Stripped Library User-Agent
id: 7c1f2d54-3a9e-4b6d-8e21-5f0a9b3c6d11
status: experimental
description: Detects POST requests carrying the attacker User-Agent 'WordPress/6.4; class-udrpc.php' (no class-udrpc.php library version or URL, unlike genuine UpdraftCentral dashboard traffic) used to deliver signed plugin.upload_plugin commands with stolen TeamUpdraft connection keys, or any request from known delivery IPs.
references:
    - https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/
    - https://nethemba.com/updraftcentral-backdoor-analysis/
    - https://teamupdraft.com/blog/security-incident-october-2026/
author: Threadlinqs Team
date: 2026-10-21
tags:
    - attack.initial-access
    - attack.t1199
    - attack.t1078
    - attack.credential-access
    - attack.t1552.004
logsource:
    category: webserver
detection:
    selection_ua:
        cs-method: POST
        cs-user-agent|startswith: 'WordPress/'
        cs-user-agent|contains: 'class-udrpc.php'
    filter_legit:
        cs-user-agent|contains: 'class-udrpc.php/'
    selection_ip:
        c-ip:
            - '43.250.53.42'
            - '2a09:bac5:4e21:2e3c::49b:9'
    condition: (selection_ua and not filter_legit) or selection_ip
falsepositives:
    - Custom internal tooling that reuses a WordPress-style User-Agent containing class-udrpc.php without a version
level: high

Known false positives:

  • Self-hosted management tooling using a stripped class-udrpc.php User-Agent
  • Security scanners replaying the published attacker User-Agent

Tuning notes: Point index/sourcetype at your web tier (Apache/nginx combined format). Keep the IOC IP list current; the User-Agent regex already excludes genuine dashboard traffic that carries class-udrpc.php/<version>. As a preventive control, block requests with udrpc_message via an mu-plugin and upgrade to UpdraftPlus 1.26.13/2.26.13.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • UpdraftCentral Signed RPC Delivery With Stripped User-Agent (Sentinel) — Exploitation · unlock with TL Creds
  • WordPress Rogue Admin/Editor Creation and Backdoor Options in MySQL Audit — Post-Exploitation · unlock with TL Creds
  • WordPress Backdoor Trigger Token Requests (Sentinel) — C2 / Access · unlock with TL Creds
  • Sigma: UpdraftCentral Signed RPC Delivery With Stripped User-Agent — Exploitation · unlock with TL Creds
  • Sigma: WordPress Backdoor Plugin File Creation — Post-Exploitation · unlock with TL Creds
  • Sigma: WordPress Backdoor Trigger Token Request — C2 / Access · unlock with TL Creds
  • UpdraftCentral Campaign Backdoor Plugin File Creation — Post-Exploitation · unlock with TL Creds
  • WordPress Backdoor Trigger Token Requests (Login Bypass) — C2 / Access · unlock with TL Creds

Indicators of compromise

As of 2026-10-24, Threadlinqs Intelligence tracks 45 indicators of compromise for TL-2026-3995.

Sample indicators (3 of 45)

  • IP address: 43.250.53[.]42
  • File hash: 59231b0e5004672b3058b47b4b4ff2b1fa89f1961bedf1741ba285e8adbe4928
  • IP address: 178.83.37[.]220

Defanged, TLP:CLEAR. Full set of 45 indicators: unlock with TL Creds.

45 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

On the weekend of 17-18 October 2026 an unauthorized party accessed TeamUpdraft's website and customer database. TeamUpdraft states the exposed data included names, email addresses, billing addresses, order history, hashed account passwords, two-factor authentication settings, and the connection keys for UpdraftCentral, UpdraftVault and UpdraftClone. Card details (processed by Stripe/PayPal), the UpdraftPlus plugin code itself and remote backups were reported as not compromised. Nethemba reports the keys include valid RSA private keys able to sign UpdraftCentral commands; keys do not expire (keys from November 2025 still worked in October 2026, and some from February 2022 were confirmed active).

Using the stolen keys, the attacker sent signed commands over UpdraftCentral's RPC channel (ordinary POST requests to the site root, parsed by class-udrpc.php) with the command plugin.upload_plugin. Patchstack notes the commands were correctly encrypted and signed with genuine dashboard private keys, so every plugin version, including 1.26.11 and 2.26.11, accepts them. The first installation was observed on 2026-10-18 at 15:32 UTC and the last at 2026-10-19 at 09:23, an roughly 18-hour campaign window in which 99 distinct plugin names were deployed. The attacker traffic carried a User-Agent of 'WordPress/6.4; class-udrpc.php' lacking the library version and URL that legitimate dashboard traffic carries, and came from 43.250.53.42 (plus an IPv6 address); Patchstack reports the attacker rotated infrastructure within a single day.

Nethemba documented three backdoor variants. Variant 1 (plugin names like load-stack-35c, text-gantry-eb0) creates an Editor-role account with manage_options and install_plugins capabilities, uses a 32-character token in a URL parameter of the form _ plus 6 hex characters, and contained a fatal PHP bug that crashed some sites (HTTP 500). Variant 2 (single-file plugins such as opt4fix, cache-smith, boost-kit) uses a 12-hex-character trigger parameter; without extra arguments it logs in the first existing administrator, and with m=setup it creates a full administrator and stores its ID in a <slug>_uid option. Variant 3 is a minimal ~673-byte single file (site-health-364f, site-health-cache) that logs in an existing admin or creates a hidden account and hides itself via all_plugins and pre_user_query filters. All variants log the attacker in with wp_set_auth_cookie (14-day remember-me cookie), bypassing 2FA, login limits and security plugins; created accounts survive removal of the plugin. The Patchstack-identified plugin description 'Small maintenance toolkit: keeps option storage tidy.' is the most reliable plugin indicator.

Vendor response: UpdraftPlus 1.26.12/2.26.12 auto-disconnected legacy sessions (but had a bug preventing key removal) and 1.26.13/2.26.13, released 19 October after 10pm BST, revoke old connection keys. Estimated exposure is about 400,000 sites (about 10% of UpdraftPlus's 4+ million installations). CVE-2026-10795 (CVSS 8.1, UpdraftPlus <=1.26.4 UpdraftCentral RPC signature-verification bypass, fixed in 1.26.5 in June 2026) is a separate earlier flaw in the same RPC channel; the sources describe the October campaign as abuse of genuine stolen keys, not exploitation of that CVE. No named threat actor has been attributed.

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1036.005 Match Legitimate Resource Name or Location; T1070 Indicator Removal; T1550 Use Alternate Authentication Material; T1564 Hide Artifacts

Execution

T1059 Command and Scripting Interpreter

Command and Control

T1071.001 Web Protocols

Initial Access

T1078 Valid Accounts; T1195 Supply Chain Compromise; T1199 Trusted Relationship

Persistence

T1098 Account Manipulation; T1136.001 Local Account; T1505 Server Software Component

Privilege Escalation

T1098 Account Manipulation

Credential Access

T1552.004 Private Keys

credential-access

T1606 Forge Web Credentials

Remediation

Patches

  • Update UpdraftPlus to 1.26.13 (free) or 2.26.13 (Premium) or later; 1.26.12/2.26.12 has a key-removal bug
  • Ensure UpdraftPlus is at 1.26.5/2.26.5 or later to address CVE-2026-10795

Immediate actions

  • Delete UpdraftCentral connection keys (Settings > UpdraftPlus Backups > Advanced Tools > UpdraftCentral, or 'wp option delete updraft_central_localkeys')
  • Remove sites from the UpdraftCentral Cloud dashboard and reconnect with new keys only if needed
  • Change the teamupdraft.com account password, reset 2FA and revoke all sessions
  • Search web access logs for requests with User-Agent containing 'class-udrpc.php' lacking a library version, and for 32-character token URL parameters
  • Audit WordPress administrators and any Editor accounts holding manage_options or install_plugins; review wp-content/plugins and mu-plugins for unknown plugins

Workarounds

  • Deploy a mu-plugin that returns HTTP 403 when $_POST['udrpc_message'] is set to block UpdraftCentral RPC
  • If compromised, delete backdoor plugin folders manually rather than via admin uninstall, remove rogue users and leftover options, and restore from a pre-17-October backup

Longer-term hardening

  • Rotate storage credentials (UpdraftVault, remote storage) and all administrator passwords
  • Enforce least privilege and restrict remote-management channels to allow-listed sources
  • Alert on plugin installations without a matching administrator action and on new users with example.org/example.com emails
  • Compare file checksums against clean installations and keep offline backups

Affected and fixed versions

  • TeamUpdraft — UpdraftPlus (UpdraftCentral remote management)
    Vulnerable versions: All versions with active UpdraftCentral keys, including 1.26.11 / 2.26.11 and earlier; CVE-2026-10795: <= 1.26.4
    Fixed in: 1.26.13 (free); 2.26.13 (Premium); CVE-2026-10795 fixed in 1.26.5 / 2.26.5
  • TeamUpdraft — UpdraftVault / UpdraftClone / TeamUpdraft customer accounts
    Vulnerable versions: Customer data and connection keys exposed in 17-18 October 2026 database breach
    Fixed in: Keys revoked in UpdraftPlus 1.26.13 / 2.26.13; reconnect with new credentials

Timeline

Last updated · 2 updates · revalidated 2× · latest source

  • Earliest UpdraftCentral connection keys later found still valid were issued as far back as November 2025 (Patchstack); many sites were enrolled via a default-checked box on TeamUpdraft.com login.
  • CVE-2026-10795 (CVSS 8.1), an UpdraftCentral RPC signature-verification bypass affecting UpdraftPlus <= 1.26.4, is published; fixed in 1.26.5. Sources treat it as separate from the October key-theft campaign.
  • Unauthorized access to TeamUpdraft's website and customer database begins over the weekend of 17-18 October.
  • First backdoor plugin installation via a signed UpdraftCentral plugin.upload_plugin command observed at 15:32 UTC; a probe on one monitored site is sent at 23:10.
  • Nethemba and Patchstack publish technical analyses with IOCs; Patchstack deploys mitigation. UpdraftPlus 1.26.13/2.26.13 released after 10pm BST to revoke old connection keys.
  • TeamUpdraft discloses the breach; UpdraftPlus 1.26.12/2.26.12 auto-disconnects legacy sessions but has a key-removal bug.
  • Last observed backdoor installation at 09:23, ending an ~18-hour window with 99 distinct plugin names deployed; broken Variant 1 plugins crash some sites with HTTP 500.
  • TeamUpdraft updates its incident page (16:25 BST): access route closed, vulnerability patched, accounts signed out, credentials and payment provider keys rotated, ICO notified.
  • Backdoor trigger attempts from locked-ioc-16, locked-ioc-17 and locked-ioc-18 are seen against sites where the plugins were already removed; BleepingComputer reports ~400,000 potentially exposed sites and TeamUpdraft updates its advisory.
  • Analysts warn the 1.26.13/2.26.13 update does not remove installed backdoors or rogue accounts and may leave a gap for keys created 12:07-21:00 UTC on 18 October that require manual deletion.

Update history

Sources cited

Other reports on CVE-2026-10795

Previous and next in supply chain

Further reading

Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats