Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MalwareUsed by 11 actorsExploits 3 CVEs

BRICKSTORM

BRICKSTORM is a backdoor/remote access trojan used in China-nexus espionage activity, most prominently linked to UNC5221 and also observed in intrusions attributed to the suspected PRC-nexus cluster UNC6201. Reporting describes it as a primary persistence implant on edge and appliance systems that often lack EDR coverage, including VMware hypervisor environments, Dell RecoverPoint for Virtual Machines appliances, Egnyte Storage Sync appliances, pfSense firewalls, and other Linux/BSD-based systems; Windows targeting has also been reported. It has been used against government and IT sector organizations, as well as legal services, software-as-a-service providers, business process outsourcers, technology firms, and U.S. law firms, with campaigns involving theft of legal, trade, national security, and intellectual property information.

Observed BRICKSTORM capabilities include interactive shell command execution, file and directory operations, and SOCKS4/5 and HTTP proxying. Operators used its proxying capability to route traffic through victim infrastructure, including SSL VPN access, and to access Microsoft 365 environments while blending with trusted internal traffic and evading Conditional Access policies. Command-and-control communications have been reported over WebSockets, TLS, and in some cases DNS-over-HTTPS for lookups; Base64 encoding of C2 communications has also been noted. Early variants were described as Golang-based, while later variants were reported as written in Rust. A FreeBSD/BSD-compatible variant was identified on pfSense firewalls.

The malware has been associated with long-term covert access, with reporting citing dwell times of more than a year and an average of 393 days in some investigations. Persistence mechanisms observed alongside BRICKSTORM deployments include modified cron files, changes to /etc/rc or /etc/rc.d/cron on pfSense, and deployment to paths such as /usr/sbin/ on compromised appliances. In Dell RecoverPoint investigations, active BRICKSTORM command-and-control traffic was observed in compromises involving CVE-2026-22769, and Mandiant reported that attackers also used BRICKSTORM as custom in-memory malware on network appliances. Publicly reported BRICKSTORM-associated infrastructure includes the domains systemsvcs.com, natsupport.net, performanceviewtools.com, winfoacacorp.com, and msazure.azdatastore.workers.dev, and reported IP indicators include 192.236.147.131, 192.236.147.138, 193.141.60.212, 192.236.154.158, 192.236.146.173, 174.169.162.62, and 64.94.84.97.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

EXPLOITED CVES

Vulnerabilities exploited

3 CVEs Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.

3 CVES
CVE-2026-22769Hardcoded Tomcat Manager Credentials in Dell RecoverPoint for Virtual MachinesExploited in the wild

Analysis of incident response engagements revealed that UNC6201, a suspected PRC-nexus threat cluster, has exploited this flaw since at least mid-2024 to move laterally, maintain persistent access, and deploy malware including SLAYSTYLE, BRICKSTORM, and a novel backdoor tracked as GRIMBOLT.

via mandiant threat intelligencecloud.google.com
CVE-2024-21887Command Injection in Ivanti Connect Secure and Policy Secure Web ComponentsExploited in the wild

BRICKSTORM, first documented last year in connection with the zero-day exploitation of Ivanti Connect Secure zero-day vulnerabilities (CVE-2023-46805 and CVE-2024-21887) against the MITRE Corporation...

via the hacker newsthehackernews.com
CVE-2023-46805Authentication Bypass in Ivanti Connect Secure and Policy Secure Web ComponentExploited in the wild

BRICKSTORM, first documented last year in connection with the zero-day exploitation of Ivanti Connect Secure zero-day vulnerabilities (CVE-2023-46805 and CVE-2024-21887) against the MITRE Corporation...

via the hacker newsthehackernews.com
THREAT ACTORS

Groups observed using it

11 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
UNC6201

Analysis of incident response engagements revealed that UNC6201, a suspected PRC-nexus threat cluster, has exploited this flaw since at least mid-2024 to move laterally, maintain persistent access, and deploy malware including SLAYSTYLE, BRICKSTORM, and a novel backdoor tracked as GRIMBOLT.

via mandiant threat intelligencecloud.google.com
UNC5221

Another high-profile campaign involves the BRICKSTORM backdoor, linked to China-nexus actor UNC5221 and observed by Google/Mandiant, which targets VMware hypervisor and Windows environments across government and IT sector organizations.

via eclecticiq blogblog.eclecticiq.com
VerdantBamboo

Tags: BRICKSTORM ... PLENET ... VerdantBamboo ...

via security online infosecurityonline.info
WARP PANDA

