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.

Risk

Malware Corrupts Iranian Financial Databases

Iran downplays threat of Narilam financial malware, saying it dates from 2009 to 2010, and doesn't bear comparisons to Stuxnet, Duqu or Flame.

Who Is Hacking U.S. Banks? 8 Facts
Who Is Hacking U.S. Banks? 8 Facts
(click image for larger view and for slideshow)
Symantec is warning that financial malware, dubbed Narilam, is actively targeting financial applications primarily used in Iran.

"In the last couple of years, we have seen highly sophisticated malware used to sabotage the business activities of chosen targets," said Symantec's advisory, released Thursday. "We have seen malware such as W32.Stuxnet designed to tamper with industrial automation systems, and other destructive examples such as W32.Disstrack and W32.Flamer, which can both wiped (sic) out data and files from hard disks. All of these threats can badly disrupt the activities of those affected.

"Following along that theme, we recently came across an interesting threat that has another method of causing chaos, this time, by targeting and modifying corporate databases," said Symantec, noting that the threat has been dubbed Narilam.

[ Read Was U.S. Government's Stuxnet Brag A Mistake? ]

"The threat copies itself to the infected machine, adds registry keys, and spreads through removable drives and network shares. It is even written using Delphi, which is a language that is used to create a lot of other malware threats," said Symantec. The malware also can update Microsoft SQL databases -- for example, to overwrite information stored therein.

In response to Symantec's warning, Iran's Computer Emergency Readiness Team (CERT) Sunday released an advisory confirming that the Narilam malware had targeted Iranian systems. But it downplayed the threat, and suggested that any comparisons to "the previously reported cyber-attacks on Iran's infrastructure like stuxnet, duqu and flame" vastly overstated the malware's capabilities.

"The malware called 'narilam' by Symantec was an old malware, previously detected and reported online in 2010 by some other names," said the Iranian CERT's advisory. "This malware has no sign of a major threat, nor a sophisticated piece of computer malware ... and is only able to corrupt the database of some of the products by an Iranian software company, those products are accounting software for small businesses. The simple nature of the malware looks more like a try to harm the software company reputation among their customers."

Iran's CERT did, however, suggest that all users of the accounting software ensured that they were backing up all related databases, and regularly scanning their systems using antivirus tools.

Narilam's target, according to Kaspersky Lab, is three financial applications by Iranian software development firm TarrahSystem. After Narilam was spotted in the wild, TarrahSystem released an advisory in June 2010 warning that newly discovered malware was targeting Maliran, its integrated financial and industrial applications; Amin, its banking and loans software; and Shahd ("Nectar"), integrated financial/commercial software.

Despite the Iran CERT's statement, could the existence of malware that targets Iranian financial information reveal another cyber-espionage campaign along the lines of Stuxnet, Duqu, Flame or Gauss, which were apparently commissioned by the United States? Gauss, for example, primarily targeted a small number of Lebanese banking customers. Security experts believe the malware was used, at least in part, to track suspected money-laundering operations involving the Lebanese militant group and political party Hezbollah.

In fact, most malware today is designed to steal financial information. As a result, Narilam appears to be simply run-of-the-mill financial malware -- along the lines of Blackhole, Citadel, Crisis, SpyEye, or Zeus, although likely less functional.

Narilam today also doesn't seem to rate as a big threat. "According to Kaspersky Security Network, there are very few reports of this malware at the moment, which means it's probably almost extinct," according to research published by Kaspersky Lab. "The earliest report of the malware is from August 2010; in total about 80 incidents have been recorded during past two years." It said that related infections affected users in Iran (60%) and Afghanistan (40%), but noted that Kaspersky has only seen six related infections in the past month.

Based on a review of how the code was built, Kaspersky Lab sees no connection between Narilam and destructive malware -- namely, Shamoon or Wiper. Furthermore, the malware has no cyber-espionage capabilities, and shares no developmental commonalities with well-known cyber-espionage tools. "Duqu, Stuxnet, Flame and Gauss have all been compiled with versions of Microsoft Visual C, while Narilam was built with Borland C++ Builder 6 (and not Delphi, as other articles seem to suggest), a completely different programming tool," said Kaspersky Lab.

Recent breaches have tarnished digital certificates, the Web security technology. The new, all-digital Digital Certificates issue of Dark Reading gives five reasons to keep it going. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
PJS880
PJS880,
User Rank: Ninja
12/10/2012 | 4:10:22 PM
re: Malware Corrupts Iranian Financial Databases
Of course Iranian officials are going to downplay the threat, they do not want to appear weak to the general public, or to the threats which I am sure area ware of the damage they can cause. The actual software does sound like it could do some serious damage as far as corrupting and overwriting the database that exists currently. Would Iran admit that their systems have been compromised, if they did not have to?

Paul Sprague
InformationWeek Contributor
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
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-2022-31650
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a.
CVE-2022-31651
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is an assertion failure in rate_init in rate.c in libsox.a.
CVE-2022-29256
PUBLISHED: 2022-05-25
sharp is an application for Node.js image processing. Prior to version 0.30.5, there is a possible vulnerability in logic that is run only at `npm install` time when installing versions of `sharp` prior to the latest v0.30.5. If an attacker has the ability to set the value of the `PKG_CONFIG_PATH` e...
CVE-2022-26067
PUBLISHED: 2022-05-25
An information disclosure vulnerability exists in the OAS Engine SecureTransferFiles functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to arbitrary file read. An attacker can send a sequence of requests to trigger this vulnera...
CVE-2022-26077
PUBLISHED: 2022-05-25
A cleartext transmission of sensitive information vulnerability exists in the OAS Engine configuration communications functionality of Open Automation Software OAS Platform V16.00.0112. A targeted network sniffing attack can lead to a disclosure of sensitive information. An attacker can sniff networ...