The OlympicDestroyer malware disrupted IT systems tied to the 2018 Winter Olympics in Pyeongchang, knocking out Wi-Fi, display systems, the Olympics website, and ticket-printing services shortly before the opening ceremony. Investigators described the operation as a destructive self-propagating worm that used stolen credentials and PsExec for lateral movement, then wiped files on remote shares, deleted backups and shadow copies, cleared event logs, disabled services, and forced systems to reboot into an unusable state. The intrusion also affected organizations connected to the Games, including ski resort hotels, an automation software vendor, Atos, and potentially collateral networks in Europe, with one ski resort automation server identified as the likely patient zero for the destructive outbreak.
Researchers found the attackers had conducted spearphishing against Olympic partners, moved manually through compromised networks before launching the worm, and operated command-and-control infrastructure through an Argentinian server bought via a Bulgarian reseller and accessed over NordVPN. The investigation concluded that several of the most prominent attribution clues were intentionally misleading: artifacts appeared to overlap with NotPetya, BadRabbit, Chinese threat actors, Sofacy, and Lazarus/BlueNoroff, but some of the strongest Lazarus-linked indicators, including a Rich header fingerprint, were assessed to have been deliberately forged. The attack was therefore seen not only as a sabotage campaign against Olympic infrastructure, but also as a deliberate effort to confuse investigators with sophisticated false-flag techniques.

TTPs, infrastructure, and targeting history in one profile.
7 events from the most recent confirmed update back to the earliest known activity.
Subsequent analysis found that several strong attribution clues, especially artifacts suggesting Lazarus involvement such as a Rich header fingerprint, were likely deliberately planted to mislead investigators.
U.S. officials told The Washington Post that Russian military intelligence was behind the Olympic cyberattack and had tried to make it appear as though North Korea was responsible. The report marked an early public attribution shift in the aftermath of the Pyeongchang disruption.
Investigators determined that a ski resort automation software server was the initial infection point for one destructive outbreak tied to the OlympicDestroyer operation.
The malware propagated using stolen credentials and PsExec, wiping files on remote shares, deleting backups and shadow copies, clearing logs, disabling services, and rebooting systems into an unusable state across multiple organizations.
Just before the opening ceremony of the 2018 Winter Olympics in Pyeongchang, OlympicDestroyer was launched, disrupting Wi-Fi, display systems, the Olympics website, and ticket-printing infrastructure.
Investigators found evidence that the operators gained access to multiple Olympic-related environments and performed manual lateral movement before deploying the worm component.
Before the 2018 Winter Olympics, attackers conducted spearphishing campaigns against Olympic-related organizations and partners as part of the preparation for the later destructive operation.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. View all 77 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See this adversary's TTPs, infrastructure, and targeting history, correlated against your exposure.
6 references tracked. Mallory keeps watching after this page renders.
darknetdiaries.com
Open sourcesecurelist.com
Open sourcecyber.wtf
Open sourcewashingtonpost.com
Open sourceblog.talosintelligence.com
Open sourcevirusbulletin.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.