arXiv:2605.02346cs.CRcs.AI2026-05被引 1

首个实现工业物联网设备自主攻防的LLM框架,90%成功率完成漏洞发现到修复闭环。

APIOT: Autonomous Vulnerability Management Across Bare-Metal Industrial OT Networks

  • 用LLM直接解析协议字段,设计新动作空间实现裸金属设备自主攻击。
  • 在290次实验中达成90.0%的攻防闭环成功率,验证框架有效性。
  • 提出运行时监管机制,防止代理陷入重复循环或检测遗漏等失效模式。

裸金属工业控制设备(尤其是运行Modbus/TCP和CoAP的微控制器)长期未被自主安全攻击覆盖。现有自主渗透测试聚焦于具备外壳和文件系统的Linux与Web系统,而裸金属OT缺乏此类接口,需让大语言模型直接基于协议字段与解析语义进行推理。这要求新的动作空间设计与运行时管控机制,并引发关于协议级漏洞推理及其部署边界的全新研究问题。本文提出APIOT(工业OT自主紫队),首个展示大语言模型对裸金属工业OT设备实现自主攻击与修复的框架,可在无逐步人工干预下完成完整发现→利用→打补丁→验证循环。我们在不同工业物联网拓扑中对Zephyr RTOS固件进行了实现与评估,通过290次实验覆盖五种前沿大模型、三种网络拓扑、两种干扰水平以及有引导与无引导条件。结果显示,APIOT在完整攻防周期中取得90.0%的任务成功率。研究发现,运行时治理层(称作‘监督者’)是关键工程变量:无该机制时,代理表现出系统性退化行为,如重复循环、漏掉崩溃验证、侦察死锁。这些结果提示两个更广泛意义:裸金属OT攻击不再受限于人力技能,防御方威胁模型必须假设具备大模型增强能力的对手,可执行从发现到修复的自主攻防循环。

原文摘要 · Abstract (English)

Bare-metal operational technology (OT) devices -- especially the microcontrollers running Modbus/TCP and CoAP at the base of industrial control systems -- have remained outside the reach of autonomous security attacks. Prior autonomous pentesting studies target Linux and web systems, whose shells and filesystems are familiar to LLM agents. Bare-metal OT has neither, so agents must reason directly over protocol fields and parser semantics. This requires new action-space designs and runtime controls, and opens new research questions about protocol-level exploit reasoning and its deployment envelope. We present APIOT (Autonomous Purple-teaming for Industrial OT), the first large language model (LLM) framework demonstrating an autonomous attack and remediation of bare-metal OT devices, achieving the full discovery -> exploitation -> patching -> verification cycle without step-by-step human intervention. We implemented and evaluated this framework on Zephyr RTOS firmware across heterogeneous industrial IoT (IIoT) topologies. Through 290 experiment runs spanning five frontier LLMs, three network topologies, two impairment levels, and guided versus unguided conditions, APIOT achieved a mission success rate of 90.0% on the full attack-remediation cycle. We found that the runtime governance layer (which we call an overseer) is a critical engineering variable: without it, agents exhibit systematic degenerate patterns, including repetition loops, missing crash verification, and reconnaissance deadlocks. Together, these findings carry two implications beyond our testbed. Attacker expertise is no longer the binding constraint on bare-metal OT exploitation, and defender threat models must now assume LLM-augmented adversaries capable of executing autonomous discovery-through-remediation cycles against industrial firmware.

工业安全大模型自主攻防固件漏洞

Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。