Olympicdestroyer

Overview

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).

Understanding the Olympic Destroyer Wiper
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.

Execution, Deception, and Destruction Mechanics
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`).

Indicators of Compromise & Impact
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.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1003: Monitor for LSASS memory dumping or registry SAM extraction. Enable Credential Guard on Windows systems.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_OLYMPICDESTROYER {
    meta:
        description = "Detects Olympicdestroyer (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "olympicdestroyer" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Olympicdestroyer Activity
id: 33b1b78d4707954818413139ce7b01e7
status: experimental
description: Detects generic indicators of the olympicdestroyer malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*olympicdestroyer*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. In a wiper scenario, immediate, physical disconnection of all network segments is critical to stop the rapid lateral spread via WMI and SMB.
2. 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.
3. Initiate disaster recovery protocols utilizing completely isolated, offline 'cold' backups, as online backups were likely targeted and destroyed by the wiper.
4. Assume all administrative credentials across the domain have been compromised; a full Active Directory credential reset is mandatory.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not trust initial attribution indicators found within the malware code; sophisticated actors use false flags (like Lazarus-style wiping routines) to deceive analysts.
2. Avoid relying on standard anti-ransomware behavioral blockers, as wipers often act faster than behavioral engines can analyze the intent.

References & External Analysis

• Search "olympicdestroyer" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Ngvck
• Blubot
• Qmlfrt0J91Kid
• Genericrxat
• Dreambot

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/olympicdestroyer.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.