LiveActive security incident?Get immediate response
MITRE ATT&CK® Group

G0128: ZIRCONIUM

ZIRCONIUM is a threat group operating out of China, active since at least 2017, that has targeted individuals associated with the 2020 US presidential election and prominent leaders in the international affairs community.CitationMicrosoft Targeting Elections September 2020CitationCheck Point APT31 February 2021

EnterpriseG0128GroupObject v2.3Modified
Glexia's Take · Automated analysis

Security context for executives and security teams

Automation confidenceMedium

ATT&CK describes ZIRCONIUM, also known as APT31 and Violet Typhoon, as a China-based threat group active since at least 2017 and associated in reporting with targeting people connected to the 2020 U.S. presidential election and prominent international affairs leaders. For defenders, the useful takeaway is not the name alone: the mapped behaviors span phishing links, user-driven execution, discovery, credential access from browsers, persistence through Run Keys or startup folders, command-and-control over proxies/web services/encryption, tool transfer, and exfiltration over C2 or to cloud storage.

Executive priority

This group profile is most useful for prioritizing readiness around high-value people, politically or diplomatically sensitive work, and organizations where email, identity, endpoint, browser credentials, and cloud storage are business-critical. Leaders should ask whether the organization can prove prevention, detection, and response coverage for spearphishing links, suspicious script and command execution, browser credential theft, persistence changes, and unusual outbound or cloud-storage data movement.

Technical view

ATT&CK provides no group-specific detection text, so SOC and IR teams should validate coverage from the mapped techniques. Focus on Windows-relevant behaviors such as Registry queries, Run Key/startup persistence, cmd.exe, msiexec abuse, browser credential access, and task/service masquerading, while also checking cross-platform telemetry for Python execution, system/user/network discovery, inbound tool transfer, encrypted or proxied C2, and exfiltration to C2 or cloud storage. Detection logic should correlate early access indicators such as spearphishing links and malicious-link execution with follow-on discovery, persistence, credential access, and outbound transfer patterns.

Likely telemetry

  • Email security and URL-click telemetry for spearphishing links and malicious-link execution
  • Endpoint process creation, command-line, parent-child process, and script execution telemetry
  • Windows Registry auditing for discovery and Run Key/startup persistence changes
  • Service, scheduled task, startup folder, and task-name metadata for masquerading review
  • Browser credential store access and suspicious file access around browser profile data

Detection direction

  • Build behavior chains rather than relying on the group name: phishing link or user execution followed by discovery, credential access, persistence, tool transfer, and outbound transfer is higher-value than any single weak signal.
  • Tune Windows detections for cmd.exe, msiexec.exe, Registry queries, Run Key changes, and browser credential access, with allowlists for legitimate administration and software installation activity.
  • Review visibility gaps for encrypted C2, legitimate web-service communications, and cloud storage uploads, since these can blend into normal business traffic.
  • Use masquerading detections that compare task/service names, paths, publishers, and execution context against known-good baselines.
  • Treat proxy and cloud-service indicators carefully: the ATT&CK mapping supports these behaviors, but source IP attribution and service use alone are not reliable proof of this group.

Mitigation priorities

  • Prioritize phishing-resistant controls and user reporting workflows for high-risk staff and roles exposed to political, international affairs, or sensitive communications.
  • Harden endpoint execution paths by controlling script interpreters, command shell abuse, installer proxy execution, startup locations, and unauthorized persistence changes.
  • Reduce credential exposure by strengthening browser credential policy, endpoint protection, and identity monitoring for suspicious credential use.
  • Improve egress governance: monitor or restrict unsanctioned cloud storage, unusual external web-service use, and tool-transfer paths while preserving approved business workflows.
  • Maintain vulnerability and patch discipline because ATT&CK maps the group to exploitation for privilege escalation, but validate priorities against local asset exposure and exploitability.
Additional notes and limits

The decision value of this ATT&CK object comes from the relationship set: ZIRCONIUM is mapped to initial access through spearphishing links, execution through user action and command/script mechanisms, discovery, persistence, credential access, C2, and exfiltration. This supports a readiness review across SOC monitoring, incident response evidence collection, identity protection, cloud-storage governance, and vulnerability management.

ATT&CK provides no official detection guidance, no platforms on the intrusion-set object itself, and no claim here should be read as evidence of current activity against any specific organization. Platform references in this take come from related ATT&CK techniques, not from a group-level platform field. Local telemetry, exposure, and threat-intelligence validation are required before making risk or attribution judgments.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

ZIRCONIUM

ZIRCONIUM is a threat group operating out of China, active since at least 2017, that has targeted individuals associated with the 2020 US presidential election and prominent leaders in the international affairs community.CitationMicrosoft Targeting Elections September 2020CitationCheck Point APT31 February 2021

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

Relationship explorer

All related ATT&CK context

No relationships are available in the current normalized data for this object.

Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.

ATT&CK release
19.1
Object version
2.3
Created
Modified
Raw hash
2d23caddc21c7275...
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.