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

12/18/2012
09:49 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Data-Destruction Attack Targeted 'Few' Select Iranian Computers

'Simplistic' data-destroying malware found on small number of targeted computers in Iran

It's no Stuxnet or Wiper, but the latest data-destroying malware targeting specific computers in Iran still wreaks some serious damage.

Iran's CERT on Sunday first issued an alert about the relatively rudimentary malware, which was discovered to delete data off of various drives at specific times and dates. The malware is a "very simple" knockoff of other wiping malware with no relation to those previously discovered malware attacks, and "very few machines" were infected by it, according to the CERT.

Researchers from Symantec, Kaspersky Lab, AlienVault Labs, and SophosLabs all have studied a sample of the malware, a.k.a. Batchwiper or GrooveMonitor. They concur that it's a simplistic yet lethal piece of malware that doesn't appear to be related to the nation-state built Stuxnet and Wiper that hit Iran's nuclear facility, or the destructive Shamoon that wiped 30,000 workstations of their data at Saudi Aramco, and deleted files at the Iranian oil ministry.

It's the latest in a series of data-destroying malware attacks targeting specific organizations in the Middle East. This return to 1980s and early-'90s malware that damages or deletes data puzzles researchers. "It's not the kind of thing you'd expect a nation-state [to create]," says Chester Wisniewski, a senior security adviser for Sophos.

He says it's odd that Iran sounded the alarm about such an unsophisticated attack. "This [malware] is something anybody could have done," he says.

Batchwiper/GrooveMonitor uses a DOS BAT file that was converted to a Windows Portable executable file. It wipes data off of drivers lettered D through I, as well as files on the user's desktop, and is set to do its dirty deed during specific dates, including between Dec. 10 and 12, and Jan. 21 and 23, as well as various dates that run through 2015.

"That's not something we see almost ever," Wisniewski says. "It's one of the few things that suggests that it's a targeted attack. It's very weird: Why would you care if it's Dec. 12? What those dates mean is a mystery."

The author of the malware even made an obvious typo in the code that prevents one feature from functioning. SophosLabs found a second variant of the malware, but it's still the same basic code.

Kaspersky Lab also saw an error in the code. "Other than the geographic region there doesn't seem to be any commonality with this file-deleting malware and the previous attacks we've seen. Even though the code is extremely simplistic it looks like the author managed to slip in a mistake, by not deleting a line of old code," says Roel Schouwenberg, senior researcher for global research and analysis at Kaspersky Lab, in a blog post.

Just how it spread is unclear. Jaime Blasco, labs manager at AlienVault Labs, thinks it may be via USB. "We don’t have details about the infection vector but based on the dropper it could be deployed using USB drives, internal actors, SpearPhishing or probably as the second stage of a targeted intrusion," Blasco says in a blog post.

The Iranian CERT initially reported that the malware was efficient yet simple, and was wiping out disk partitions and user profile directories without being detected by antivirus software.

"This is as basic as it gets. But if it was effective, that doesn't matter. If it wasn't clear already -- the era of cybersabotage has arrived. Be prepared," Schouwenberg says.

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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/27/2020
10 iOS Security Tips to Lock Down Your iPhone
Kelly Sheridan, Staff Editor, Dark Reading,  5/22/2020
How an Industry Consortium Can Reinvent Security Solution Testing
Henry Harrison, Co-founder & Chief Technology Officer, Garrison,  5/21/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13632
PUBLISHED: 2020-05-27
ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.
CVE-2020-13253
PUBLISHED: 2020-05-27
sd_wp_addr in hw/sd/sd.c in QEMU 4.2.0 uses an unvalidated address, which leads to an out-of-bounds read during sdhci_write() operations. A guest OS user can crash the QEMU process.
CVE-2020-13630
PUBLISHED: 2020-05-27
ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.
CVE-2020-13631
PUBLISHED: 2020-05-27
SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.
CVE-2020-4226
PUBLISHED: 2020-05-27
IBM MobileFirst Platform Foundation 8.0.0.0 stores highly sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 175207.