Executive SummaryRisk level: High
What happened

Between January 11 and February 18, 2026, an AI-assisted threat actor compromised 600+ FortiGate devices across 55 countries, using generative AI to accelerate reconnaissance and exploitation of unpatched/exposed devices.

Who is affected

Organizations operating internet-exposed FortiGate devices, globally.

Why it matters

AI compresses recon-to-exploit timelines and scales attacks, enabling rapid compromise, persistence, and follow-on ransom demands.

Immediate recommended actions

  • Patch FortiGate firmware and reduce internet exposure of management.
  • Hunt for post-compromise PowerShell and persistence on/around devices.
  • Monitor firewall/EDR for exploit signatures and anomalous logons.
  • Rotate device credentials and enforce MFA for admin access.
How to read this report. Items are labelled by confidence: Confirmed stated as fact in the source, Reported described by the source, Potential analyst inference, and Requires Validation to be confirmed in your environment. Where the source lacks detail this is stated as “Not specified in the source material”.

Key Technical Findings

Vulnerability / Campaign Type

AI-assisted mass exploitation of FortiGate devices.

Affected Systems

600+ FortiGate devices across 55 countries.

Initial Access Vector

Exploitation of vulnerabilities in public-facing FortiGate devices (T1190).

Execution Method

Malicious payloads executed, including via PowerShell (T1086).

Persistence

Mechanisms established to survive device reboots.

Privilege Escalation

Attempts to elevate privileges to access sensitive configs.

Defense Evasion

Avoidance of signature-based detection.

Credential Access

Credentials harvested from compromised devices.

Lateral Movement

Movement across the network to additional devices.

Data Exfiltration

Data collected for exfiltration or ransom.

Impact Level

High – mass device compromise with ransom demands.

Technical Background

The actor used generative AI to automate reconnaissance, rapidly identifying vulnerable FortiGate devices and targeting known weaknesses (T1190). Post-access, payloads were executed (including PowerShell, T1086), persistence established, privileges escalated, and credentials harvested for lateral movement, culminating in ransom demands.

The novelty is speed and scale rather than a new exploit. Defenses remain firmware patching, exposure reduction, MFA, and behavioral detection of post-compromise activity.

Attack Chain Analysis

  1. Initial Access

    ActivityAI-assisted exploitation of vulnerable FortiGate devices (T1190).

    EvidenceExploit signatures in device/firewall logs.

    TelemetryFirewall/device logs.

    Detection opportunityMonitor for exploit attempts against FortiGate.

  2. Execution

    ActivityRun payloads, including PowerShell (T1086).

    EvidenceEncoded command lines.

    TelemetrySysmon EID 1, PowerShell 4104.

    Detection opportunityAlert on -enc/-nop PowerShell.

  3. Persistence

    ActivityEstablish reboot-surviving access.

    EvidenceNew persistence artifacts.

    TelemetrySecurity 7045/4698, device configs.

    Detection opportunityHunt for new persistence.

  4. Credential Access

    ActivityHarvest device credentials.

    EvidenceAccess to config/credential stores.

    TelemetryDevice logs, EDR.

    Detection opportunityDetect credential extraction.

  5. Impact

    ActivityIssue ransom demands.

    EvidenceRansom notes/communications.

    TelemetryIncident reports.

    Detection opportunityCorrelate compromise with extortion.

Deep Technical Behavior Analysis

The defining behavior is AI-accelerated targeting that turns broad scanning into rapid, precise exploitation of exposed devices. Because edge devices lack endpoint EDR, device/firewall logs and detection of post-compromise host activity (PowerShell, persistence) are the primary surfaces.

Specific exploited CVEs and indicators are not specified in the source material and require validation.

Indicators of Compromise

No indicators of compromise were provided in the source material.

Indicators of Behavior

Behavioral indicators to hunt for even when atomic IoCs are limited (Potential — validate against your baseline).

Behavioral Indicator Description Data Source Confidence
Anomalous PowerShell execution Encoded/obfuscated commands, download cradles, or unusual parent-child process lineage. Sysmon EID 1, PowerShell 4104 Potential
Suspicious child process lineage Office or web/service processes spawning script hosts or shells. Sysmon EID 1, EDR Potential
Security log clearing Event log cleared or audit policy changed to hinder visibility. Windows Security 1102, 4719 Potential
New service / scheduled task creation Unexpected persistence via services or tasks. Security 7045, 4698; Sysmon Potential
New SSH authorized_keys / cron entries Unexpected persistence on Linux hosts. auditd, /var/log/secure, cron logs Potential
Shell history gaps or clearing History truncated or redirected to /dev/null. auditd, bash history Potential
Web shell-like activity New/modified server-side scripts in writable web paths; anomalous POSTs. Web access/error logs, FIM Potential
Abnormal 403/404/500 patterns Enumeration or exploitation attempts against endpoints. Web server logs, WAF Potential
Beaconing to rare destinations Periodic outbound connections to newly-seen domains/IPs or direct-IP C2. Proxy, firewall, DNS logs Potential
Unusual DNS queries High-entropy or rare domains; possible tunneling. DNS resolver logs Potential
Authentication anomalies Spraying/stuffing, impossible travel, or MFA fatigue patterns. IdP/VPN logs, Azure AD/Okta sign-ins Potential

