Skip to content
Threat Feed
high threat

Adoption of Autonomous Agentic Frameworks for Offensive Operations

Multiple threat actors, including STORM-0940, are utilizing autonomous, LLM-driven offensive frameworks like ARTEX to conduct highly automated, high-velocity intrusions.

Triage facts

Revision 1
Applicability
Azure, AWS +2
Evidence
Unknown
Severity
High
Action
Elevated
Sources
4 public sources
Freshness
Revision 1Nov 1, 20:35 UTC
Source quality
A1Very likely

Threat actors are increasingly weaponizing agentic, LLM-driven offensive frameworks - specifically ARTEX, Hexstrike, and CAIRN - to automate multiple stages of the attack lifecycle. These tools translate high-level tactical goals into machine commands, enabling rapid execution of reconnaissance, privilege escalation, and lateral movement. Unlike human operators, these frameworks exhibit distinct forensic characteristics, such as executing complex tasks in compressed bursts (2-25 seconds) and relying on iterative trial-and-error that generates high log volumes.

Attack Chain

  1. Initial Access: Adversaries utilize compromised credentials to gain entry.
  2. Reconnaissance: Agentic frameworks profile target environments (e.g., Active Directory, cloud infrastructure/AWS security groups).
  3. Exploitation: Frameworks target specific services, such as Linux web servers, using exposed application-specific APIs.
  4. Execution/Persistence: Automated injection of malicious files; specifically, poisoning MySQL general logs via SET GLOBAL general_log_file to write webshells to public directories.
  5. Lateral Movement: Autonomous exploration and pivot execution between services.
  6. Exfiltration: Automated staging and preparation of stolen data.

Impact

Automated attack frameworks enable adversaries to move from initial access to deep system access in significantly reduced timeframes, with observed incidents occurring in as little as 15 minutes. The high-volume, iterative nature of agentic activity increases the speed and scale of data theft and infrastructure exploitation.

Recommendation

  • Implement control-plane isolation to prevent automated tools from harvesting cloud service credentials.
  • Enforce short-lived credentials and strict least-privilege policies to limit the scope of autonomous tool activity.
  • Implement network segmentation to disrupt the lateral movement paths frequently probed by automated agents.
  • Deploy behavioral analytics to detect rapid, burst-like execution patterns that deviate from human-paced administrative activity.

Immediate actions

Audit database service accounts for global configuration change privileges (e.g., SET GLOBAL general_log_file).

SOC 48h

Threat Hunt

Identify rapid bursts of administrative/API activity from a single service account.

high high confidence hunt now

Data: Database query logs (MySQL general logs), Cloud platform audit logs (AWS CloudTrail, Azure Activity Log)

Mitigations

Apply strict least-privilege to database service accounts and implement network segmentation between web and database tiers.

immediate IT Operations

Web-shell injection via SQL poisoning.