A China-nexus cyber espionage group has been observed deploying a BSD variant of a known backdoor called BRICKSTORM... the adversary had compromised an unnamed victim's Egnyte Storage Sync system by exploiting a local privilege escalation flaw to deploy BRICKSTORM.

via the hacker newsthehackernews.com
Clay Typhoon

A China-nexus cyber espionage group has been observed deploying a BSD variant of a known backdoor called BRICKSTORM... the adversary had compromised an unnamed victim's Egnyte Storage Sync system by exploiting a local privilege escalation flaw to deploy BRICKSTORM.

via the hacker newsthehackernews.com
PRC-Nexus

Mandiant (part of Google Cloud) just published a comprehensive defender’s guide on securing VMware vSphere environments against the BRICKSTORM backdoor and associated malware activity.

via austin larsen blogaustinlarsen.me
MITRE ATT&CK

Techniques & procedures

26 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

4 techniques
T1078Valid AccountsEvidence2

The threat actor used the malware's proxying capabilities deployed on the Storage Sync system, along with compromised credentials, to access the victim's Microsoft 365 (M365) environment.

T1133External Remote ServicesEvidence1

The attacker’s workstation, sitting somewhere outside the victim’s network, connected to the organization’s web-based SSL VPN.

T1190Exploit Public-Facing ApplicationEvidence5

Mandiant and Google Threat Intelligence Group (GTIG) have identified the zero-day exploitation of a high-risk vulnerability in Dell RecoverPoint for Virtual Machines, tracked as CVE-2026-22769... UNC6201... has exploited this flaw since at least mid-2024

T1195Supply Chain CompromiseEvidence1

The MSP’s pfSense firewall had a FreeBSD variant of BRICKSTORM running on it... The working theory... is that the actors gained a foothold at the MSP, used that position to harvest administrative credentials for client environments

Execution

2 techniques
T1053.003CronEvidence2

The same malware was found on the MSP’s pfSense firewall in a FreeBSD-compatible variant, obfuscated with a tool called gobfuscate and set to run automatically through a modified cron startup file.

T1059.004Unix ShellEvidence2

Handles file and directory operations Runs arbitrary interactive shell commands

Persistence

7 techniques
T1037Boot or Logon Initialization ScriptsEvidence2

UNC6201 established BRICKSTORM and GRIMBOLT persistence on the Dell RecoverPoint for Virtual Machines by modifying a legitimate shell script named convert_hosts.sh to include the path to the backdoor. This shell script is executed by the appliance at boot time via rc.local.

T1053.003CronEvidence2

The same malware was found on the MSP’s pfSense firewall in a FreeBSD-compatible variant, obfuscated with a tool called gobfuscate and set to run automatically through a modified cron startup file.

T1078Valid AccountsEvidence2

The threat actor used the malware's proxying capabilities deployed on the Storage Sync system, along with compromised credentials, to access the victim's Microsoft 365 (M365) environment.

T1133External Remote ServicesEvidence1

The attacker’s workstation, sitting somewhere outside the victim’s network, connected to the organization’s web-based SSL VPN.

T1543Create or Modify System ProcessEvidence1

Volexity found that VerdantBamboo had set up persistence for the BRICKSTORM implant by modifying the file /etc/rc.d/cron to include a single line to execute the implant.

T1543.002Systemd ServiceEvidence1

Once you have that, you can write to /usr/sbin/ , install a service, modify /etc/rc for persistence

T1556Modify Authentication ProcessEvidence1

To Microsoft’s authentication infrastructure, the logins looked like they were coming from inside the building.

Privilege Escalation

7 techniques
T1037Boot or Logon Initialization ScriptsEvidence2

UNC6201 established BRICKSTORM and GRIMBOLT persistence on the Dell RecoverPoint for Virtual Machines by modifying a legitimate shell script named convert_hosts.sh to include the path to the backdoor. This shell script is executed by the appliance at boot time via rc.local.

T1053.003CronEvidence2

The same malware was found on the MSP’s pfSense firewall in a FreeBSD-compatible variant, obfuscated with a tool called gobfuscate and set to run automatically through a modified cron startup file.

T1068Exploitation for Privilege EscalationEvidence3

the adversary had compromised an unnamed victim's Egnyte Storage Sync system by exploiting a local privilege escalation flaw to deploy BRICKSTORM

T1078Valid AccountsEvidence2

The threat actor used the malware's proxying capabilities deployed on the Storage Sync system, along with compromised credentials, to access the victim's Microsoft 365 (M365) environment.

