Skip to navigation

Threat reportThreat IntelligenceTL-2026-6150

exploit_agent: AI-driven patch-diffing framework autonomously discovers, weaponizes and executes web application exploits (GTIG)

highACTIVE

Google Threat Intelligence Group (GTIG) found an exposed staging server hosting 'exploit_agent', a multi-agent framework that uses frontier and local LLMs to diff web application software before and after patch announcements, draft exploits and execute them with no human in the loop.

Key facts

IdentifiersTL-2026-6150, CVE-2026-7465
Also known asexploit_agent
SeverityHIGH
First disclosed
EPSSCVE-2026-7465: 1.1% (68.0th percentile)
Affected productsVarious Popular web application software (framework targets patch-diffed web applications; French media/entertainment and education sites observed); Brainstorm Force Spectra (Ultimate Addons for Gutenberg) WordPress plugin
Malwareexploit_agent
ToolsARTEX, Agent Zero, CAIRN, CyberStrikeAI, HexStrike AI, PentAGI, Strix
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1110 Brute Force, T1190 Exploit Public-Facing Application, T1505.003 Web Shell, T1583.004 Server, T1587.004 Exploits, T1588.006 Vulnerabilities, T1588.007 Artificial Intelligence, T1595.002 Vulnerability Scanning
MotivationUNKNOWN
Target sectorsnews - media, entertainment, education
Target regionsfrance
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-11-16, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6150 across Splunk SPL, Microsoft KQL and Sigma, covering 10 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: exploit_agent — Spectra Popup REST Route Probing and Write Requests

Behaviour-first search (TL-2026-6150) for automated probing or write-method requests to the Spectra (Ultimate Addons for Gutenberg) REST route /wp/v2/spectra-popup, the access-control target (restrict_popup_rest_access, v21925.php) GTIG showed exploit_agent analysing. Flags request bursts or successful writes per source and 15-minute window. The route is an analysis target, not a confirmed exploitation indicator.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1595.002
  • Data sources: splunk:index=web:access_combined, splunk:index=web:ms:iis:auto, splunk:index=web:nginx:plus:kv, W3CIISLog
  • Severity: high
  • Confidence: medium

Splunk SPL

index=web sourcetype IN ("access_combined","ms:iis:auto","nginx:plus:kv") "spectra-popup"
```Spectra REST route wp/v2/spectra-popup guarded by restrict_popup_rest_access in v21925.php was analysed by exploit_agent```
| eval src=coalesce(clientip,c_ip,src_ip), meth=upper(coalesce(method,cs_method)), code=tostring(coalesce(status,sc_status))
| eval is_write=if(match(meth,"^(POST|PUT|PATCH|DELETE)$"),1,0), is_ok_write=if(is_write=1 AND match(code,"^(200|201|204)$"),1,0)
| bin _time span=15m
| stats count AS requests sum(is_write) AS write_requests sum(is_ok_write) AS successful_writes values(meth) AS methods values(code) AS statuses by _time, host, src
| where requests>=10 OR successful_writes>=1
| table _time host src requests write_requests successful_writes methods statuses

Microsoft KQL

W3CIISLog
| where TimeGenerated > ago(24h)
| where csUriStem has "spectra-popup" or csUriQuery has "spectra-popup"
| extend IsWrite = csMethod in~ ("POST", "PUT", "PATCH", "DELETE")
| summarize Requests = count(), WriteRequests = countif(IsWrite), SuccessfulWrites = countif(IsWrite and scStatus in ("200", "201", "204")), Methods = make_set(csMethod), Statuses = make_set(scStatus), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by cIP, sSiteName, bin(TimeGenerated, 15m)
| where Requests >= 10 or SuccessfulWrites >= 1
| project TimeGenerated, sSiteName, cIP, Requests, WriteRequests, SuccessfulWrites, Methods, Statuses, FirstSeen, LastSeen

Sigma