Detection Engineering Guidance

Defensive detection logic (Potential — tune to your environment). No exploit code is included; logic is for hunting and alerting only.

T1190 — Exploit Public-Facing Application
  • ObjectiveDetect exploitation of public-facing apps
  • Suspicious patternWeb/WAF anomalies + new files
  • Data sourceWeb access/error, WAF, FIM
  • False positivesAdmin tooling/automation; baseline before alerting.
  • ResponseTriage host, validate scope, preserve evidence, contain if confirmed.
pseudo: spike in 4xx/5xx to a single endpoint
  followed by new/modified server-side script in web root => alert(level=high)
Platform Log Source What to Look For Priority
Windows Security Event Log Logon (4624/4625), service (7045), task (4698), log clear (1102) High
Windows Sysmon Process creation (1), network (3), image load (7), LSASS access (10) High
Windows PowerShell Operational Script block logging (4104), module logging High
Endpoint EDR / Defender telemetry Process tree, persistence, tamper attempts High
Web Web server access logs Anomalous POSTs, new endpoints, web-shell-like requests High
Web Web server error logs Repeated 403/404/500 bursts on single endpoints Medium
Linux auth.log / secure SSH logins, sudo, account changes High
Linux auditd execve, file writes, persistence paths High
Identity IdP / VPN logs Impossible travel, spraying, MFA fatigue High
Network DNS resolver logs Rare/high-entropy domains, tunneling Medium
Network Proxy / firewall logs Beaconing, direct-IP C2, exfil volume High

MITRE ATT&CK Mapping

Tactic Technique ID Technique Name Relevance Detection Opportunity Confidence
Initial Access T1190 Exploit Public-Facing Application Exploitation of vulnerabilities in FortiGate devices to gain unauthorized access. Monitoring for exploit signatures in logs. Reported
Execution T1086 PowerShell Utilization of PowerShell scripts for executing malicious payloads post-compromise. Sysmon Event ID 1; flag -enc / -nop flags. Reported

Incident Response Guidance

  • Validate exposure and confirm whether the issue applies to your environment.
  • Preserve evidence (memory, disk, relevant logs) before remediation.
  • Isolate affected hosts/accounts if compromise is suspected.
  • Collect volatile data and review the log sources listed above.
  • Hunt for the indicators of behavior and any related atomic indicators.
  • Rotate potentially exposed credentials, keys, and session tokens.
  • Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
  • Patch affected systems; reimage where integrity cannot be assured.
  • Run post-remediation validation and a BAS/security-validation retest.

Remediation and Hardening

  • Patch affected systems and reduce internet-exposed services.
  • Enforce MFA and least-privilege for privileged and remote access.
  • Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
  • Restrict script execution and constrain LOLBins where feasible.
  • Monitor persistence locations and disable unnecessary services.
  • Segment critical assets and review privileged accounts.
  • Rotate secrets and remove credentials from configuration files.
  • Tune SIEM/EDR detections, then validate controls after changes.

Business Risk

  • Service disruption: degraded or unavailable systems during compromise or recovery.
  • Data exposure: risk to sensitive, regulated, or customer data depending on scope.
  • Regulatory exposure: potential breach-notification and compliance obligations.
  • Financial impact: incident response, downtime, and potential extortion costs.
  • Brand and trust impact: reputational damage with customers and partners.
  • Operational continuity: ransomware can halt critical business processes until restored.
  • Identity blast radius: compromised accounts can expand access across cloud and SaaS.

Executive Takeaway

What leadership needs to know: AI compresses recon-to-exploit timelines and scales attacks, enabling rapid compromise, persistence, and follow-on ransom demands. Current assessed risk: High.

Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.

Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.

Validating Your Defenses with Valitrix

The Valitrix Breach and Attack Simulation (BAS) platform provides organizations with the capability to continuously validate their security controls against real-world adversary techniques. By emulating specific tactics from the MITRE ATT&CK framework, such as those demonstrated in the AI-powered FortiGate breach, organizations can ascertain the effectiveness of their detection and prevention mechanisms without exposing their environments to actual threats.

This proactive approach allows SOC teams to refine their incident response strategies and enhance their overall security posture. By simulating these advanced techniques, Valitrix enables organizations to identify gaps in their defenses and implement necessary improvements before a real incident occurs.

Key Takeaways

  • The recent AI-powered breach affecting FortiGate devices highlights the increasing sophistication of cyberattacks.
  • Over 600 devices were compromised across 55 countries, emphasizing the need for global vigilance.
  • Organizations must adapt their defenses to counter AI-assisted threats effectively.
  • Regular updates and continuous monitoring are essential for mitigating risks associated with known vulnerabilities.

Frequently Asked Questions

What are FortiGate devices?

FortiGate devices are security appliances that provide firewall and VPN capabilities, primarily used by enterprises to protect their networks from cyber threats.

How can organizations detect AI-assisted attacks?

Organizations can detect AI-assisted attacks by monitoring network traffic for anomalies, implementing advanced threat detection systems, and using AI-driven analytics to identify unusual behavior patterns.

What should I do if my FortiGate device is compromised?

If a FortiGate device is compromised, it is critical to isolate the device from the network, conduct a thorough investigation, and apply the latest security patches to prevent further exploitation.