BRICKSTORM Malware Targets VMware vSphere: Critical Hardening Urged for Defenders

By

Breaking: BRICKSTORM Malware Compromises VMware vSphere Environments

April 10, 2025 – A sophisticated malware campaign known as BRICKSTORM is actively targeting VMware vSphere ecosystems, leveraging weak security configurations rather than software vulnerabilities to gain persistent control over virtualization layers. Researchers at Google Threat Intelligence Group (GTIG) have identified that BRICKSTORM infiltrates vCenter Server Appliance (VCSA) and ESXi hypervisors, operating beneath guest operating systems where standard endpoint detection and response (EDR) tools cannot see.

BRICKSTORM Malware Targets VMware vSphere: Critical Hardening Urged for Defenders
Source: www.mandiant.com

“This is not an exploit of a product flaw; it’s an exploitation of poor security architecture and identity management at the virtualization control plane,” said a GTIG analyst who spoke on condition of anonymity. The attack chain establishes administrative-level persistence across the entire vSphere environment, allowing threat actors to move laterally while evading traditional security monitoring.

Background

BRICKSTORM first came to light through joint research by Mandiant and GTIG, which published a detailed analysis of the malware’s ability to target VMware vSphere. The virtualization layer—encompassing VCSA and ESXi—is now seen as a critical attack vector because it lacks the host-based monitoring typical of physical servers. “Organizations have historically focused security on guest operating systems, leaving the hypervisor and its management appliance relatively unmonitored,” explains Stuart Carrera, a security researcher who contributed to the report.

The malware capitalizes on weak passwords, misconfigured identity providers, and default settings in vSphere deployments. Once inside, BRICKSTORM takes over the entire hypervisor management plane, effectively rendering all virtual machines and their data accessible to the attacker.

What This Means

For defenders, BRICKSTORM underscores the urgent need to treat the virtualization layer as a Tier-0 asset—equivalent to domain controllers or privileged access management (PAM) systems. “Compromise of the vCenter control plane gives an attacker administrative control over every managed ESXi host and every virtual machine,” Carrera warns. “Traditional tiering models become irrelevant.”

Mandiant has released a vCenter Hardening Script that automates security configurations at the Photon Linux layer of VCSA. The script enforces host-based protections, restricts administrative access, and enables logging—transforming the virtualization layer into a defensible environment. Organizations are advised to immediately audit their vSphere configurations and implement the recommended hardening measures.

BRICKSTORM Malware Targets VMware vSphere: Critical Hardening Urged for Defenders
Source: www.mandiant.com

Immediate Steps for Defenders

  • Apply the vCenter Hardening Script from Mandiant to enforce baseline security on all VCSA instances.
  • Enable two-factor authentication for all administrative access to vSphere.
  • Restrict network access to VCSA and ESXi management interfaces to authorized jump hosts only.
  • Implement audit logging for all vCenter events and monitor for anomalous behavior.

“This is a wake-up call for every organization running VMware,” Carrera adds. “Waiting for a vulnerability patch is not enough; you must harden the architecture itself.”

Technical Details

BRICKSTORM exploits the visibility gap at the virtualization layer, where standard security controls like EDR agents are not supported. The global reach of the campaign is still being assessed, but GTIG notes that targets include critical infrastructure, financial services, and government agencies. Full technical indicators of compromise (IOCs) are available in the official GTIG report.

Defenders should also review the Mandiant hardening guide for additional context. No new vulnerabilities have been disclosed in VMware products; the issue is entirely configuration-based.

Tags:

Related Articles

Recommended

Discover More

Record-Breaking Patch Tuesday: 167 Flaws Fixed, Zero-Day Under Active Attack – Microsoft, Google, Adobe Issue Urgent UpdatesBreaking: Feature Flags Eliminate Need for Costly A/B Testing Platforms, Experts SayRivian Surges Past Expectations: R2 Production Launch Drives Q1 Revenue GrowthHow to Unravel the Mysteries of Magic's Reality Fracture Set: A Step-by-Step GuideMaximize Your Rewards: A Guide to Apple Card’s $100 Co-Owner Bonus