Threat reportToolTL-2026-1261
VEXAIoT: Autonomous Multi-Agent LLM Framework Automates End-to-End IoT Vulnerability Discovery and Exploitation (95% Success Rate)
Academic researchers (Swinea, Aryal, Praharaj, Gupta) published VEXAIoT, a two-agent LLM framework (ChatGPT 5.1 thinking) that chains Nmap reconnaissance, Searchsploit/Exploit-DB lookups, Bettercap, and John the Ripper into autonomous, dependency-aware IoT attack plans.
Key facts
| Identifiers | TL-2026-1261, CVE-2011-2523, CVE-2004-2687, CVE-2019-12108, CVE-2019-12109, CVE-2019-12110, CVE-2019-12111, CVE-2020-28951 |
|---|---|
| Also known as | VEXAIoT, Vulnerability EXploitation using AI Agents, VEXA_IoT |
| Severity | MEDIUM |
| Exploitation status | Public proof-of-concept exploit for a linked CVE |
| EPSS | CVE-2011-2523: 96.1% (99.8th percentile); CVE-2004-2687: 80.9% (99.5th percentile); CVE-2019-12111: 3.4% (87.4th percentile) |
| Affected products | OWASP IoTGoat; Rapid7 / community Metasploitable2; MiniUPnP Project MiniUPnP daemon; vsftpd project (trojaned archive) vsftpd; distcc distccd; OpenWrt libuci |
| Weaknesses (CWE) | CWE-798, CWE-77, CWE-79, CWE-284, CWE-494, CWE-476, CWE-416, CWE-306 |
| Malware | vsftpd 2.3.4 trojaned backdoor |
| Tools | Bettercap, Exploit-DB, John the Ripper, Nmap, Searchsploit, VEXAIoT |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1041 Exfiltration Over C2 Channel, T1046 Network Service Discovery, T1059.004 Unix Shell, T1068 Exploitation for Privilege Escalation, T1071 Application Layer Protocol, T1078.001 Default Accounts, T1082 System Information Discovery, T1110.002 Password Cracking, T1190 Exploit Public-Facing Application, T1495 Firmware Corruption, T1498 Network Denial of Service and 10 more in the attack flow |
| Motivation | UNKNOWN |
| Target sectors | technology, iotmanufacturing, criticalinfrastructure, consumerelectronics, researchacademia |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 9 cited sources |
Detection coverage
As of 2026-07-13, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1261 across Splunk SPL, Microsoft KQL and Sigma, covering 24 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: vsftpd 2.3.4 Trojaned Backdoor Login Trigger and distccd Unauthenticated RCE
Detects the two Metasploitable2-class exploitation primitives VEXAIoT automated during post-exploitation: an FTP login attempt containing the vsftpd 2.3.4 smiley-face backdoor trigger sequence (CVE-2011-2523) and distccd spawning a shell interpreter as a child process consistent with unauthenticated command execution (CVE-2004-2687).
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1190, T1078.001, T1059.004
- Data sources: linux_secure, ftp_logs, sysmon, DeviceProcessEvents, DeviceNetworkEvents
- Severity: critical
- Confidence: high
Splunk SPL
index=network sourcetype IN (linux_secure, ftp_logs, sysmon) (CommandLine="*/bin/sh*" ParentImage="*distccd*") OR (Message="*USER*:)*" OR Message="*USER *)*" service="ftp")
| eval detection_reason=case(match(ParentImage, "distccd"), "distccd_rce_CVE-2004-2687", match(Message, "\)\)\)|:\)"), "vsftpd_backdoor_trigger_CVE-2011-2523", 1=1, "other")
| where detection_reason!="other"
| table _time host user CommandLine ParentImage Message detection_reasonMicrosoft KQL
let distcc_rce = DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName has "distccd" and ProcessCommandLine has_any ("/bin/sh", "id;")
| project Timestamp, DeviceName, ProcessCommandLine, InitiatingProcessFileName, DetectionReason="distccd_rce_CVE-2004-2687";
let vsftpd_trigger = DeviceNetworkEvents
| where Timestamp > ago(24h)
| where RemotePort == 21 and AdditionalFields has ":)"
| project Timestamp, DeviceName, ProcessCommandLine=tostring(AdditionalFields), InitiatingProcessFileName="vsftpd", DetectionReason="vsftpd_backdoor_trigger_CVE-2011-2523";
distcc_rce
| union vsftpd_triggerSigma
title: distccd Unauthenticated Command Execution (CVE-2004-2687)
id: 7c3a1e2a-1f4b-4b7e-9a0e-1d2c3b4a5f02
status: experimental
description: Detects distccd spawning a shell interpreter as a direct child process, consistent with unauthenticated remote command execution via CVE-2004-2687, as automated by VEXAIoT's Attack Execution Agent against Metasploitable2-class targets.
references:
- https://nmap.org/nsedoc/scripts/distcc-cve2004-2687.html
- https://arxiv.org/abs/2607.09653
author: Threadlinqs Team
date: 2026-07-13
tags:
- attack.initial-access
- attack.t1190
- attack.execution
- attack.t1059.004
- cve.2004.2687
logsource:
category: process_creation
product: linux
detection:
selection:
ParentImage|endswith: '/distccd'
CommandLine|contains:
- '/bin/sh'
- 'id;'
condition: selection
falsepositives:
- Legitimate distributed compilation jobs (distcc used as intended within a trusted, access-controlled build network)
level: highKnown false positives:
- Legitimate distcc build-farm traffic from trusted internal build servers
- FTP clients that happen to include a colon-parenthesis sequence in a legitimate username by coincidence
Tuning notes: Restrict distccd child-shell alerting to hosts outside the approved build-network CIDR; require distccd hardening (--allow flag) or full decommission where not operationally required.
- OpenWrt [indicator] / MiniUPnP Crash-Loop Exploitation (IoTGoat-class Devices) · unlock with TL Creds
- Hardcoded/Default Credential Access Followed by Local Password-Cracking Utility Execution · unlock with TL Creds
- Rapid Automated Log-Clearing Immediately Following Exploit/RCE Activity · unlock with TL Creds
- MiniUPnP / [indicator] / [indicator] Rapid Multi-Service Scan Preceding Exploit (Exploitation Phase) · unlock with TL Creds
- MiniUPnP Backdoor/Service Abuse and Developer-Backdoor Interface Access (Post-Exploitation Phase) · unlock with TL Creds
- Adversary-in-the-Middle ARP/DHCP Spoofing and Credential Interception (C2/Lateral Movement Phase) · unlock with TL Creds
- Agentic Recon-to-Exploit Command Sequencing (VEXAIoT-class Chaining) · unlock with TL Creds
- [indicator] 2.3.4 Backdoor Shell Established on TCP/6200 · unlock with TL Creds
Indicators of compromise
As of 2026-07-13, Threadlinqs Intelligence tracks 24 indicators of compromise for TL-2026-1261.
Technical analysis
Tested against IoTGoat and Metasploitable2 across 260 executions covering 10 OWASP IoT Top 10 attack scenarios (hardcoded password cracking, MiniUPnP backdoor abuse, XSS injection, developer backdoor access, malicious firmware update execution, DNS DoS, database PII extraction, MitM credential interception, log erasure, and RCE), it achieved a 95% overall success rate (94.5% on IoTGoat, 96.7% on Metasploitable2) with most attacks completing in under two minutes and low token overhead (460-1,480 tokens/attack).
VEXAIoT ("Vulnerability EXploitation using AI Agents") is a research framework published on arXiv (2607.09653, submitted 2026-07-10, CC BY 4.0) by Katherine Swinea, Kshitiz Aryal, Lopamudra Praharaj, and Maanak Gupta, first reported publicly by Cyber Security News on 2026-07-13. The system decomposes offensive IoT security assessment into a modular multi-agent pipeline: reconnaissance -> vulnerability mapping -> attack planning -> execution -> validation.
Architecturally, VEXAIoT uses two cooperating agents built on ChatGPT 5.1 ("thinking" reasoning mode): a Vulnerability Detection Agent that runs Nmap-driven reconnaissance to enumerate hosts, open ports, exposed services, and software versions, then correlates discovered software against known CVEs via Searchsploit and Exploit-DB; and an Attack Execution Agent that consumes the detection agent's findings, selects an appropriate offensive tool (Nmap NSE scripts, Searchsploit-sourced PoC exploits, Bettercap for MITM/traffic interception, John the Ripper for password cracking), generates the exact command sequence, executes it, and validates success using LLM-based interpretation of tool output. When a command fails, the LLM revises its approach using error-message feedback and retry logic rather than following a rigid, pre-scripted playbook -- the paper's central claim of novelty versus prior CTF-focused LLM pentesting tools such as PentestGPT, AutoAttacker, and AutoPentester.
The authors deliberately used functional, non-malicious tool-description framing in their prompts specifically to reduce LLM safety-refusal behavior during offensive tasking -- a prompt-engineering technique with dual-use implications for real-world adversarial automation, since it demonstrates a working method to lower a commercial LLM's resistance to producing exploit commands.
Evaluation targeted two intentionally vulnerable testbeds: IoTGoat (OWASP's deliberately insecure OpenWrt-based IoT firmware, containing MiniUPnP 2.1 DoS flaws CVE-2019-12108/12109/12110/12111 and libuci use-after-free CVE-2020-28951) and Metasploitable2 (a classic vulnerable Linux distribution whose exploited services in this study align with the well-known vsftpd 2.3.4 backdoor CVE-2011-2523 and distcc remote command execution CVE-2004-2687). Across 260 total execution runs mapped to 10 OWASP IoT Top 10 categories, VEXAIoT achieved 247/260 (95.0%) successful exploitations: 189/200 (94.5%) on IoTGoat and 58/60 (96.7%) on Metasploitable2. Seven of ten scenarios (XSS injection, developer backdoor access, malicious update execution, database PII extraction, log erasure, and RCE) reached 100% success; MiniUPnP backdoor abuse and DNS DoS scenarios lagged at 80% due to command-syntax generation errors and model refusals. Parallelized execution completed all 10 attack scenarios in ~3 minutes 50 seconds versus ~8 minutes 31 seconds sequentially. Of the 13 failures, the paper attributes 5 to model refusals, 5 to LLM-generated command syntax errors, and 1 to model hallucination (2 unaccounted/other in the reported breakdown).
No CVE was assigned to VEXAIoT itself (it is a research tool/methodology, not a vulnerability), and no threat-actor adoption or in-the-wild use has been reported. The risk profile is that of a capability-lowering dual-use tool: it demonstrates that commodity multi-agent LLM tooling can autonomously chain reconnaissance-to-exploitation against IoT/embedded Linux targets with high reliability and low cost, shortening the skill and time barrier previously required for manual IoT penetration testing or malicious exploitation. The authors explicitly scope the work to isolated, authorized testbeds and recommend production/real-world deployment safeguards: strict access controls, comprehensive action logging, mandatory human approval gates for sensitive actions, and technical guardrails preventing agents from reaching hosts outside an approved test scope. They acknowledge that autonomous exploit execution at scale requires stronger command validation and safety controls before any responsible real-world use, and note the study does not reflect production-network complexity (patched software, IDS/IPS, network segmentation, device heterogeneity) that would degrade success rates outside a lab.
MITRE ATT&CK techniques by tactic:
Collection
T1005 Data from Local System; T1557.003 DHCP Spoofing
Exfiltration
T1041 Exfiltration Over C2 Channel
Discovery
T1046 Network Service Discovery; T1082 System Information Discovery
Execution
Privilege Escalation
T1068 Exploitation for Privilege Escalation
Command and Control
T1071 Application Layer Protocol
Initial Access
T1078.001 Default Accounts; T1190 Exploit Public-Facing Application
Credential Access
T1110.002 Password Cracking; T1552.001 Credentials In Files; T1557 Adversary-in-the-Middle
Impact
T1495 Firmware Corruption; T1498 Network Denial of Service; T1565 Data Manipulation
Persistence
Resource Development
T1588.002 Tool; T1588.005 Exploits
Reconnaissance
T1592.002 Software; T1595.002 Vulnerability Scanning
defense-impairment
Remediation
Patches
- Apply MiniUPnP patches addressing CVE-2019-12108, CVE-2019-12109, CVE-2019-12110, CVE-2019-12111
- Apply OpenWrt libuci patch for CVE-2020-28951 (18.06.9+ / 19.07.5+)
- Remove/replace vsftpd builds affected by the 2011 backdoor trojan (CVE-2011-2523) with a clean, current vsftpd release
- Disable distccd or restrict to trusted build networks only, patching/mitigating CVE-2004-2687
Immediate actions
- Patch/replace known-vulnerable IoT and Linux services that map to the ten demonstrated OWASP IoT attack scenarios (weak/hardcoded credentials, exposed UPnP services, unauthenticated ecosystem interfaces, unsigned firmware update mechanisms, verbose DNS services, unencrypted data-in-transit, default/insecure configurations enabling RCE)
- Disable or firewall MiniUPnP and other UPnP services on IoT gateways/routers unless explicitly required, and patch to versions beyond CVE-2019-12108/12109/12110/12111
- Remove or upgrade vsftpd 2.3.4 and distccd installations still exposed on any Linux hosts (CVE-2011-2523, CVE-2004-2687) — legacy Metasploitable-class misconfigurations recur in real IoT/edge deployments
- Enforce unique, non-default credentials on all IoT/embedded management interfaces to blunt automated hardcoded-password-cracking attack chains
- Deploy network segmentation isolating IoT/OT devices from core enterprise networks to blunt lateral movement from any single compromised device
Workarounds
- Restrict management/API interfaces (UPnP, FTP, distcc, web admin) to trusted internal networks via firewall/ACL
- Disable unauthenticated remote administration on IoT devices where not operationally required
- Rate-limit and alert on rapid sequential port scans followed by service-specific exploit attempts from a single source
Longer-term hardening
- Deploy behavioral/EDR-style monitoring on IoT gateways and embedded Linux devices capable of detecting rapid, automated recon-to-exploit command sequences (Nmap sweeps followed by exploit tool invocation within seconds)
- Establish a firmware/software update validation and integrity-verification process (signed updates) to prevent malicious-update-style attack chains
- Adopt IoT-specific threat modeling aligned to the OWASP IoT Top 10 during procurement and device lifecycle management
- Track emerging LLM-driven offensive automation frameworks (VEXAIoT-class tooling) as a maturing threat category and update detection engineering accordingly
Affected and fixed versions
- OWASP — IoTGoat
Vulnerable versions: all released images with default MiniUPnP 2.1 / vulnerable libuci
Fixed in: not applicable — deliberately vulnerable training firmware - Rapid7 / community — Metasploitable2
Vulnerable versions: all released images (vsftpd 2.3.4, distccd)
Fixed in: not applicable — deliberately vulnerable training image - MiniUPnP Project — MiniUPnP daemon
Vulnerable versions: 2.1 and prior versions affected by CVE-2019-12108/12109/12110/12111
Fixed in: patched releases post-2019 disclosure - vsftpd project (trojaned archive) — vsftpd
Vulnerable versions: 2.3.4 (trojaned distribution, June 30-July 1 2011)
Fixed in: current official vsftpd releases - distcc — distccd
Vulnerable versions: configurations exposing distccd without access control (CVE-2004-2687)
Fixed in: restrict/disable distccd remote access - OpenWrt — libuci
Vulnerable versions: before 18.06.9 and 19.x before 19.07.5 (CVE-2020-28951)
Fixed in: 18.06.9+; 19.07.5+
Timeline
- distcc remote command execution vulnerability (CVE-2004-2687) disclosed; remains present in Metasploitable2 as a VEXAIoT test target
- Malicious backdoor trojan (CVE-2011-2523) inserted into the vsftpd 2.3.4 download archive, later used as one of VEXAIoT's Metasploitable2 test targets
- MiniUPnP 2.1 NULL pointer dereference DoS vulnerabilities (CVE-2019-12108/12109/12110/12111) disclosed, later included in IoTGoat's vulnerable service set
- OpenWrt libuci use-after-free vulnerability (CVE-2020-28951) disclosed, present in OpenWrt versions used by IoTGoat firmware
- PentestGPT (arXiv:2308.06782), an earlier LLM-empowered automatic penetration testing tool later presented at USENIX Security 2024, is submitted to arXiv; VEXAIoT's authors position their framework as advancing beyond PentestGPT's largely CTF-focused, more manually-guided approach toward fully autonomous end-to-end IoT exploitation
- Swinea, Aryal, Praharaj, and Gupta submit the VEXAIoT paper (arXiv:2607.09653), describing the multi-agent LLM framework and its 260-run IoTGoat/Metasploitable2 evaluation
- TL-Intel-Harness HUNT phase flags VEXAIoT via RSS ingestion (Cyber Security News feed) as an emerging AI-driven offensive-tooling threat relevant to SOC detection priorities
- Cyber Security News and Arabian Post publish articles covering VEXAIoT's 95% automated IoT exploitation success rate, bringing the research to broader security-community attention
Sources cited
- VEXAIoT: Autonomous IoT Vulnerability EXploitation using AI Agents (arXiv:2607.09653) arxiv.org · Research · 2026-07-10
- VEXAIoT arXiv HTML full text arxiv.org · Research · 2026-07-10
- VSFTPD 2.3.4 Backdoor Command Execution (Rapid7 module) Rapid7 · Vendor report · 2026-07-13
- distcc-cve2004-2687 NSE script — Nmap Scripting Engine documentation nmap.org · Vendor report · 2026-07-13
- PentestGPT: An LLM-empowered Automatic Penetration Testing Tool (arXiv:2308.06782) arxiv.org · Research · 2023-08-13
- OWASP/IoTGoat — deliberately insecure OpenWrt-based firmware GitHub · Code repository · 2026-07-13
- IoTGoat challenges wiki GitHub · Code repository · 2026-07-13
- VEXAIoT Automates IoT Reconnaissance cybersecuritynews.com · News · 2026-07-13
- AI agents automate IoT attacks with 95% success thearabianpost.com · News · 2026-07-13
Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.