T1543Create or Modify System ProcessEvidence1

Volexity found that VerdantBamboo had set up persistence for the BRICKSTORM implant by modifying the file /etc/rc.d/cron to include a single line to execute the implant.

T1543.002Systemd ServiceEvidence1

Once you have that, you can write to /usr/sbin/ , install a service, modify /etc/rc for persistence

T1548.003Sudo and Sudo CachingEvidence2

exploiting a misconfigured sudo rule to gain elevated privileges.

Stealth

4 techniques
T1027Obfuscated Files or InformationEvidence2

The same malware was found on the MSP’s pfSense firewall in a FreeBSD-compatible variant, obfuscated with a tool called gobfuscate

T1070.004File DeletionEvidence1

After this operation was successful, the threat actor removed the file from /etc/cron.d, meaning there was no long-term persistence method for this implant.

T1078Valid AccountsEvidence2

The threat actor used the malware's proxying capabilities deployed on the Storage Sync system, along with compromised credentials, to access the victim's Microsoft 365 (M365) environment.

T1140Deobfuscate/Decode Files or InformationEvidence1

Mandiant also released a tool for decoding Garble strings[2]... After retrieving all the matches and removing possible substrings I can emulate the code... This won’t get every single string as some are passed as offsets to the data residing in rodata section for longer pieces.

Defense Impairment

1 technique
T1556Modify Authentication ProcessEvidence1

To Microsoft’s authentication infrastructure, the logins looked like they were coming from inside the building.

Credential Access

1 technique
T1556Modify Authentication ProcessEvidence1

To Microsoft’s authentication infrastructure, the logins looked like they were coming from inside the building.

Lateral Movement

1 technique
T1021.004SSHEvidence2

The two malware families deployed to the NAS appliance over SSH are as follows

Collection

1 technique
T1005Data from Local SystemEvidence1

The attackers exploited zero-day vulnerabilities, deployed the BRICKSTORM backdoor, and maintained access for over a year to steal sensitive legal, trade, and national security information.

Command and Control

9 techniques
T1071Application Layer ProtocolEvidence2

Instead of connecting to Egnyte’s own infrastructure, it was quietly beaconing out to a domain controlled by the attackers, hiding behind Cloudflare IP addresses and using Google’s public DNS server at 8.8.8.8 to resolve queries over HTTPS, a technique that neatly disguised the malicious traffic. | The device was an Egnyte Storage Sync appliance... quietly beaconing out to a domain controlled by the attackers, hiding behind Cloudflare IP addresses and using Google’s public DNS server at 8.8.8.8 to resolve queries over HTTPS.

T1071.001Web ProtocolsEvidence3

Communicates with its C2 infrastructure over WebSockets, with some variants using DNS-over-HTTPS (DoH) to obscure C2 lookups from standard DNS monitoring

T1071.004DNSEvidence2

some variants using DNS-over-HTTPS (DoH) to obscure C2 lookups from standard DNS monitoring

T1090ProxyEvidence4

The threat actor used the malware's proxying capabilities deployed on the Storage Sync system, along with compromised credentials, to access the victim's Microsoft 365 (M365) environment.

T1090.001Internal ProxyEvidence1

They contain three core task extensions: ... socks A Socks5 proxy server implementation

T1105Ingress Tool TransferEvidence4

deploy additional malware to a Synology Network Attached Storage (NAS) appliance

T1219Remote Access ToolsEvidence2

GRIMBOLT... provides a remote shell capability and uses the same command and control as previously deployed BRICKSTORM payload.

T1568Dynamic ResolutionEvidence1

It appeared to be using Google to perform queries via DNS over HTTPS, as there was no DNS activity for the domain observed in the connections.

T1573Encrypted ChannelEvidence1

The appliance was also making TLS connections to one of Google’s public DNS servers (8.8.8.8). It appeared to be using Google to perform queries via DNS over HTTPS

INDICATORS OF COMPROMISE

IOCs tracked for this family

42 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
29 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
12 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

Other
1 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
ip.v4●●●●●●●●●●●●View more in app11 days ago
ip.v4●●●●●●●●●●●●View more in app11 days ago
ip.v4●●●●●●●●●●●●View more in app11 days ago
ip.v4●●●●●●●●●●●●View more in app11 days ago
ip.v4●●●●●●●●●●●●View more in app11 days ago
ip.v4●●●●●●●●●●●●View more in app11 days ago
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching42

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution11

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities3

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping26

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.