- Date
- August 15, 2012
- Location
- Saudi Arabia
- Industry
- Oil & Gas
- Access vector
- Phishing
- OT targeting
- Indirect: IT dependency
- Primary peril
- None
- Impact duration
- Weeks to months (disputed)
Saudi Aramco Shamoon wiper attack, 2012

The incident path, stage by stage
Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.
Scroll sideways to see every stage.
On this page
Highlights
What happened. On August 15, 2012, a wiper called Shamoon began erasing Saudi Aramco’s corporate Windows computers, and Aramco said about 30,000 workstations were affected[1]. Aramco said its production systems, isolated from that network, were not affected[2][1]. According to Chris Kubecka, a consultant Aramco hired after the attack, the loss of payment systems stopped domestic fuel sales to tank trucks for 17 days[3].
Why it matters. It is an early case of an attack that never reached control systems but, by one first-hand account, still stopped part of an energy company’s business. The plants kept producing; the company could not take payment for fuel at home.
About this analysis. This analysis sets out what is known, stage by stage. Much of the detail on the disruption and the recovery comes from one person, Kubecka, speaking three to seven years later, and Aramco has confirmed none of it. It reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- Shamoon overwrites files and the master boot record so a computer will not start[4]. Aramco put the number affected at about 30,000 workstations; Kubecka puts it at more than 35,000[1][5].
- Aramco said its exploration and production systems were unaffected and its plants fully operational, “as these control systems are also isolated”[1].
- In Kubecka’s account, Aramco stopped selling oil to domestic tank trucks, began giving it away free after 17 days, ran on paper and faxes, and bought 50,000 hard drives[3][6]. Aramco never disclosed a cost.
- A group calling itself Cutting Sword of Justice claimed the attack. US intelligence sources attributed it to Iran but offered no specific evidence, and no government has formally attributed it[1][7].
Attack flow
- Updated: 2026-10-22
- Intent: Malicious [confirmed]
- Threat actors: Hacktivists [reported | Cutting Sword of Justice claim]; Nation-State [reported | Iran, per anonymous US officials]
- Access vector: Phishing [confirmed | T1566, per Kubecka]
- IT impact: Data Sabotage [confirmed | T1485; T1561.002 reported]; Malware [confirmed | Shamoon wiper]; System Outage [confirmed | payment systems, per Kubecka]
- OT targeting: Indirect: IT Dependency [confirmed]
- OT sophistication: Not applicable [not in path | OT not reached]
- OT impact: Not in path [not in path | Production systems isolated, not reached]
- Perils: No Perils [confirmed | No physical event]
- Financial losses: Business Interruption [confirmed]; Hardware Bricking [confirmed | $5M–$10M est.]; Cyber Incident Response [confirmed]; Data Loss [implied]; Reputation Damage [implied]
What happened
Kubecka says the attackers were inside from about April or May 2012[8]. Her Black Hat 2015 timeline lists a “Targeted Phishing attack” and an “Internal Saudi Aramco PC used as proxy by attackers”, both with no date[5]. The wiper struck on August 15, during Ramadan, when most employees were on holiday[3]. The group that claimed the attack gave 11:08 AM Saudi time; Kaspersky found the same moment, 08:08 UTC, hard-coded in the malware[9].
Symantec’s analysis, which names no victim, describes a dropper, a wiper and a reporter: the wiper overwrites files and the master boot record, and the reporter sends the attackers a count of overwritten files and the computer’s IP address[4]. US Secretary of Defense Leon Panetta said the routine “replaced crucial system files with an image of a burning U.S. flag”[10]. Aramco disconnected from the internet the same day[5].
On August 16, Aramco said a virus was suspected to have infected personal workstations, not the primary servers and core network, and that production was not affected[2]. On August 26 it said its main internal network services had been restored and the workstations “cleaned and restored to service”[11][1]. Its chief executive said there was “no doubt whatsoever about Saudi Aramco meeting its commitments to its customers worldwide”[12].
Kubecka’s account runs longer. Tank trucks seeking refills were turned away because there was no way to take payment, staff worked on paper with typewriters and fax machines, and Aramco bought 50,000 hard drives[3][6]. She says it took five months, or about three and a half months, to get back to normal[3][8]. Less than two weeks after the Aramco attack, the Qatari gas producer RasGas was knocked offline; a spokesman said gas extraction and processing were not affected[13][14].
Intent: malicious
The attack was built to destroy: Shamoon makes computers unusable, and its reporter tells the attackers only how many files it overwrote and where[4]. The claimants framed it as a political act against the al-Saud regime[1]. No ransom or other demand was made, and no source describes any attempt to make money from the attack. The incident is sometimes grouped with ransomware; it does not belong there.
Threat actors: claimed, not formally attributed
A group calling itself Cutting Sword of Justice claimed the attack on Pastebin, saying it acted against the al-Saud regime. It later posted core router names and admin passwords, and the chief executive’s email address and “supposed” password[1]. Those are the attackers’ own claims.
US intelligence sources, speaking to the New York Times, attributed the attack to Iran; CCDCOE notes that they offered no specific evidence[13][7]. CFR suggests Iran may have been responding to the April 2012 Wiper attack on Iran’s oil ministry and national oil company, which is its reading, not a finding[13]. No government has formally attributed the attack. Both the claim and the Iranian attribution are shown as reported.
Access vector: a phishing email
The only account of the entry point comes from Kubecka. She told CNNMoney that a computer technician on Aramco’s IT team “opened a scam email and clicked on a bad link”[3], and Dark Reading reports her account as a spear-phishing email[6]. Her Black Hat timeline lists the phishing attack and an internal PC used as a proxy, both marked “Date unknown”[5]. Aramco itself said only that a virus was suspected to have infected personal workstations[2].
Phishing is shown as confirmed on her first-hand account. The date of the email, how long the attackers were inside before August 15, and how they obtained credentials and moved between machines remain unknown.
IT impact: tens of thousands of computers wiped
Data destruction is confirmed. Kubecka’s slides say more than 35,000 Aramco PCs began “shutting down & being wiped” on August 15, and Aramco said about 30,000 workstations were affected[5][1]. The master boot record overwrite is described by Symantec and MITRE at the level of the malware, and neither names Aramco, so that technique is shown as reported[4][15]. MITRE also says Shamoon copies itself to other machines on the network; no Aramco-side source describes how it spread[15].
The sources disagree on servers. Aramco said the primary servers and core network were not hit; Kubecka says the attackers targeted “desktops, mail servers, and other Windows systems”[2][6]. Her slide sums up the business effect: “No IT payment systems, no Gas”[5]. No personal-data compromise is documented.
OT targeting: indirect, through IT
The control systems were not touched. What stopped, in Kubecka’s account, was the commercial side: the payment systems needed to sell fuel to domestic tank trucks were wiped, so trucks were turned away[3][6]. That is an indirect effect through an IT dependency. CNNMoney reports that production held at 9.5 million barrels per day, from company records[3].
OT sophistication: not applicable
No OT system was reached, so there is no OT technique to rate. The malware itself was capable on Windows: it used a legitimate disk driver, which MITRE names RawDisk, to write straight to disk sectors[4][15]. That capability says nothing about the attackers’ ability to act on industrial control systems, and no source suggests they tried.
OT impact: not in this attack’s path
Aramco said its exploration and production systems were unaffected and its production plants fully operational, “as these control systems are also isolated”[1]. Kubecka’s slides also read “ICS & IT networks isolated”[5]. No ICS technique is sourced, and no controller, remote terminal unit or field instrument is described as corrupted, replaced or reflashed. The stage is marked Not in path.
Perils: none
There was no physical event. Bricking was considered and not adopted. Panetta said the infected computers “were rendered useless, and had to be replaced”[10], but Aramco said its workstations were “cleaned and restored to service”[1], and a wiped disk can be reimaged, so no source establishes hardware that could not be restored. The stop in domestic fuel sales was commercial, with no physical failure behind it.
Isolation kept the plants producing; it could not keep the payment systems running.
Financial losses: what it cost
Aramco never disclosed a cost. As a state-owned, unlisted company in 2012 it had no filing that would have forced one: its shares first traded in Riyadh on December 11, 2019[16]. The only figure is our own estimate for the replacement hard drives, and it must not be read as a number Aramco reported. Most of the confirmed losses below rest on Kubecka’s account.
Loss evidence
- Confirmed: Lost domestic fuel sales to tank trucks; Manual operations and workarounds (paper, typewriters, faxes); Third-party physical and societal impact (tank trucks turned away); Computer and laptop replacement (50,000 hard drives bought); Network event response and recovery; Voluntary improvements (a security operations center)
- Estimated: $5M–$10M Replacement hard drives only, 50,000 drives at an assumed $100–$200 each (low confidence)
- Estimate note: Our own estimate, not a disclosed cost, set against published 2012 drive prices[17][18]; it is a floor that leaves out labor, travel, lost sales and the months of recovery.
- Implied: Production data integrity; Server replacement; Public relations response
- Not supported: Proprietary data response and recovery; Ransom extortion; Market valuation; Sensitive personal data response; Network device replacement; Embedded device replacement; Industry regulation liability
Kubecka called it “a tremendously expensive recovery”, which included building a security operations center[6]. No insurance claim, compensation or count of the trucks and stations affected has been published.
What this incident shows
Shamoon is one of the few cases where a working control is on the record. Tens of thousands of corporate computers were wiped, and the production networks, which Aramco says were isolated, were not reached[1]. On the other side of the ledger, a single phishing email, by Kubecka’s account, was enough to give the attackers a foothold that spread across the company[3].
The recovery points to a second gap, more tentatively. Buying 50,000 hard drives at a premium, rather than restoring machines from central images or backups, is consistent with limited enterprise-wide backup and redeployment capability in 2012[3]. No source describes Aramco’s backup arrangements at the time, so that is an inference from how it recovered, not a confirmed cause.
References
- Leyden, John. “Saudi Aramco malware attack analysis.” The Register, 29 Aug. 2012. theregister.com/2012/08/29/saudi_aramco_malware_attack_analysis/
- Gronholt-Pedersen, Jacob (Dow Jones Newswires). “Saudi Aramco computer network attacked by virus, operations unaffected.” Hydrocarbon Processing, 16 Aug. 2012. hydrocarbonprocessing.com/news/2012/08/saudi-aramco-computer-network-attacked-by-virus-operations-unaffected/
- “The inside story of the biggest hack in history.” CNNMoney, 5 Aug. 2015. money.cnn.com/2015/08/05/technology/aramco-hack/
- Symantec Security Response. “The Shamoon Attacks.” Symantec Connect (Broadcom), 16 Aug. 2012. community.broadcom.com/symantecenterprise/communities/community-home/librarydocuments/viewdocument?DocumentKey=281521ea-2d18-4bf9-9e88-8b1dc41cfdb6&CommunityKey=1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68&tab=librarydocuments
- Kubecka, Chris. “How to Implement IT Security after a Cyber Meltdown.” Black Hat USA 2015, Aug. 2015. blackhat.com/docs/us-15/materials/us-15-Kubecka-How-To-Implement-IT-Security-After-A-Cyber-Meltdown.pdf
- Rashid, Fahmida Y. “Inside The Aftermath Of The Saudi Aramco Breach.” Dark Reading, 8 Aug. 2015. darkreading.com/attacks-breaches/inside-the-aftermath-of-the-saudi-aramco-breach
- NATO CCDCOE. “Shamoon (2012).” International Cyber Law: Interactive Toolkit. cyberlaw.ccdcoe.org/wiki/Shamoon_(2012)
- Rhysider, Jack. “Ep 30: Shamoon.” Darknet Diaries, 22 Jan. 2019. darknetdiaries.com/episode/30/
- Constantin, Lucian. “Kill timer found in Shamoon malware suggests possible connection to Saudi Aramco attack.” Network World, 23 Aug. 2012. networkworld.com/article/712862/smb-kill-timer-found-in-shamoon-malware-suggests-possible-connection-to-saudi-aramco-attack.html
- Garamone, Jim. “Panetta spells out DOD roles in cyberdefense.” American Forces Press Service, via army.mil, 11 Oct. 2012. army.mil/article/89031/panetta_spells_out_dod_roles_in_cyberdefense
- Kirk, Jeremy. “Saudi Aramco restores internal network after malware attack.” PCWorld (IDG News Service), 26 Aug. 2012. pcworld.com/article/460895/saudi_aramco_restores_internal_network_after_malware_attack.html
- Prince, Brian. “Saudi Aramco Oil Company Says It Fought Off Malware Attack.” eWeek, 27 Aug. 2012. eweek.com/security/saudi-aramco-oil-company-says-it-fought-off-malware-attack/
- Council on Foreign Relations. “Compromise of Saudi Aramco and RasGas.” Cyber Operations Tracker, 16 Aug. 2012. cfr.org/cyber-operations/2012/08/16/compromise-of-saudi-aramco-and-rasgas/
- Leyden, John. “Mystery virus attack blows Qatari gas giant RasGas offline.” The Register, 30 Aug. 2012. theregister.com/security/2012/08/30/mystery-virus-attack-blows-qatari-gas-giant-rasgas-offline/1326164
- MITRE. “Shamoon, Software S0140.” MITRE ATT&CK, version 2.2, 17 Nov. 2024. attack.mitre.org/software/S0140/
- Reuters. “Saudi Aramco shares at 10% premium above issue price on listing day.” Business Today, 11 Dec. 2019. businesstoday.in/markets/company-stock/saudi-aramco-shares-at-10-premium-above-issue-price-on-listing-day/story/391888.html
- Vilches, Jose. “Hard Drive Pricewatch: Thai Floods.” TechSpot, 7 Feb. 2012. techspot.com/guides/494-hard-drive-pricewatch-thai-floods
- Soulskill. “A Year After Thailand Flooding, Hard Drive Prices Remain High.” Slashdot, 9 Nov. 2012, summarizing TechReport. hardware.slashdot.org/story/12/11/09/1634247


