Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

8/27/2012
04:49 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

30,000 Machines Infected In Targeted Attack On Saudi Aramco

Oil company's revelation matches counts by hackers claiming responsibility and Shamoon connection

In what may be the closest sign yet to a public confirmation that this month's targeted attack against Saudi Aramco was actually the malicious Shamoon malware attack, the massive oil company yesterday revealed that 30,000 of its workstations had been infected in the attack -- the same number quoted by the attackers who took responsibility for it and gave a hat tip to the Shamoon research in an online post.

Though Saudi Aramco, Symantec, and Kaspersky Lab won't confirm the connection between Shamoon and the targeted attack on the oil company, other security experts say this could finally be the piece of the puzzle that connects the two, even though the oil company didn't name Shamoon yesterday.

Aviv Raff, co-founder and CTO at Seculert, said Saudi Aramco's statement yesterday appears to be a confirmation that the Shamoon attack was also aimed at Saudi Aramco due to the matching number of attacked machines confirmed by the oil company, as well as the behavior of the malware and timing of the two attacks.

Meantime, one source with knowledge of the attacks told Dark Reading that the attack on Saudi Aramco was, indeed, Shamoon.

In a statement on its website yesterday, Saudi Aramco said its internal resources hit by the attack are now back up and running: "Saudi Aramco has restored all its main internal network services that were impacted on August 15, 2012, by a malicious virus that originated from external sources and affected about 30,000 workstations. The workstations have since been cleaned and restored to service. As a precaution, remote Internet access to online resources was restricted," according to the statement.

The statement also noted that Saudi Aramco was not the only intended target of the attackers, something researchers at Seculert had concluded earlier this month. Seculert says Shamoon targeted "several specific companies in a few industries."

Khalid A. Al-Falih, president and CEO at Saudi Aramco, said in a statement yesterday: "We addressed the threat immediately, and our precautionary procedures, which have been in place to counter such threats, and our multiple protective systems, have helped to mitigate these deplorable cyber threats from spiraling. Saudi Aramco is not the only company that became a target for such attempts, and this was not the first nor will it be the last illegal attempt to intrude into our systems, and we will ensure that we will further reinforce our systems with all available means to protect against a recurrence of this type of cyber-attack."

[ Still no definitive connection between Shamoon and Saudi Aramco breach, but new clues emerge. See Shamoon, Saudi Aramco, And Targeted Destruction. ]

Meanwhile, yet another anonymous Pastebin post appeared today that claims to have committed a second wave of attacks against the oil company not yet publicized, this time dumping what appear to be router passwords pilfered from the company's network, as well as the alleged email and password for CEO Al-Falih. "We think it's funny and weird that there are no news coming out from Saudi Aramco regarding Saturday's night. well, we expect that but just to make it more clear and prove that we're done with we promised, just read the following facts -valuable ones- about the company's systems," the post said in its introduction.

Saudi Aramco first announced that it was hit by a virus on Aug. 15 that led to the shutdown of many of its internal systems. A day later, Symantec revealed its findings on Shamoon, a targeted attack that's all about total annihilation of data, not theft like other targeted attacks. Symantec didn't name the victim of the attack, but did say it was an energy-sector company in the Middle East.

Meanwhile, there were multiple Pastebin posts in the ensuing days by self-professed hackers claiming responsibility for the attacks on Saudi Aramco for reasons of protest. The most telling post referred to Shamoon, saying: "Symantec, McAfee and Kaspersky wrote a detail analysis about the virus, good job," and also claimed to have "completely destroyed" 30,000 clients and servers at the oil company -- the victim machine count that Saudi Aramco has now confirmed.

Researchers at Kaspersky Lab previously had spotted a time correlation between the Aramco attack and the date and time found in the Shamoon malcode on Aug. 15.

Just who is behind the attacks remains a mystery, with some fingerpointing at nation/state-sponsored Iranian hacktivists, possibly with some insider help.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32606
PUBLISHED: 2021-05-11
In the Linux kernel 5.11 through 5.12.2, isotp_setsockopt in net/can/isotp.c allows privilege escalation to root by leveraging a use-after-free. (This does not affect earlier versions that lack CAN ISOTP SF_BROADCAST support.)
CVE-2021-3504
PUBLISHED: 2021-05-11
A flaw was found in the hivex library in versions before 1.3.20. It is caused due to a lack of bounds check within the hivex_open function. An attacker could input a specially crafted Windows Registry (hive) file which would cause hivex to read memory beyond its normal bounds or cause the program to...
CVE-2021-20309
PUBLISHED: 2021-05-11
A flaw was found in ImageMagick in versions before 7.0.11 and before 6.9.12, where a division by zero in WaveImage() of MagickCore/visual-effects.c may trigger undefined behavior via a crafted image file submitted to an application using ImageMagick. The highest threat from this vulnerability is to ...
CVE-2021-20310
PUBLISHED: 2021-05-11
A flaw was found in ImageMagick in versions before 7.0.11, where a division by zero ConvertXYZToJzazbz() of MagickCore/colorspace.c may trigger undefined behavior via a crafted image file that is submitted by an attacker and processed by an application using ImageMagick. The highest threat from this...
CVE-2021-20311
PUBLISHED: 2021-05-11
A flaw was found in ImageMagick in versions before 7.0.11, where a division by zero in sRGBTransformImage() in the MagickCore/colorspace.c may trigger undefined behavior via a crafted image file that is submitted by an attacker processed by an application using ImageMagick. The highest threat from t...