TP-2026-0061 high AI Draft B

Multi-Stage Linux Intrusion Pivoted from F5 BIG-IP to Confluence

Date May 22, 2026
Attack Type Intrusion Sector Technology
Geography Unknown
Threat Actor Unknown
Attribution A4
Confidence B

Summary

Microsoft reported a multi-stage intrusion that began with an exposed F5 BIG-IP edge appliance and later pivoted into internal Linux and identity infrastructure. The reported intrusion path included access to an internal Confluence server, credential theft, and follow-on attempts to abuse authentication flows for broader access.

The report describes both Linux-host activity and domain-focused follow-on activity. The threat actor was not publicly named in the cited sources.

Technical Analysis

According to Microsoft, the actor gained an initial foothold through a compromised edge path associated with F5 BIG-IP and then used SSH and shell execution across Linux systems. The actor conducted discovery, transferred tools, and moved laterally to an internal Confluence server.

Microsoft described credential theft, subsequent exploitation of CVE-2025-33073, and attempted Kerberos/NTLM relay behavior against domain infrastructure.

CISA KEV data and NVD reference data for CVE-2025-33073 provide supporting vulnerability context aligned to the incident-evidenced CVE.

Attack Chain

Stage 1: Edge Foothold

Initial access was established through the edge environment associated with F5 BIG-IP.

Stage 2: Linux Execution and Discovery

The actor used SSH, shell commands, and tooling on Linux hosts to enumerate files and reachable services.

Stage 3: Internal Pivot to Confluence

The actor moved laterally to an internal Confluence server and performed further execution and credential access activity.

Stage 4: Authentication Abuse Attempts

After obtaining credentials, the actor attempted relay-style authentication abuse against domain services.

Impact Assessment

The reported activity shows risk of escalation from perimeter compromise to enterprise identity compromise. Observed behaviors included host execution, tool transfer, internal pivoting, and attempted credential abuse against domain infrastructure.

Public sources do not provide a confirmed victim count for this event.

Attribution

The threat actor remains unknown for this incident. Available documentation provides behavioral and infrastructure details, but no government-confirmed named actor attribution was identified.

Timeline

2026-05-22 — Microsoft intrusion case published

Microsoft published the multi-stage Linux intrusion case describing compromise flow from edge appliance to internal systems and identity-focused follow-on activity.

Remediation & Mitigation

Prioritize patching and mitigation for internet-facing edge systems and internal critical applications, including F5 BIG-IP and Confluence instances noted in the cited material. Restrict management-plane exposure and limit reachable admin surfaces.

For identity-layer hardening, apply controls that reduce relay abuse paths, including stronger authentication channel protections and restrictions on legacy authentication paths where operationally feasible. Ensure consistent endpoint telemetry and prevention coverage across Linux servers and investigate signs of compromise before returning affected systems to production trust.

Sources & References