Threat actor profile · suspected PRC-nexus espionage
ARMORY CASTLE (UNC5221)
Google renamed UNC5221 ARMORY CASTLE [1]; the DOJ announcement about Yin and Zhou uses “UNC 5221” alongside APT27, but the evidence leaves open whether those names describe the same operational group [11]. The public sources reviewed do not identify who directed the 2026 BeyondTrust and vCenter intrusions [1][23].
Source review: 20 November 2026
How to read the edge types
Each edge encodes what kind of claim links the name to the cluster. A vendor merge, a published cross-reference and a government alias list are different kinds of evidence, and the diagram keeps them visibly distinct.
same cluster one vendor renamed or merged its own trackingvendor cross-map another vendor's name mapped onto UNC5221 by a third party or the vendors themselvesDOJ naming overlap DOJ groups the names; a match between operational groups is not established
Intersection map
Select a labeled alias or campaign to jump to its evidence. The full evidence tables are also available below.
Left: public names and the basis for linking them to the Google/Mandiant cluster. Right: campaigns and related advisories, including a case CrowdStrike attributes to WARP PANDA and a separate vCenter flaw shown as patch context. Inclusion does not attribute every item to ARMORY CASTLE.
Aliases
Name
Who uses it
Relationship to Armory Castle / UNC5221
Tier
Sources
Armory Castle
Google Threat Intelligence Group / Mandiant
Current name. First used publicly in the 15 Oct 2026 BeyondTrust post; Google writes "formerly tracked as UNC5221".
Cluster that Mandiant had tied to the SPAWN malware ecosystem. Google's 8 Jan 2025 Ivanti post now reads "Since the publication of this blog post, Mandiant has merged UNC5337 into UNC5221"; no merge date is given, and the post's changelog shows "Attribution updated to UNC5221" on 17 Jan 2025.
Strongest evidence: Volexity itself writes "VerdantBamboo (WARP PANDA, UNC5221)" in its 4 Jun 2026 BRICKSTORM investigation, a first-party vendor cross-reference. SecurityWeek (twice, citing Mandiant/GTIG) writes "also tracked as UNC5221 and Warp Panda". ExtraHop (20 Feb 2026) says UNC5221 and WARP PANDA share tools but "it is not yet confirmed if they represent the same operational entity", and attributes BRICKSTORM to both. The cross-reference is published; the scope of each vendor's cluster remains unclear. Neither source quotes CrowdStrike directly. Malpedia's UTA0178/UNC5221 entry does not list WARP PANDA as an alias; it cites CrowdStrike only under the separate BRICKSTORM malware entry. Google's own BeyondTrust and vSphere posts do not use the name. CrowdStrike's one attribution in this set, the ESX logging flaw CVE-2026-41709, is to WARP PANDA; only The Hacker News equates that with Armory Castle.
Malpedia's actor entry is titled UTA0178 with "aka: ARMORY CASTLE, Red Dev 61, UNC5221" and cites Volexity's 2024 Ivanti Connect Secure report; ExtraHop lists it as an alias; the U.S. government lists it beside UNC5221 in the APT27 alias set.
Volexity's own 4 Jun 2026 report writes "a Chinese threat actor, which Volexity tracks as VerdantBamboo (WARP PANDA, UNC5221)", a first-party vendor cross-reference. The Hacker News adds Clay Typhoon (Microsoft) to the overlap list, but that name is not in Volexity's post and is not confirmed here. Open question: Volexity also coined UTA0178, and its VerdantBamboo post does not say whether the two are one cluster; Malpedia files VerdantBamboo-era activity under its UTA0178 entry.
Cloudflare’s public threat report overview names PunyToad [50]. A secondary account reports that Cloudforce One cross-referenced UNC5221, UTA0178 and WARP PANDA [51]. The primary source for that exact mapping was not verified. See the F5 incident for the separate campaign assessment.
Listed by ExtraHop and by Malpedia as an alias of UNC5221; neither says whose name it is. Two listings establish that the cross-reference is public, not that the vendor draws the same cluster boundary.
DOJ and State Department list "Silk Typhoon" with "UNC 5221" and "UTA0178" as names for APT27. Mandiant told The Hacker News its cluster "likely overlaps" with Silk Typhoon and APT27 but it has no independent evidence. GTIG's own September 2025 report: "While UNC5221 has been used synonymously with the actor publicly reported as Silk Typhoon, GTIG does not currently consider the two clusters to be the same."
APT27Emissary Panda · Threat Group 3390 · Bronze Union · Lucky Mouse · Iron Tiger · Budworm
Mandiant (APT27); CrowdStrike (Emissary Panda); Secureworks (Bronze Union); Dell SecureWorks (TG-3390); Kaspersky (Lucky Mouse); Trend Micro (Iron Tiger); Symantec (Budworm). Vendor-to-name mapping from general knowledge, not from today's sources.
The DOJ announcement groups APT27 with “UNC 5221,” Silk Typhoon and UTA0178 [11]. Paragraph 24 of the FBI affidavit uses “UNC5221” and does not explain how each vendor label was matched to Yin’s activity [14]. Whether APT27 and UNC5221 describe the same operational group remains unresolved.
Naming overlap is not operational equivalence. DOJ groups the names in its announcement about Yin and Zhou [11]. GTIG explicitly distinguishes UNC5221 from Silk Typhoon [27]. Whether APT27 and UNC5221 describe the same operational group remains unresolved.
Tools
Groups share tools, so a tool is not proof of attribution. BRICKSTORM and GRIMBOLT turn up under several cluster names, and Google’s own BRICKSTORM attribution covers “UNC5221 and closely related” clusters [27]. In the 2026 campaigns Google says the tooling “align[s] with previously observed activity” and cites one direct overlap, LAZYBONES [1]. BeyondTrust said the actor “rotates its infrastructure and tooling for every victim, so attribution here rests on behavior” [53]. Tools that are open source or built on public code show technique, not identity. On the map, a dashed chip marks a tool that a source also attributes to another cluster.
ZIPLINE · THINSPOOL · LIGHTWIRE · WARPWIRE
Passive backdoor, dropper, web shell and credential harvester, per Google’s one-line labels.
Where seen
Ivanti Connect Secure, Dec 2023–Jan 2024 (CVE-2023-46805 / CVE-2024-21887).
Attribution and other users
Google lists them as UNC5221’s in the earlier campaign; no further detail in this set.
Ivanti implant set: SPAWNANT installer (survives upgrades), SPAWNMOLE tunneler in the web process, SPAWNSNAIL SSH backdoor, SPAWNSLOTH log tampering.
Where seen
Ivanti CVE-2025-0282 (Jan 2025); the “SPAWN ecosystem” again after CVE-2025-22457 (Apr 2025), adding SPAWNSNARE (kernel-image extraction) and SPAWNWAVE (evolved SPAWNANT).
Attribution and other users
Originally attributed to UNC5337, which Mandiant later merged into UNC5221. Google says SPAWNWAVE overlaps with SPAWNCHIMERA and RESURGE, families reported by JPCERT and CISA and not attributed to UNC5221 there.
Go backdoor that takes commands from a Slack channel over HTTPS; command execution and file transfer. Installed as /usr/bin/vmtoolscs with a systemd service restarting every 50 minutes.
Where seen
vCenter campaign, Sept 2026. Google says it saw LAZYBONES in “a separate campaign in early 2025 following the successful exploitation of CVE-2025-22457”.
Attribution and other users
Google’s April 2025 report on that CVE does not name LAZYBONES; the early-2025 link rests on the Nov 2026 post. Google calls it a direct overlap with earlier ARMORY CASTLE activity.
Go backdoor with SOCKS proxying (later Rust variants and a FreeBSD build per Volexity); Linux and BSD appliances; C2 via Cloudflare Workers, Heroku, sslip.io/nip.io and DoH.
Where seen
2024–25 U.S. legal, SaaS and tech intrusions (393-day average dwell); Egnyte, pfSense and GroupWise hosts investigated from Sept 2025 and reported in Jun 2026.
Attribution and other users
Google attributes it to “UNC5221 and closely related, suspected China-nexus threat clusters”. Google also attributes BRICKSTORM use to UNC6201, a separate cluster with “notable overlaps” with UNC5221. ExtraHop attributes it to UNC5221 and WARP PANDA; Volexity to VerdantBamboo.
Linux backdoor in .NET/C#, compiled with Native AOT and UPX-packed: interactive shell, command execution, file operations, C2 switching.
Where seen
Volexity: deployed by VerdantBamboo on a Synology NAS (file ovs-dbctl).
Attribution and other users
Volexity says the malware “was referred to as ‘GRIMBOLT’ by Google Cloud”. Google attributes GRIMBOLT to UNC6201, which replaced BRICKSTORM with it in Sept 2025. Google has not attributed GRIMBOLT to ARMORY CASTLE.
Obfuscated PHP web shell (mangoapi.php) with Base32 transport and RC4; returns 404 unless the expected POST parameter is present.
Where seen
BeyondTrust Remote Support, from 29 Aug 2026; created about 11 minutes after the first POST to a staging web shell. A primary foothold for the rest of the intrusion.
C tunneler (/tmp/ingredi_ws) offering SOCKS5 over WebSocket on TCP 19800, built with CivetWeb and OpenSSL. HAProxy was edited to route /uidchanarge to it, hiding the listener from external scans.
Go exploitation utility for CVE-2026-123890 against vCenter 7.x/8.x: exfiltrates the LMDB, hijacks the SAML Security Token Service and creates an SSO administrator (csa subcommand). Internally named vcenter-db-teamcheck-go; build timestamp 13 Jul 2026, which Google notes can be altered.
Where seen
vCenter campaign, early Sept 2026.
Attribution and other users
Google says the build date indicates it “was likely developed for broader operations”. Whether only this cluster holds it is unknown.
Go Golden SAML utility: extracts IdP signing keys from vCenter’s data.mdb, forges SAML assertions for Administrator, returns session cookies. A Go port of Horizon3’s public vcenter_saml_login.py.
Where seen
vCenter campaign; deleted with rm afterwards.
Attribution and other users
Built on a public tool, so its techniques are available to anyone.
nmap (ports 9080, 5480, 2012 and others), gdb (to set SUID on /bin/env), WinSCP, scp/ssh, PySoxy and BusyBox (Ivanti intrusions), and BeyondTrust’s own bt-secrets CLI to dump the vault.
Where seen
Across campaigns.
Attribution and other users
Available to anyone; they show method, not identity.
Ivanti Connect Secure CVE-2023-46805 and CVE-2024-21887
Google: UNC5221 "previously exploited" these "as early as December 2023"; after the 10 Jan 2024 disclosure Mandiant observed widespread exploitation by UNC5221.
Attributed to UNC5221; SPAWN family deployed. In its report on this CVE, Mandiant also describes DRYHOOK as a credential stealer; that description alone does not attribute its use to UNC5221. UNC5337 was merged into UNC5221 after the post was published (changelog entry 17 Jan 2025; no merge date given).
Google’s April 2025 report attributes the exploitation and the SPAWN ecosystem to UNC5221 and also describes TRAILBLAZE and BRUSHFIRE [46]. It does not mention LAZYBONES; Google’s Nov 2026 vSphere post later says LAZYBONES was deployed after this CVE was exploited [1]. Disclosed by Ivanti 3 Apr 2025.
Mandiant reported a 393-day average dwell time and separately observed the actor clone Windows Server VMs in at least two cases. This does not establish that credentials collected by BRICKSTEAL were used for those cloning events.
Google ("UNC5221 and closely related, suspected China-nexus clusters"); ExtraHop ("researchers", UNC5221 and WARP PANDA)
F5 confirmed theft of some BIG-IP source code and information about undisclosed vulnerabilities. DCISE reports that researchers found BRICKSTORM on F5 systems but gives limited detail supporting its attribution.
F5 described an unnamed nation-state actor [48]. DCISE listed UNC5221 as suspected [49]. A secondary account attributes the incident to Cloudflare’s PunyToad cluster; a primary Cloudflare attribution was not verified [51].
Investigated September 2025; reported June 4, 2026
Egnyte Storage Sync local privilege escalation (fixed in 13.13, Mar 2026), then Microsoft 365 via proxying and stolen credentials; return after remediation via stolen firewall admin credentials and SSL VPN; malware on a Synology NAS and on the MSP's pfSense firewall
Volexity tracks the actor as VerdantBamboo (WARP PANDA, UNC5221); BRICKSTORM BSD/Rust variants, PLENET/GRIMBOLT, AGENTPSD; initial compromise at least 18 months before discovery.
BeyondTrust Remote Support CVE-2026-102764 (zero-day; BeyondTrust CVSS v4.0 9.3 [44]; Ghostwire stores 9.8, with no verified source or version)
Google: exploited "as a zero-day, in late August 2026"; SecurityWeek: first confirmed exploitation 29 Aug against one BeyondTrust-hosted and one self-hosted appliance, flaw identified by BeyondTrust 28 Sept. Patch applied to all SaaS tenants 9 Oct; disclosed 15 Oct. SAWFLY and BARECLAW. Google's exact wording on tactics: in past campaigns the group "conducted widespread and opportunistic exploitation following the public disclosure of vulnerabilities it had exploited selectively as zero-days", and it is possible the same will follow for this CVE; this describes past behaviour, not a declared shift. The BSI advisory number 2026-297832 still rests on a secondary source only.
Reached from the BeyondTrust appliance; BONESAW, SAWSNAKE, BEARBONES, web shells; stole vCenter encryption key and DB credentials; read AD, registry and DNS data out of a Windows virtual disk on ESXi; exfiltrated via the BeyondTrust box. Patched 19 Nov.
VMware ESX CVE-2026-41709 (CVSS 2.7; Broadcom: lets a malicious administrator perform certain operations without them being logged)
Abused to reduce audit-trail visibility. CrowdStrike's attribution, in its 2026 legal-sector threat report, is to WARP PANDA, "a China-nexus group it tracks"; it does not say how the group got in or name malware. Only The Hacker News folds this into Armory Castle's record. Shown on the map as a cross-map edge for that reason.
CrowdStrike (WARP PANDA); equated with Armory Castle by The Hacker News
APT27 is the name the U.S. government chose when it indicted two Chinese contractors in 2025, and it is the only name on this page that a government has tied to specific people. Google’s July 2026 naming system now calls its APT27 cluster SHORE CASTLE, alongside ARMORY CASTLE for UNC5221; both names sit in Google’s “CASTLE” family for PRC actors but are tracked as separate clusters [54]. It is also the oldest cluster here: vendors have tracked the activity since around 2009–2010 under a dozen names. DOJ groups the names in its announcement about Yin and Zhou [11]. GTIG explicitly distinguishes UNC5221 from Silk Typhoon [27]. Whether APT27 and UNC5221 describe the same operational group remains unresolved.
Names and who coined them
Name
Vendor
Notes
Sources
APT27
Mandiant
The name the DOJ, FBI and State Department use for the Yin Kecheng / Zhou Shuai cases.
The 2025 charges and the FBI’s naming cross-reference
On 5 March 2025 the DOJ unsealed two D.C. indictments against Yin Kecheng ("YKC", 38) and Zhou Shuai ("Coldface", 45), both fugitives. The 2018 indictment covers Yin's conduct from August 2013 to December 2015; the 2023 indictment covers both men from June 2018 to November 2020. Charges include conspiracy, wire fraud, Computer Fraud and Abuse Act violations, aggravated identity theft and money laundering [16]. Prosecutors describe them as for-profit contractors and data brokers rather than officials: Yin stole data, Zhou brokered it through Chinese data brokers including i-Soon, whose main customers were the MSS and MPS [16][17]. Treasury sanctioned Yin on 17 January 2025 for the September–December 2024 breach of the U.S. Treasury Department, which ran through VPS infrastructure on an account he and co-conspirators set up, and its release states that he "is affiliated with the People's Republic of China Ministry of State Security (MSS)", with no bureau, unit or chain of command given [30]. On 5 March 2025 Treasury sanctioned Zhou, "a Shanghai-based malicious cyber actor and data broker", and Shanghai Heiying, "a Shanghai-based cybersecurity company that has employed numerous known China-backed malicious cyber actors, including Yin Kecheng", noting Zhou worked from intelligence requirements covering the U.S., Russia and Western Europe (telecommunications, border-crossing and religious-research personnel data) that Treasury attributes to "the CCP's intelligence services" [31][16][17]. Neither Treasury release uses the names APT27, UNC5221 or Silk Typhoon; those appear only in the DOJ and State Department documents. State offered up to $2 million for each man [12][16]. Victims named in the release include cleared defense contractors, think tanks, law firms, universities, municipalities, health-care systems, communication providers, a large U.S. religious organization, foreign ministries of several Asian governments, and U.S. federal and state agencies as late as 2024 [16]. DOJ groups APT27, Silk Typhoon, “UNC 5221” and UTA0178 in its announcement [11]. The FBI affidavit’s paragraph 24 spells the label “UNC5221” [14]. That naming overlap does not establish operational equivalence.
Why that alias list is weaker than it looks. The charging documents rest on specific individuals: the joint indictment alleges a conspiracy from June 2018 to November 2020 [16], and the FBI search-warrant affidavit, a separate document, ties Yin to hosting accounts used in the Treasury intrusion and to earlier intrusions through infrastructure overlaps from October 2021 to February 2022 [14]. Neither explains how Yin and Zhou connect to the 2024 Ivanti or 2026 appliance campaigns that define UNC5221. Natto Thoughts points out that the DOJ used "APT27" here and "HAFNIUM" for the July 2025 Xu Zewei / Zhang Yu indictment even though Microsoft retired HAFNIUM for Silk Typhoon in April 2023, and reads this as officials using whichever name was attached when the activity was first attributed [18]. Mandiant told The Hacker News that UNC5221 likely overlaps with APT27 and Silk Typhoon but that it lacks independent evidence [10]. GTIG’s published distinct-cluster statement specifically compares UNC5221 with Silk Typhoon [27].
Operational history (as the DeXpose profile sources it)
When
Activity
Tooling
Sourcing strength
Dec 2017–2020
Operation StealthyTrident: supply-chain compromise of the Able Desktop chat app in Mongolia via trojanized installers.
PlugX
ESET reference cited
Apr 2019
Three SharePoint servers at two Middle East government bodies breached, believed via CVE-2019-0604.
HyperBro
Unit 42 reference cited
Mar 2021
ProxyLogon exploitation of Exchange (CVE-2021-26855 and related) to deploy HyperBro.
HyperBro
HHS reference cited
2021
Zoho ADSelfService Plus CVE-2021-40539, at least nine organizations; shifted to ServiceDesk Plus CVE-2021-44077 on 25 Oct 2021.
—
HHS / Unit 42 cited
Nov 2021–mid 2022
MiMi chat supply chain: trojanized installers delivering HyperBro on Windows and rshell on macOS and Linux.
HyperBro, rshell
Trend Micro cited
Jan 2022
Germany's BfV reports intrusions at German companies via unpatched Exchange and ADSelfService Plus.
HyperBro
BfV brief and The Record cited
2022–2023
Budworm campaign against a Middle East government, an electronics maker and a U.S. state legislature via Log4Shell on Tomcat; SysUpdate gains Linux support; Aug 2023 new SysUpdate variant against a Middle East telecom and an Asian government.
SysUpdate, PlugX
Symantec / Trend Micro cited
11 Jul 2024
BfV warns APT27 is likely attacking European entities with new rshell versions; publishes a YARA rule.
rshell
BfV cited
Sept–Dec 2024
U.S. Treasury Department breach through Yin's VPS infrastructure (via BeyondTrust Remote Support SaaS, per the Silk Typhoon coverage).
Unit 42 (as "Iron Taurus") reports continued SysUpdate C2 activity from devices in 45 countries over the prior two years.
SysUpdate
Unit 42 cited
2026
No APT27-specific 2026 activity found in the sources opened for this page.
—
Gap
Malware the profile associates with APT27 beyond the table: ShadowPad, ZxShell, China Chopper, Pandora, OwaAuth, Mimikatz. The "active since 2009/2010" start date, the sector breakdown and most vendor-name mappings are weakly sourced in that profile; it infers vendors from reference URLs [19]. The April 2020 Polar ransomware and December 2020 gaming-sector incidents are listed there as unresolved attributions and are left out here. The August 2022 "@APT27_Attack" DDoS account is a hacktivist persona with no tooling overlap, not the group [19].
How it differs from Armory Castle in practice
APT27's documented pattern is widely known Windows and Linux backdoors (PlugX, HyperBro, SysUpdate), supply-chain and n-day exploitation of Exchange, Zoho and Log4Shell, and a for-profit data-brokerage layer around state tasking. Armory Castle's documented pattern is purpose-built appliance zero-days (Ivanti, BeyondTrust, VMware) with bespoke Go tooling and long dwell. Shared contractors are one possible explanation for the overlap in names, but only that: the government's alias list gives no explanation, the vendors decline to assert one, and none of the cited records establishes that the charged individuals ran the 2024–2026 appliance campaigns.
Further reading on the attribution overlap
Natto Thoughts has three pieces that bear on this section. None of them mentions Armory Castle, UNC5221, WARP PANDA, BeyondTrust or vCenter in the portions that could be read, so they give context for the disagreement without changing any edge on the map.
Piece
Date
What it adds
Access
Beyond the Aliases: Decoding Chinese Threat Group Attribution and the Human Factor
22 Oct 2025
The APT27 / HAFNIUM / Silk Typhoon naming problem as seen through U.S. government disclosures; the observation that DOJ used "APT27" for Yin and Zhou and "HAFNIUM" for Xu Zewei and Zhang Yu even though Microsoft retired HAFNIUM for Silk Typhoon in April 2023. Already cited as [18].
Read via fetch; a reviewer reports it paywalled past the preview
Zhou Shuai: A Hacker's Road to APT27
19 Mar 2025
Operator background: Zhou ("Coldface") as a first-generation Chinese patriotic hacker linked to the Green Army, later the owner of Shanghai Heiying and Yin Kecheng's alleged co-conspirator. Supports the people side of the indictment, not the 2026 campaigns.
The i-SOON case as an example of one contractor serving several government customers. Context for the shared-contractor hypothesis above; applying it to Armory Castle would still need case-specific evidence.
Not opened; scope per a reviewer's description [29]
Chinese advisories
Chinese-language evidence is grouped by source type. Qi An Xin CERT and NSFOCUS provide technical vCenter advisories; Tencent supplies explicit catalog cross-references. The Foreign Ministry statements are government denials about separate incidents, not technical evidence or attribution. The 渊龙Sec aggregator supplies discovery leads, not independent verification from Chaitin or Aliyun. iThome’s articles were checked directly. They report findings from Google/Mandiant and Volexity rather than independently attributing the campaigns.
A targeted Ghostwire production headline search found one NSFOCUS match for the five CVEs checked across the selected Chinese-language publishers. This was an explicit-ID headline check only: it does not measure those publishers’ full coverage or validate any actor relationship. A source does not count as corroboration simply because Ghostwire ingests it.
Source
Date
What it says
Bearing on this page
Ref
PRC Foreign Ministry, spokesperson Mao Ning, regular press conference
31 Dec 2024
Asked about the Treasury Department breach, called it a "groundless accusation lacking evidence" (缺乏证据的无端指控) and said China "has consistently opposed all forms of hacking attacks" and opposes "the spreading of false information targeting China for political purposes." No specific rebuttal.
The denial on record for the Treasury breach that Treasury later tied to Yin Kecheng [30]. Indirect: rejects the accusation rather than addressing the facts alleged.
PRC Foreign Ministry, spokesperson Lin Jian, answer on the indictment of 12 Chinese nationals
7 Mar 2025
"China firmly opposes the groundless accusations the U.S. has made against China" and demands it "stop its wrongful practice of abusing sanctions"; cites two December 2024 cases released by Chinese cybersecurity agencies alleging U.S. intelligence attacks on Chinese high-tech companies; calls the U.S. "the world's largest hacker empire" and "a thief crying 'stop thief'." Names no defendant, company or group; does not mention APT27 or the Treasury intrusion.
The denial on record for the Yin / Zhou / i-Soon indictments and the Heiying sanctions [16][31]. A blanket rejection plus counter-accusation, with no engagement on the individuals.
Qi An Xin CERT (奇安信) in-the-wild exploitation advisory on CVE-2026-123890, republished by 安全内参 (SecRSS)
20 Nov 2026
Titles the flaw "VMware vCenter 目录服务身份认证绕过漏洞" (Directory Service authentication bypass); assigns QVD-2026-112898; CVSS 3.1 9.8, Qi An Xin severity 高危; exploitation status 在野利用 "已发现", which the advisory states as Qi An Xin CERT's own detection ("监测到"); 利用可能性 "高"; POC, EXP and technical details all "未公开"; 影响量级 "十万级" (impact scale on the order of 100,000), with no methodology, denominator or geography given, so it is not a count of exposed or compromised hosts; affected and fixed versions match Broadcom. Cites Broadcom's advisory and a BleepingComputer article. Names no actor, victim, Google, Mandiant, Armory Castle or UNC5221, and lists no CNNVD or CNVD number.
Qi An Xin CERT reports detecting exploitation in the wild. The advisory provides no incident-level evidence or actor attribution.
The vCenter article uses the English names Armory Castle and UNC5221 and attributes the findings to Google and Mandiant. The separate BRICKSTORM article reports Volexity’s VerdantBamboo/UNC5221 cross-reference.
Traditional Chinese search wording and secondary coverage, not independent attribution or a verified Chinese-language actor alias.
Chinese government response to the Armory Castle / vCenter attribution
as of 20 Nov 2026
None found. The Chinese-language coverage reviewed here includes iThome’s reporting on the Google/Mandiant findings, not a PRC government response.
The page's statement that no Chinese government response to the vCenter attribution has been reported stands; it was published less than 24 hours before this check.
—
Chinese identifiers for the CVEs on this page
CVE stays the common key. QVD is Qi An Xin's identifier, TVD is Tencent's, NS- numbers are NSFOCUS advisories, and CNNVD and CNVD are the two national catalogs. CNNVD and CNVD could not be queried directly (robots refusal and a WAF challenge), so the two CNNVD IDs below are cross-referenced by Tencent, not directly verified in the national catalog, and no CNVD entry was confirmed for any CVE here.
CVE
Chinese ID(s)
Chinese title
Exploitation status, per vendor
Verification
Ref
CVE-2026-123890 · VMware vCenter
QVD-2026-112898 (Qi An Xin) · NS-2026-0037 (NSFOCUS)
Database snapshot · 20 November 2026 UTC. Of the 16 distinct CVEs explicitly named in this dossier, Ghostwire matched 10 in production and one more only in development. Five were not found in either database snapshot. Named vulnerability families without explicit IDs were not counted.
Chinese national catalogs: No native CNVD ID was confirmed. The production records contained eight CNNVD search links but no native CNNVD IDs for the named CVEs. A search link is a lead, not proof of a catalog entry. Tencent explicitly pairs CNNVD-202504-663 with CVE-2025-22457 [40] and CNNVD-202401-2693 with CVE-2024-21893 [42]; both are verified vendor cross-references, not direct CNNVD confirmations. The two named CNNVD IDs also returned no matches in a reverse search of production descriptions and reference data.
CVE-2026-123890 · VMware vCenter Directory Service authentication bypass
Critical · 9.8 CVSS v3.1 · Exploited in the wild
Broadcom published the advisory and rated the flaw Critical, with a maximum CVSS v3.1 base score of 9.8 [45]. Google and Mandiant report forensic evidence that ARMORY CASTLE used the flaw in early September 2026 [1].
VMware vCenter 目录服务身份认证绕过漏洞QVD-2026-112898 is Qi An Xin’s vulnerability identifier. Qi An Xin reports detecting exploitation in the wild; it doesn’t name the operator.
VMware vCenter 身份验证绕过漏洞NS-2026-0037 is its advisory number. NSFOCUS reports exploitation, cites Broadcom, and doesn’t name the operator. The advisory doesn’t establish a separate observation.
vCenter身分驗證繞過漏洞 · VMware vCenter零時差漏洞The article uses Armory Castle and UNC5221 and credits Google and Mandiant. It adds Traditional Chinese search wording, not independent attribution.
Catalog status: No directly verified CNNVD or CNVD identifier for this CVE. The QVD and NSFOCUS numbers are vendor references. No Chinese-language actor alias was verified in the sources reviewed.
GTIG reports campaign use [46]. The CVE record gives Ivanti’s CVSS v3.1 score of 9.0; Tencent gives 9.8 as its own assessment [40]. Neither score is a Ghostwire snapshot value.
Campaign use reported by Google [23]. BeyondTrust and the NVD entry show CVSS v4.0 9.3 [44]. Ghostwire’s stored 9.8 is an unresolved discrepancy, not a separate verified score.
Adjacent advisories, alias-overlap claims, and background
CrowdStrike reports use by WARP PANDA [25]; the ARMORY CASTLE connection remains a cross-map claim [2]. Broadcom’s 2.7 is cited in the dossier, not stored in this Ghostwire record.
APT27 background only; no ARMORY CASTLE inference.
CVE-2021-26855 Exchange
Not found in either snapshot
—
—
—
No CNNVD match verified
APT27 background only; no ARMORY CASTLE inference.
CVE-2021-40539 Zoho ADSelfService Plus
Not found in either snapshot
—
—
—
No CNNVD match verified
APT27 background only; no ARMORY CASTLE inference.
CVE-2021-44077 Zoho ServiceDesk Plus
Not found in either snapshot
—
—
—
No CNNVD match verified
APT27 background only; no ARMORY CASTLE inference.
Metrics are the values recorded in Ghostwire at the time of the lookup. Production values take precedence in this table; the development-only row is labeled. A dash means no value is shown from that snapshot, not zero. Stored severity and CVSS are not automatically attributable to a vendor. EPSS is a probability estimate; KEV marks known exploitation, not exploitation by this actor. A record not marked KEV is not evidence that it was never exploited. No catalog match upgrades an actor, alias, or campaign claim. Original citations and attribution caveats remain in the dossier.
What no source in this set establishes
GTIG assesses a suspected PRC nexus for ARMORY CASTLE [1]. U.S. Treasury identifies Yin Kecheng as MSS-affiliated in connection with the 2024 Treasury breach [30] and says Shanghai Heiying has employed him [31]. The DOJ announcement documents naming overlap in the cases against Yin and Zhou [11], not a confirmed operational match. The public sources reviewed do not link Yin, Zhou Shuai, or Shanghai Heiying to the 2026 BeyondTrust or vCenter intrusions. The sponsoring bureau, operational unit, and contractor remain unconfirmed.
What unit-level attribution looks like. In a separate investigation, Intrusion Truth reports that an internal eDiary references PLA Unit 61046, identified as the 8th Technical Reconnaissance Base, and reports infrastructure and victim overlap with specific activity previously attributed to APT15 [47]. This is the publisher’s assessment of a subset of APT15 activity, not independent confirmation or evidence about ARMORY CASTLE.
The identity or count of 2026 victims beyond "multiple incidents"; whether BONESAW is held exclusively by this cluster; whether WARP PANDA and UNC5221 are one team or two teams sharing tools; and whether the APT27 indictment's individuals are connected to the 2026 appliance campaigns. None of the opened sources reports a Chinese government response to the vCenter attribution.
Sources
Source review: 20 Nov 2026. The primary vSphere [1], BeyondTrust [23] and BRICKSTORM [27] reports were checked directly, as were the DOJ announcement [11] and FBI affidavit [14]. The individual entries note which other sources were checked directly, were available only as excerpts, or could not be opened.
Google Threat Intelligence Group and Mandiant, "ARMORY CASTLE Exploits vSphere," Google Cloud Blog, 19 Nov 2026. Primary report checked directly. GTIG links early September vCenter exploitation to ARMORY CASTLE and describes the preceding BeyondTrust intrusion. cloud.google.com
Ravie Lakshmanan, "China-Linked Hackers Exploit Critical VMware vCenter Zero-Day to Gain Admin Access and Steal Data," The Hacker News, 20 Nov 2026. thehackernews.com
Eduard Kovacs, "Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT," SecurityWeek, 19 Nov 2026. securityweek.com
Brandefense, "ARMORY CASTLE (UNC5221) threat group profile," metadata date 19 Oct 2026 but it describes the 19 Nov 2026 Google post, so it has been updated without a visible date. Secondary account of the UNC5337 merger. Mandiant’s January 17 changelog confirms the merger after publication of the January 8 report; it does not specify the exact merge date [24]. Also discusses "as early as October 2023, per GTIG"; the 15 Oct 2026 attribution of CVE-2026-102764, SAWFLY and BARECLAW; and "these sources do not establish a government attribution to ARMORY CASTLE". brandefense.io
Technology.org, "Google Warns of Widespread Attacks on BeyondTrust Remote Support Zero-Day," 16 Oct 2026. Only the search excerpt was available. Use the original Mandiant report [23] for the roughly 11-minute timing and for Google’s observation about past opportunistic exploitation after disclosure. technology.org
Tech Insider, "BeyondTrust Zero-Day Hits CVSS 9.3, China Blamed," 17 Oct 2026, updated 13 Nov. A secondary rewrite citing SecurityWeek, BankInfoSecurity and CSO Online; author's usual beat is games. Sole source here for the BSI advisory number 2026-297832. tech-insider.org
TechTimes, "China Hacked BeyondTrust Enterprise Vaults With Zero-Day Active for Seven Weeks," 19 Oct 2026. Excerpt only; its "high confidence, PRC state-sponsored" wording is stronger than Google's own "suspected" and is not used on this page. techtimes.com
ExtraHop, "The BRICKSTORM Campaign: UNC5221," 20 Feb 2026. Read in full. Gives the aliases UTA0178 and Red Dev 61 without naming a vendor; does not contain the 393-day figure; mentions ADFS only as a detection target, not as a compromised system. extrahop.com
The Hacker News, "UNC5221 Uses BRICKSTORM Backdoor to Infiltrate U.S. Legal and Technology Sectors," 24 Sept 2025. Read in full. Secondary reporting on average dwell time and attribution. See GTIG [27] for the 393-day figure and its specific distinction between UNC5221 and Silk Typhoon. thehackernews.com
The Hacker News, "U.S. Sanctions Chinese Cybersecurity Firm Over Treasury Hack Tied to Silk Typhoon," 18 Jan 2025, updated 5 Apr 2025. Read in full. Confirms the Treasury breach ran through a compromised BeyondTrust Remote Support SaaS API key and was attributed to Silk Typhoon; confirms Mandiant's "likely overlaps … no independent evidence" caveat; the sanctioned company in that action was Sichuan Juxinhe Network Technology, with Yin Kecheng named as MSS-affiliated. thehackernews.com
U.S. Department of Justice, "Chinese Nationals with Ties to the PRC Government and 'APT27' Charged in a Computer Hacking Campaign for Profit," Mar 2025. justice.gov
The Hacker News, "U.S. Charges 12 Chinese Nationals in State-Backed Hacking Operations," Mar 2025. thehackernews.com
U.S. Department of Justice, search warrant affidavit 25-sz-13 (Yin Kecheng infrastructure overlaps, Oct 2021–Feb 2022). Paragraph 24 (PDF page 16, printed page 8) reads “UNC5221” without a space; the DOJ announcement [11] uses “UNC 5221.” The public PDF checked here does not read “UNC3221.” Read FBI affidavit ¶24 (PDF)
Cyber Security News, "Hackers Exploit VMware vCenter 0-Day Since September to Hijack Admin Accounts and Steal VM Data," 20 Nov 2026; and NetManageIT, "ARMORY CASTLE's VMware vCenter Attack Chain Explained," 20 Nov 2026 (GDB/SUID detail). cybersecuritynews.com · netmanageit.com
U.S. Attorney's Office, District of Columbia, "Chinese Nationals with Ties to the PRC Government and 'APT27' Charged in a Computer Hacking Campaign for Profit," 5 Mar 2025. Read in full. justice.gov
Jonathan Greig, "US charges Chinese nationals in cyberattacks on Treasury, dissidents and more," The Record, 5 Mar 2025. Read in full. therecord.media
Natto Thoughts, "Beyond the Aliases: Decoding Chinese Threat Group Attribution and the Human Factor," 22 Oct 2025. The fetch returned the full analysis (Malpedia's 16 aliases, the HAFNIUM-versus-Silk Typhoon naming point, the Xu Zewei / Zhang Yu indictment of 8 Jul 2025); a reviewer reports the page paywalled past the preview, so readers without a subscription may see less. nattothoughts.substack.com
DeXpose, "Threat Actor Profile: APT27 Cyber Espionage Group," 15 Sept 2025, updated 15 Dec 2025. Read in full; a secondary profile whose own sourcing is uneven, as noted in the history table. dexpose.io
FBI Internet Crime Complaint Center, PSA I-030525-PSA on APT27 and i-Soon, 5 Mar 2025. Not opened; cited via [19]. ic3.gov
U.S. Department of Justice, "Justice Department Charges 12 Chinese Contract Hackers and Law Enforcement Officers," 5 Mar 2025. Not opened; the i-Soon companion release. justice.gov
Ionut Arghire, "Chinese APT Exploited BeyondTrust Vulnerability as Zero-Day," SecurityWeek, 16 Oct 2026. Read in full. Confirms: "also tracked as UNC5221 and Warp Panda"; first exploitation 29 Aug against one hosted and one self-hosted appliance; BeyondTrust identified the flaw 28 Sept; SAWFLY as a lightweight PHP web shell; BARECLAW as a custom SOCKS5 proxy tunneler. Contains no SAWFLY timing, no "selective to opportunistic" statement and no BSI reference. securityweek.com
Google Threat Intelligence Group and Mandiant, "ARMORY CASTLE Exploits BeyondTrust," Google Cloud Blog, 15 Oct 2026. Read in full. Primary source for: "suspected PRC-nexus espionage actor ARMORY CASTLE (formerly tracked as UNC5221)"; "active as early as October 2023"; zero-day use "in late August 2026"; SaaS tenants patched 9 Oct; SAWFLY and BARECLAW descriptions; the 11-minute interval between the initial POST request and SAWFLY's creation; the past-behaviour statement on opportunistic exploitation after disclosure; YARA rules for both tools. Does not mention WARP PANDA or UTA0178. cloud.google.com
Google Threat Intelligence Group and Mandiant, "Ivanti Connect Secure VPN Targeted in New Zero-Day Exploitation," Google Cloud Blog, 8 Jan 2025, with changelog to 17 Jan 2025. Read in full. Primary source for: UNC5221 as "a suspected China-nexus espionage actor" that "previously exploited" CVE-2023-46805 and CVE-2024-21887 "as early as December 2023"; the SPAWN family (SPAWNANT, SPAWNMOLE, SPAWNSNAIL, SPAWNSLOTH) and its original attribution to UNC5337; "Since the publication of this blog post, Mandiant has merged UNC5337 into UNC5221" with no date given. cloud.google.com
Defender Daily, "VMware ESX logging flaw abused by WARP PANDA," 29 Oct 2026. Read in full. Reports CrowdStrike's attribution of CVE-2026-41709 abuse to WARP PANDA, "a China-nexus group it tracks", citing CrowdStrike's 2026 legal-sector threat report; does not mention UNC5221 or Armory Castle. CrowdStrike’s own 28 Oct report was checked: it directly attributes early-2026 use to WARP PANDA, not to ARMORY CASTLE. defenderdaily.com · crowdstrike.com (primary report)
Malpedia (Fraunhofer FKIE), actor entry "UTA0178", aliases "ARMORY CASTLE, Red Dev 61, UNC5221". Read in full. Vendor for Red Dev 61 not indicated; WARP PANDA not listed as an alias; references include Volexity's 2024 Ivanti report and a 2024 QuoIntelligence WIREFIRE web shell analysis. malpedia.caad.fkie.fraunhofer.de
Google Threat Intelligence Group and Mandiant, BRICKSTORM espionage campaign report, Google Cloud Blog, 24 Sept 2025. Read in full on a later attempt. Primary source for the 393-day average dwell, the BRICKSTEAL mechanism (HTTP Basic header on /web/saml2/sso/*), the attribution "to UNC5221 and closely related, suspected China-nexus threat clusters", and the sentence "GTIG does not currently consider the two clusters to be the same" regarding Silk Typhoon. APT27 is not mentioned in it. cloud.google.com
Natto Thoughts, "Zhou Shuai: A Hacker's Road to APT27," 19 Mar 2025 (modified 12 May 2026). Introduction read; remainder paywalled. nattothoughts.com
Natto Thoughts, "Provincial Tasking, Cross-Provincial Execution," 28 Jan 2026. Not opened; listed as further reading on the strength of a reviewer's description of its scope. nattothoughts.com
U.S. Department of the Treasury, press release JY2792 (sanctions on Yin Kecheng and Sichuan Juxinhe Network Technology), 17 Jan 2025. Read in full. States Yin "is affiliated with the People's Republic of China Ministry of State Security (MSS)" and was "associated with the recent compromise of the Department of the Treasury's Departmental Offices network." Does not mention APT27, UNC5221, Silk Typhoon, a bureau or a unit. home.treasury.gov
U.S. Department of the Treasury, press release SB0042 (sanctions on Zhou Shuai and Shanghai Heiying Information Technology), 5 Mar 2025. Read in full. Describes Heiying as having "employed numerous known China-backed malicious cyber actors, including Yin Kecheng"; attributes Zhou's intelligence requirements to "the CCP's intelligence services"; does not mention MSS, MPS, the PLA, APT27, UNC5221 or Silk Typhoon in its text. home.treasury.gov
PRC Ministry of Foreign Affairs, regular press conference of spokesperson Mao Ning, 31 Dec 2024 (Chinese). Read in full and translated. Official government statement; partisan. mfa.gov.cn
PRC Ministry of Foreign Affairs, "Spokesperson's answer on the U.S. indicting 12 Chinese nationals on hacking grounds," Lin Jian, 7 Mar 2025 (Chinese). Read in full and translated. Official government statement; partisan. mfa.gov.cn
NSFOCUS CERT, "VMware vCenter身份验证绕过漏洞(CVE-2026-123890)通告," advisory NS-2026-0037, 20 Nov 2026 (Chinese). Read in full and translated. Chinese security vendor; technical only. blog.nsfocus.net
Volexity, "VerdantBamboo: Just Another BRICKSTORM in the Firewall," 4 Jun 2026. Read in full. Source for "a Chinese threat actor, which Volexity tracks as VerdantBamboo (WARP PANDA, UNC5221)", the BRICKSTORM Go/Rust/BSD variants, PLENET ("referred to as GRIMBOLT by Google Cloud"), AGENTPSD, and the Egnyte / Synology / pfSense chain. Does not mention Clay Typhoon or UTA0178. volexity.com
Ravie Lakshmanan, "VerdantBamboo Deploys BSD Variant of BRICKSTORM on Linux Appliances," The Hacker News, 8 Jun 2026. Read in full. Adds the overlap list "Clay Typhoon (Microsoft), UNC5221 (Google), and Warp Panda (CrowdStrike)"; the Clay Typhoon mapping is not in Volexity's post. thehackernews.com
BleepingComputer, "Chinese APT deploys new malware to keep access to hacked networks," 5 Jun 2026. Read in full. "UNC5221 is also tracked as VerdantBamboo." bleepingcomputer.com
Qi An Xin CERT, "VMware vCenter 目录服务身份认证绕过漏洞(CVE-2026-123890)在野利用通告," republished by 安全内参, 20 Nov 2026 (Chinese). Read in full and translated. Vendor advisory; technical only. secrss.com
iThome (Taiwan): the vCenter article’s indexed text and direct page were checked. The 20 November 2026 story uses Armory Castle and UNC5221 and credits Google and Mandiant. The separate BRICKSTORM article was also checked directly and credits Volexity for the VerdantBamboo/UNC5221 cross-reference. iThome vCenter article · iThome BRICKSTORM article
Tencent Cloud Security (云鼎实验室), "2025年4月必修安全漏洞清单," developer.cloud.tencent.com article 2651892 (Chinese). Read in full. Row 6: Ivanti多款产品 远程代码执行漏洞, TVD-2025-10575, CVE-2025-22457, CNNVD-202504-663, 高危, 9.8, 在野利用 已发现. The article notes its scores are Tencent's own assessment. developer.cloud.tencent.com
NSFOCUS, February 2024 monthly threat intelligence roundup (mentions CVE-2023-46805 and CVE-2024-21887), and Tencent Cloud Security article 2393588 (Jan 2024). The Tencent publication explicitly pairs CNNVD-202401-2693 with CVE-2024-21893 (TVD-2024-3703). The NSFOCUS roundup was not independently checked here. blog.nsfocus.net · developer.cloud.tencent.com
渊龙Sec 网络安全威胁情报 aggregator (threat.aabyss.cn), snapshot read 20 Nov 2026. Source for the Chaitin and Aliyun AVD entries for NGINX2Root and Java4Shell and the KEV mirrors for Apache Axis and BeyondTrust. No CNNVD/CNVD IDs and no actor names appear in it. threat.aabyss.cn
Broadcom VMSA-2026-0009: confirms CVSS v3.1 9.8 for CVE-2026-123890. Broadcom advisory
Google Threat Intelligence Group, “Suspected China-Nexus Threat Actor Actively Exploiting Critical Ivanti Connect Secure Vulnerability (CVE-2025-22457),” 3 Apr 2025. Read in full. Attributes the exploitation and “the SPAWN ecosystem of malware” to UNC5221 and confirms it previously observed use of Citrix CVE-2023-4966. Also describes TRAILBLAZE, BRUSHFIRE, SPAWNSNARE and SPAWNWAVE without naming a cluster for each. Does not mention LAZYBONES. Google report
Intrusion Truth, 28 July 2026, reports eDiary and campaign overlaps for a subset of activity previously attributed to APT15. Separate comparison; not evidence about ARMORY CASTLE. Intrusion Truth investigation
F5, 15 October 2025. The SEC filing dates discovery to 9 August and describes an unnamed nation-state actor; the advisory confirms theft of BIG-IP source code and information about undisclosed vulnerabilities. F5 SEC filing · F5 advisory K000154696
DCISE, DIB-Reported Cyber Threats, CY 2025 Q4 (11 February 2026). Reports researchers’ BRICKSTORM finding on F5 systems and labels UNC5221 suspected. The public bulletin provides limited attribution detail. DCISE bulletin (PDF)
Cloudflare / Cloudforce One, 2026 Threat Report overview. The public overview identifies PunyToad as a name it tracks. It does not itself list the proposed aliases or attribute the F5 incident. Cloudflare report overview
TLCTC, “PUNYTOAD-F5-BIGIP-2025.” Secondary account reporting a Cloudforce One cross-reference between PunyToad, UNC5221, UTA0178 and WARP PANDA, and linking PunyToad to F5. The primary Cloudflare statements for those two claims were not verified.
Mandiant and Google Threat Intelligence Group, “From BRICKSTORM to GRIMBOLT: UNC6201 Exploiting a Dell RecoverPoint for Virtual Machines Zero-Day,” Google Cloud Blog, 17 Feb 2026. Read in full from Ghostwire’s stored copy. Primary source for UNC6201, “a suspected PRC-nexus threat cluster”, deploying SLAYSTYLE, BRICKSTORM and GRIMBOLT; GRIMBOLT as a C# Native AOT backdoor packed with UPX that replaced BRICKSTORM in September 2025; and “There are notable overlaps between UNC6201 and UNC5221”. The same sentence repeats Google’s statement that it does not consider UNC5221 and Silk Typhoon the same cluster; it does not say whether UNC6201 and UNC5221 are distinct, beyond tracking them under separate names. The vSphere post [1] separately notes that UNC6201 also enabled vCenter SSH through the VAMI API. cloud.google.com
Matt Kapko, “Prolific Chinese espionage group exploits BeyondTrust zero-day,” CyberScoop, 16 Oct 2026. Read in full from Ghostwire’s stored copy. Quotes BeyondTrust’s security team: “This threat actor rotates its infrastructure and tooling for every victim, so attribution here rests on behavior.” BeyondTrust’s own post was not opened. cyberscoop.com
Google Threat Intelligence Group, “Updated Cyber Threat Actor Naming System,” 24 Jul 2026, table added 30 Jul. Read in full from Ghostwire’s stored copy. Table 2 maps “APT27 → SHORE CASTLE” and “APT15 → RIVER CASTLE”; the second word, CASTLE, marks People’s Republic of China actors. cloud.google.com