Pre-compromise mitigations involve proactive measures and defenses implemented to prevent adversaries from successfully identifying and exploiting weaknesses during the Reconnaissance and Resource Development phases of an attack. These activities focus on reducing an organization's attack surface, identify adversarial preparation efforts, and increase the difficulty for attackers to conduct successful operations. This mitigation can be implemented through the following measures: Limit Information Exposure: - Regularly audit and sanitize publicly available data, including job posts, websites, and social media. - Use tools like OSINT monitoring platforms (e.g., SpiderFoot, Recon-ng) to identify leaked information. Protect Domain and DNS Infrastructure: - Enable DNSSEC and use WHOIS privacy protection. - Monitor for domain hijacking or lookalike domains using services like RiskIQ or Domain…
MITRE mitigation sourceAdversaryGraph public intelligence page
This page is part of Threat Matrix, the public browser workspace for the main AdversaryGraph platform. Use it for ATT&CK pivots, actor and technique context, similarity leads, detection coverage review, and analyst-ready investigation paths.
Validation disclaimer: TTP overlap, actor similarity, generated summaries, and coverage findings are investigation leads, not attribution proof or operational validation without analyst review.
Main AdversaryGraph project Documentation Malware Analysis GitHub
Malware
Adversaries may develop malware and malware components that can be used during targeting. Building malicious software can include the development of payloads, droppers, post-compromise tools, backdoors (including backdoored images), packers, C2 protocols, and the creation of infected removable media. Adversaries may develop malware to support their operations, creating a means for maintaining control of remote machines, evading defenses, and executing post-compromise behaviors.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Citation: ActiveMalwareEnergy)(Citation: FBI Flash FIN7 USB) During malware development, adversaries may intentionally include indicators aligned with other known actors in order to mislead attribution by defenders.(Citation: Olympic Destroyer)(Citation: Risky Bulletin Threat actor impersonates FSB APT)(Citation: GamaCopy organization) As with legitimate development efforts, different skill sets may be required for developing malware. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's malware development capabilities, provided the adversary plays a role in shaping requirements and maintains a degree of exclusivity to the malware. Some aspects of malware development, such as C2 protocol development, may require adversaries to obtain additional infrastructure. For example, malware developed that will communicate with Twitter for C2, may require use of [Web Services](https://attack.mitre.org/techniques/T1583/006).(Citation: FireEye APT29)
Open detection, hunting, mitigation, and evidence workspace
Detection logic
Consider analyzing malware for features that may be associated with the adversary and/or their developers, such as compiler used, debugging artifacts, or code similarities. Malware repositories can also be used to identify additional samples associated with the adversary and identify development patterns over time. Much of this activity will take place outside the visibility of the target organization, making detection of this behavior difficult. Detection efforts may be focused on post-compromise phases of the adversary lifecycle.
Observed actors
G0003Ke3chang
G0004Turla
G0010APT29
G0016Lazarus Group
G0032Sandworm Team
G0034FIN7
G0046OilRig
G0049Kimsuky
G0094APT-C-36
G0099Indrik Spider
G0119Mustang Panda
G0129TeamTNT
G0139Aoqin Dragon
G1007Moses Staff
G1009LuminousMoth
G1014FIN13
G1016Moonstone Sleet
G1036RedCurl
G1039Play
G1040Salt Typhoon
G1045UNC3886
G1048Contagious Interview
G1052MirrorFace
G1054VOID MANTICORE
G1055TeamPCP
G1056NIMBUS MANTICORE
G1059
Correlated CTI and IR reports
Cyber Knowledge context
Use these routes to move from the ATT&CK behavior into explanation, implementation, evidence handling, validation, and defensive operations. Relevance is generated from explicit identifiers/names and governed topic mappings; it is not attribution evidence.
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 3 — Core Frameworks Models
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 4 — Collection Sources
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 5 — Analysis Techniques Tradecraft
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 6 — The Threat Actor Landscape
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 9 — Tools of the Trade
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 10 — Career Path Continuing Education
Cyber Threat Intelligence (CTI) · Exact technique name · 92/100Module 10 — Laboratories, tool discipline, and reporting
Red Team & Offensive Security · Exact technique name · 92/100Module 13 — Red-team infrastructure and operations
Red Team & Offensive Security · Exact technique name · 92/100Module 1 — Defensive mission, operating model, and SOC service
Blue Team & Defensive Security · Exact technique name · 92/100Module 7 — Endpoint defense and EDR
Blue Team & Defensive Security · Exact technique name · 92/100Reproducible research laboratory
Vulnerability Research & Exploit Development · Exact technique name · 92/100
MITRE mitigations
MITRE detection strategies and analytics
- AN2004 · Analytic 2004 — Consider analyzing malware for features that may be associated with the adversary and/or their developers, such as compiler used, debugging artifacts, or code similarities. Malware repositories can also be used to identify additional samples associated with the adversary and identify development patterns over time. Monitor for contextual data about a malicious payload, such as compilation times, file hashes, as well as watermarks or other identifiable configuration information. Much of this activity will take place outside the visibility of the target organization, making detection of this behavior difficult. Detection efforts may be focused on post-compromise phases of the adversary lifecycle.
Continue the investigation
Attack tools, simulations and detection rules
Follow explicit source relationships into the reference modules. Linked procedures and detectors are not claims of live validation or actor attribution.
- T1587.001 Malware simulation — Exact active technique ID
- T1587.001 detection rules — Exact active technique ID; not actor-specific detector coverage