title: Write-Method Request to Spectra Popup REST Route (exploit_agent Target)
id: 3f6a2c1e-8b74-4d09-a5e2-61c0b7d94a11
status: experimental
description: Detects POST, PUT, PATCH or DELETE requests to the WordPress REST route /wp/v2/spectra-popup of the Spectra (Ultimate Addons for Gutenberg) plugin, whose restrict_popup_rest_access check in v21925.php was analysed by exploit_agent (TL-2026-6150). This is an access-control analysis target and not a confirmed exploitation indicator.
references:
  - https://cloud.google.com/blog/topics/threat-intelligence/agentic-threat-activity-crosses-a-significant-threshold
  - https://www.theregister.com/research/2026/11/16/google-ai-agent-turned-a-security-patch-into-a-working-exploit-with-no-human-help/5309926
author: Threadlinqs Team
date: 2026-11-16
tags:
  - attack.initial-access
  - attack.t1190
  - attack.reconnaissance
  - attack.t1595.002
logsource:
  category: webserver
detection:
  selection_route:
    c-uri|contains: 'spectra-popup'
  selection_method:
    cs-method:
      - 'POST'
      - 'PUT'
      - 'PATCH'
      - 'DELETE'
  condition: selection_route and selection_method
falsepositives:
  - Authenticated editors saving popup content through the WordPress block editor
  - Authorised vulnerability scanning of the site
level: medium

Known false positives:

  • Authenticated editors saving popups through the block editor generate write requests
  • Authorised vulnerability scanners or uptime monitors requesting the route repeatedly

Tuning notes: Exclude authenticated admin/editor source ranges and known scanner IPs; lower the request threshold (10 per 15 min) on low-traffic sites; adjust the index and sourcetype to your web log pipeline; combine with WAF logs to separate unauthenticated requests. Expect the route to be probed by many scanners after any Spectra advisory.

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)
  • exploit_agent — Automated Brute Force Against WordPress Login and XML-RPC · unlock with TL Creds
  • exploit_agent — Web Server Process Spawning Shell or Recon Utility · unlock with TL Creds
  • exploit_agent — Agentic Offensive Framework Execution · unlock with TL Creds
  • exploit_agent — Webshell Access via PHP in WordPress Uploads Directory · unlock with TL Creds
  • exploit_agent — Brute-Force and Recon Tools Launched From Web Server Context · unlock with TL Creds
  • exploit_agent — Unexpected Local LLM Inference Service on Server · unlock with TL Creds
  • exploit_agent — Webshell Written or Rival Webshell Removed by Web Server Process · unlock with TL Creds
  • exploit_agent — Server-Side Process Contacting LLM Provider APIs · unlock with TL Creds

Indicators of compromise

As of 2026-11-16, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-6150.

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

Technical analysis

GTIG calls this the first time it has seen vulnerability discovery and exploitation fully automated this way. The operator showed Russian-language indicators and appeared interested in French media/entertainment websites and the education sector.

On 2026-11-16 GTIG published its AI Threat Tracker ('Agentic threat activity crosses a significant threshold'). It reports an exposed staging server that hosted exploit_agent, a multi-agent vulnerability research and weaponization framework integrated with multiple frontier and local LLMs. The framework is configured to run continuous differential analysis of popular web application software. It compares code before and after patch announcements, analyzes the differences to find potential vulnerabilities, drafts exploits and executes them automatically. GTIG states this is the first time it has identified threat actors using LLM frameworks to fully automate vulnerability discovery and exploitation without a human in the loop.

The staging server also held data exfiltrated from victim organizations and several post-compromise scripts. These covered internal reconnaissance, brute-forcing, installing webshells and removing other attackers' webshells. A configuration file carried the Russian comment '# LLM API-ключи для авто-эксплуатации (пилот exploit_agent)' ('LLM API keys for auto-exploitation (exploit_agent pilot)'), with further Russian instructions to enter the keys directly. Victim telemetry suggests the operator was interested in French websites in the media and entertainment industries and in the education sector. The sources name no victims, victim counts, CVEs, IP addresses, domains or file hashes, and no named actor. Attribution is limited to a suspected Russian-speaking operator, so confidence is low.

As an example of the framework's output, GTIG shows it inspecting access control in the Spectra (Ultimate Addons for Gutenberg) WordPress plugin v2.19.25. The figure shows the restrict_popup_rest_access function in v21925.php, which guards the REST route /wp/v2/spectra-popup, flagged as an insecure capability check. GTIG gives no CVE for this and does not say it was exploited in the wild. A separate Wordfence entry (CVE-2026-7465, authenticated Contributor+ RCE in Spectra <= 2.19.25) was not tied to exploit_agent by any source reviewed, so it is not listed as this threat's CVE.

