Security

F5 and Confluence Attack Chain Hits Hybrid Identity

3 min read

Summary

Microsoft detailed a multi-stage intrusion where attackers compromised an internet-facing F5 BIG-IP appliance, pivoted to an internal Linux host, then exploited Confluence to steal credentials and target Active Directory. The incident highlights how edge devices, Linux systems, and SaaS apps can become linked attack paths in hybrid environments, making broader monitoring and patching essential.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published a new incident analysis showing how a compromise of an internet-facing edge appliance can quickly turn into a much broader enterprise breach. For security teams, the key lesson is clear: edge devices, Linux servers, internal web apps, and identity systems must all be treated as part of the same attack surface.

What happened

The attack chain began with an F5 BIG-IP Virtual Edition appliance hosted in Azure. Microsoft said the device was running an end-of-life version, making it a likely entry point through exploitation of a known vulnerability.

The threat actor then:

  • Used the F5 appliance to gain SSH access to an internal Linux server
  • Performed network discovery and reconnaissance with tools including Nmap and gowitness
  • Downloaded a custom Linux reconnaissance tool detected as HackTool:Linux/MalPack.B
  • Identified an unpatched Atlassian Confluence server and used it for remote code execution
  • Extracted credentials from Confluence configuration files
  • Attempted NTLM and Kerberos relay-style attacks against Active Directory, including activity tied to CVE-2025-33073

Microsoft noted that the attacker maintained privileged access without deploying formal persistence, relying instead on trusted access and over-privileged accounts.

Why this matters for defenders

This incident shows how modern attacks increasingly cross traditional boundaries:

  • Edge appliances are becoming high-value initial access points
  • Linux systems are often less monitored than Windows endpoints
  • Internal apps like Confluence can expose sensitive service credentials
  • Hybrid identity trust relationships can enable lateral movement that bypasses perimeter-focused defenses

Even when a vulnerable application is not internet-facing, attackers can still reach it after compromising another trusted system inside the environment.

Impact on IT administrators

Security and infrastructure teams should review whether they have:

  • Unsupported or end-of-life edge appliances still in production
  • Over-privileged Linux accounts with broad sudo access
  • Unpatched Confluence or other internal web applications
  • Monitoring coverage across network devices, Linux hosts, SaaS apps, and identity events

Organizations using Azure-hosted network appliances should also validate image versions used in ARM templates or Terraform deployments.

  • Patch or replace EOL F5 BIG-IP instances immediately
  • Audit and reduce privileged SSH access on Linux systems
  • Patch Confluence and review stored application credentials
  • Monitor for unusual cross-system authentication activity involving service accounts
  • Use Microsoft Defender XDR detections, advanced hunting, and attack path analysis to identify related exposure

The broader takeaway is that defenders should stop viewing edge, endpoint, SaaS, and identity security as separate problems. Attackers are already treating them as one connected path.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

F5 BIG-IPConfluenceMicrosoft Defender XDRLinux securityActive Directory

Related Posts

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.

Security

GSocket C2 Abuse: Microsoft Warns of Stealthy Persistence

Microsoft has observed multiple threat actors deploying the open source GSocket remote access tool on compromised Linux web servers to maintain access after the original vulnerability is patched. The technique relies on outbound-only encrypted connections through a shared relay network, making traditional IP or domain blocking far less effective and raising the need for host-level investigation and egress monitoring.

Security

Linux Kernel Bug Reports: 59 Findings From Microsoft

Microsoft’s FORGE Lab detailed how its MDASH project turned 26,502 Linux kernel scan findings into 59 upstream bug reports and 33 CVEs, with 38 fixes already merged. The research highlights both the promise of AI-assisted vulnerability discovery and the continued need for expert validation, patching, and coordination with upstream maintainers.

Security

AI Sleeper Agent Threat: Microsoft Shares Defenses

Microsoft Research says AI models can be backdoored by editing fewer than 10 neurons, creating sleeper agents that pass evaluations but execute attacker commands when triggered. The findings matter because autonomous agents often run with privileged access, making model weight integrity, auditing, and runtime controls critical for enterprise AI security.

Security

Rust Memory Safety Issues Found by Microsoft FORGE

Microsoft FORGE Lab disclosed several memory safety issues in Rust’s standard library, including cases where safe Rust code could still trigger undefined behavior. The research, aided by the Hyenas AI vulnerability-scanning system, highlights recurring unsafe-code design pitfalls that matter for developers and security teams relying on Rust at scale.