{
  "family": "olympicdestroyer",
  "sample_count": 5,
  "category": "ransomware",
  "description": "Trojan:Win32/Olympicdestroyer (or simply **Olympic Destroyer**) is a highly sophisticated, destructive wiper malware deployed during the opening ceremony of the 2018 Winter Olympics in Pyeongchang, South Korea. The attack crippled the Olympic IT infrastructure, taking down the official website, Wi-Fi networks, and broadcast systems. It is legendary in the threat intelligence community not just for its impact, but for its unprecedented use of **false flags**—code artifacts intentionally planted to misdirect attribution away from the actual perpetrators (widely believed to be the Russian GRU / Sandworm team).<br><br><b>Understanding the Olympic Destroyer Wiper</b><br>To an observer, the attack looked like ransomware, but it was purely destructive; there was no mechanism to recover the data. For security analysts, Olympic Destroyer was a masterclass in deception. The malware contained code snippets mimicking the Lazarus Group (North Korea) and customized Rich Headers matching tools used by Chinese APTs. The goal was to cause chaos while framing other nation-states for the disruption.<br><br><b>Execution, Deception, and Destruction Mechanics</b><br>Olympic Destroyer was likely deployed laterally across the Olympic network using stolen credentials (`T1078`). Once executed, it acted incredibly fast. It used WMI and PsExec for rapid lateral movement across the internal network (`T1047`, `T1569.002`). It aggressively disabled endpoint security and deleted all backup catalogs and Volume Shadow Copies (`vssadmin.exe delete shadows`) to prevent recovery (`T1490`). It did not encrypt files; it simply wiped them and rendered the machines unbootable by destroying the Master Boot Record (MBR) (`T1561.002`). The malware was highly tailored, containing hardcoded lists of Olympic infrastructure hostnames and utilizing a built-in credential stealer (a modified version of Mimikatz) to further propagate (`T1003`).<br><br><b>Indicators of Compromise & Impact</b><br>The impact was massive IT paralysis. Host-based IoCs included the sudden execution of `vssadmin.exe`, `wbadmin.exe`, and `bcdedit.exe` to destroy recovery options. System event logs would show thousands of critical files being deleted, followed by the system crashing and failing to find a bootable device on restart. The presence of the specific credential stealing module dropped in the `%Temp%` directory was a key signature.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Olympicdestroyer and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Olympicdestroyer is classified as a Ransomware. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments."
      }
    },
    {
      "@type": "Question",
      "name": "How does Olympicdestroyer establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Olympicdestroyer typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Olympicdestroyer compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Olympicdestroyer should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups."
      }
    },
    {
      "@type": "Question",
      "name": "What cryptographic algorithms and file targeting techniques does Olympicdestroyer employ during execution?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Olympicdestroyer typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options."
      }
    },
    {
      "@type": "Question",
      "name": "Are decryptors available for Olympicdestroyer, and what is the recommended recovery procedure?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Decryption availability for Olympicdestroyer depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1485",
    "T1490",
    "T1561.002",
    "T1003"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1561.002",
      "name": "Disk Wipe: Disk Structure Wipe (Destroying the MBR)",
      "tactic": "Impact"
    },
    {
      "id": "T1485",
      "name": "Data Destruction (Wiping critical files)",
      "tactic": "Impact"
    },
    {
      "id": "T1490",
      "name": "Inhibit System Recovery (Deleting Shadow Copies)",
      "tactic": "Impact"
    },
    {
      "id": "T1003",
      "name": "OS Credential Dumping (Modified Mimikatz for lateral movement)",
      "tactic": "Credential Access"
    }
  ],
  "containment_steps": [
    "In a wiper scenario, immediate, physical disconnection of all network segments is critical to stop the rapid lateral spread via WMI and SMB.",
    "Do NOT attempt to reboot affected machines; if the MBR is wiped, they will not boot. Attempt offline forensic imaging of the drives to recover any unwiped data sectors.",
    "Initiate disaster recovery protocols utilizing completely isolated, offline 'cold' backups, as online backups were likely targeted and destroyed by the wiper.",
    "Assume all administrative credentials across the domain have been compromised; a full Active Directory credential reset is mandatory."
  ],
  "what_to_avoid": [
    "Do not trust initial attribution indicators found within the malware code; sophisticated actors use false flags (like Lazarus-style wiping routines) to deceive analysts.",
    "Avoid relying on standard anti-ransomware behavioral blockers, as wipers often act faster than behavioral engines can analyze the intent."
  ],
  "target_industries": [
    "Healthcare",
    "Critical Infrastructure",
    "Enterprise"
  ],
  "motivation": "Financial Extortion",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "defense_evasion",
    "impact"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}