GTIG places the finding in a wider shift to agentic offensive tooling. Other frameworks it names are ARTEX (Chinese-developed, open source, released July 2026), CAIRN (OODA-loop multi-agent pentesting, seen in intrusion activity including against US aerospace), CyberStrikeAI (Go-based C2 and orchestration for 100+ tools), HexStrike AI (MCP harness with 150+ tools) and PentAGI (a customized build used from late August to early October 2026 for reconnaissance and vulnerability scanning against organizations in Asia). PRC-nexus espionage actors are also experimenting with such frameworks. Press coverage describes a Chinese-speaking operator chaining Hermes, Strix and Cairn against 27+ companies in September 2026, and the use of ARTEX against South Korean financial organizations and against 123 Reg. These are context for the trend, not confirmed links to the exploit_agent operator.

Defensive implication: the window between a patch being published and exploitation shrinks because n-day exploits can be built by diffing patches automatically. Priorities are fast patching of internet-facing web applications (CMS plugins especially), webshell detection, rotation of credentials, and monitoring for unusual LLM service enablement and for 'burn and rotate' service account patterns.

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter

Credential Access

T1110 Brute Force

Initial Access

T1190 Exploit Public-Facing Application

Persistence

T1505.003 Web Shell

Resource Development

T1583.004 Server; T1587.004 Exploits; T1588.006 Vulnerabilities; T1588.007 Artificial Intelligence

Reconnaissance

T1595.002 Vulnerability Scanning

Remediation

Patches

  • Keep WordPress core and plugins, including Spectra (Ultimate Addons for Gutenberg), on the latest vendor releases

Immediate actions

  • Prioritize patching of internet-facing web applications and CMS plugins as soon as vendor fixes are released, since patch diffs can be weaponized quickly
  • Hunt web roots for unexpected webshells and for the removal or replacement of existing webshells
  • Rotate credentials and session tokens on any web server suspected of compromise
  • Review web server and WAF logs for automated scanning and brute-force activity following patch releases

Workarounds

  • Restrict or WAF-filter unauthenticated access to plugin REST routes such as /wp/v2/spectra-popup where the plugin cannot be updated immediately
  • Use file integrity monitoring on web roots

Longer-term hardening

  • Shorten the interval between vendor patch disclosure and deployment
  • Monitor for unusual LLM service enablement and 'burn and rotate' service account patterns
  • Apply Mandiant's hardening guidance for LLM-enabled offensive tooling
  • Deploy behavioral and volumetric detection for automated agentic scanning and exploitation activity

Affected and fixed versions

  • Various — Popular web application software (framework targets patch-diffed web applications; French media/entertainment and education sites observed)
  • Brainstorm Force — Spectra (Ultimate Addons for Gutenberg) WordPress plugin
    Vulnerable versions: 2.19.25 (analyzed by exploit_agent per GTIG; no CVE or exploitation stated)

Timeline

  • The Register reports criminals boasting of using the HexStrike AI offensive harness against Citrix bugs (context for the wider agentic-tooling trend).
  • ARTEX, an open-source Chinese-developed agentic pentesting tool, is released (July 2026, exact day not stated).
  • Per press coverage of Gambit research, a Chinese-speaking operator begins large-scale Strix scanning (Aug 23-31); Cairn later compromises 27+ companies (Sep 10-15). Related campaign, not linked to exploit_agent.
  • Per GTIG, a customized PentAGI-based platform is used from late August to early October 2026 for reconnaissance and vulnerability scanning against organizations in Asia (start date approximate).
  • Intrusion into UK registrar 123 Reg, which says the attacker used ARTEX and AI attack skills hosted on Chinese infrastructure.
  • CrowdStrike publishes CSA-261162 linking ARTEX to activity against South Korean financial organizations beginning in late September 2026.
  • GTIG publishes its AI Threat Tracker disclosing the exposed exploit_agent staging server and calls it the first observed fully autonomous AI-driven vulnerability discovery and exploitation; The Register reports the same day.

Sources cited

Previous and next in threat intel

Drafted by the Threadlinqs research pipeline from 7 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