G0081: Tropic Trooper
Tropic Trooper is an unaffiliated threat group that has led targeted campaigns against targets in Taiwan, the Philippines, and Hong Kong. Tropic Trooper focuses on targeting government, healthcare, transportation, and high-tech industries and has been active since 2011.CitationTrendMicro Tropic Trooper Mar 2018CitationUnit 42 Tropic Trooper Nov 2016CitationTrendMicro Tropic Trooper May 2020
Security context for executives and security teams
Tropic Trooper is a long-running threat group in ATT&CK associated with targeted campaigns against government, healthcare, transportation, and high-tech organizations in Taiwan, the Philippines, and Hong Kong. For leaders, the practical issue is not the name of the group but the defensive pattern: ATT&CK links this group to remote access tools, backdoors, discovery activity, command-and-control over web and DNS protocols, automated exfiltration, and USB-based exfiltration relevant to air-gapped environments.
Executive priority
Prioritize this as a resilience and assurance use case where the organization operates in, supports, or resembles the sectors and regions described by ATT&CK, or where sensitive environments depend on segmentation or air gaps. Executives should ask whether security teams can prove visibility across Windows endpoints, command-line activity, removable media, DNS/web egress, local account use, and data movement. This object also supports audit and risk discussions around air-gapped operations, third-party/supply-chain exposure, and whether incident responders can investigate both connected and disconnected systems.
Technical view
ATT&CK does not provide a detection section for Tropic Trooper itself, so coverage should be validated through the linked software and techniques. Relationship context points to Windows-focused malware/tools including PoisonIvy, BITSAdmin, KeyBoy, YAHOYAH, USBferry, and ShadowPad, plus behaviors such as discovery, Windows command shell execution, DLL injection, masquerading, file deletion, local account abuse, web/DNS command-and-control, automated exfiltration, and exfiltration over USB. SOC and IR teams should map detections to these behaviors rather than relying on group-name alerts.
Likely telemetry
- Endpoint process creation and command-line telemetry, especially cmd.exe and administrative utilities
- Windows DLL load, process injection, and suspicious process access events where available
- File creation, modification, deletion, and unusual executable placement or naming patterns
- DNS query logs and web proxy/firewall egress logs for command-and-control analysis
- BITS job creation and usage telemetry on Windows systems
Detection direction
- Build behavior-based detections around the related ATT&CK techniques rather than expecting a single Tropic Trooper signature.
- Validate visibility for discovery commands and enumeration of users, processes, files, network configuration, network connections, and services.
- Tune web and DNS command-and-control analytics to reduce false positives from normal business traffic while retaining visibility into rare domains, unusual query patterns, and abnormal egress from sensitive hosts.
- Review removable media monitoring for environments that rely on air gaps; USB-based exfiltration is specifically represented through the USBferry and Exfiltration over USB relationships.
- Correlate local account use with unusual execution, discovery, or data movement because local accounts are listed as an abused access mechanism in the related techniques.
Mitigation priorities
- Start with asset and data prioritization for government, healthcare, transportation, high-tech, military, or air-gapped environments when relevant to the organization.
- Harden and monitor local accounts, especially administrative and shared local credentials; reduce reuse and ensure investigation-ready authentication logs.
- Restrict and monitor removable media use in sensitive and segmented environments, with documented exceptions and evidence collection procedures.
- Ensure endpoint controls capture command execution, suspicious DLL activity, file deletion, and unexpected tool use such as BITSAdmin.
- Control egress through DNS and web gateways, and retain logs long enough to support incident response and threat hunting.
Additional notes and limits
The group object has no official ATT&CK detection text, no tactics listed on the group object itself, and no group-level platforms specified. The technical guidance is therefore derived from the supplied relationships to software and techniques. The related software is Windows-focused, but several related techniques list additional platforms; local validation should determine which apply in the environment.
This take does not assert current activity, attribution beyond the ATT&CK group description, customer exposure, or guaranteed detection coverage. External references are cited by ATT&CK, but their detailed contents were not used beyond the supplied fields. Organizations need their own telemetry, asset criticality, geography, sector exposure, and incident history to determine priority.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Tropic Trooper
Tropic Trooper is an unaffiliated threat group that has led targeted campaigns against targets in Taiwan, the Philippines, and Hong Kong. Tropic Trooper focuses on targeting government, healthcare, transportation, and high-tech industries and has been active since 2011.CitationTrendMicro Tropic Trooper Mar 2018CitationUnit 42 Tropic Trooper Nov 2016CitationTrendMicro Tropic Trooper May 2020
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.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
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.
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: 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.