Olympicdestroyer
Table of Contents
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 our technical analysis hubs and the official 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.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-LSA | LSASS Memory Protection | Harden | T1003 | Enable Windows Credential Guard (LsaCfgFlags) and restrict debug privileges (SeDebugPrivilege). |
D3-WORM | Immutable Backup Storage | Harden | T1485 | Store primary backups in Write-Once-Read-Many (WORM) cloud repositories protected by multi-party out-of-band credentials. |
D3-VSS | Volume Shadow & Snapshot Hardening | Harden | T1490 | Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories. |
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_OLYMPICDESTROYER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Olympicdestroyer"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "olympicdestroyer" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Olympicdestroyer (Ransomware) Execution & Triage
id: b18997bf-33fb-5fc0-aa7a-69f3ee75ff46
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Olympicdestroyer malware family. Detects volume shadow copy deletion, boot
status tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/olympicdestroyer
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1485
- attack.t1490
- attack.t1561_002
- attack.t1003
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \vssadmin.exe
- \wmic.exe
- \wbadmin.exe
- \bcdedit.exe
CommandLine|contains:
- delete shadows
- shadowcopy delete
- resize shadowstorage
- recoveryenabled no
- ignoreallfailures
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_OLYMPICDESTROYER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Olympicdestroyer tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "olympicdestroyer" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- 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
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- 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.
References & External Analysis
- Search "olympicdestroyer" on VirusTotal (External Analysis)
- Search "olympicdestroyer" on Any.Run (Sandbox Sandbox)
- Search "olympicdestroyer" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Olympicdestroyer and what threat category does it belong to?
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.
How does Olympicdestroyer establish persistence and evade defensive controls?
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.
What are the essential incident response steps for mitigating a Olympicdestroyer compromise?
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.
What cryptographic algorithms and file targeting techniques does Olympicdestroyer employ during execution?
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.
Are decryptors available for Olympicdestroyer, and what is the recommended recovery procedure?
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.
How do I remove the Olympicdestroyer Ransomware from Windows?
Manual removal of Olympicdestroyer is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Olympicdestroyer a virus or a Ransomware?
Olympicdestroyer is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Olympicdestroyer typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Olympicdestroyer infection?
Symptoms of Olympicdestroyer can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Ransomwares
Want to prevent Olympicdestroyer and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/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.