theDocumentId => 747034 FireEye Links Triton Malware to Russian Research ...

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.

Security Management

10/24/2018
09:35 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

FireEye Links Triton Malware to Russian Research Institute

Triton appeared in late 2017, designed to target industrial control systems. Now, FireEye has linked the malware to a Russian research facility.

In late 2017, security researchers from several different security firms first began noticing a new attack against industrial control systems (ICS) that they named Triton. Now FireEye has linked the malware to Russian research facility.

In an October 23 blog post, FireEye details the company's nearly year-long effort to track this particular piece of malware, which seems designed to specifically target Schneider Electric's Triconex Safety Instrumented System (SIS), which control the shutdown mechanisms for large industrial facilities. It's through this association that Triton got its name. (See Schneider Electric Offers Additional Details on Triton Malware.)

FireEye researchers write that they have traced the origins of the malware to the Moscow-based Central Scientific Research Institute of Chemistry and Mechanics, a government-owned research and technical facility.

Central Research Institute of Chemistry and Mechanics in Moscow\r\n(Source: Google Maps via FireEye)\r\n
Central Research Institute of Chemistry and Mechanics in Moscow
\r\n(Source: Google Maps via FireEye)\r\n

The post offers numerous details about the origins of Triton and how it developed at the institute. Researchers were able to link the malware to one specific, although unnamed, person who worked there and the pattern of activity and attacks tended to dovetail with the Moscow time zone.

Specifically, FireEye tracked a strain of malware under the codename TEMP.Veles back to the Moscow facility. However, the researchers were not able to definitively trace the actual attack to the institute -- which goes by the moniker CNIIHM -- but noted that secondary strains of the TEMP.Veles malware were used during the time of the Triton attack.

In addition, some of the work at CNIIHM focuses on critical infrastructure and safety, along with military weapons development, which is the same industry that the malware targeted. As the blog notes:

While we know that TEMP.Veles deployed the TRITON attack framework, we do not have specific evidence to prove that CNIIHM did (or did not) develop the tool. We infer that CNIIHM likely maintains the institutional expertise needed to develop and prototype TRITON based on the institute's self-described mission and other public information.

FireEye also found an IP address -- 87.245.143.140 -- that was registered to CNIIHM and that address was used by the creators of TEMP.Veles for numerous tasks, including monitoring open source coverage of Triton, network reconnaissance, as well as malicious activity that supported the attack.

Heatmap of Triton attacker operating hours\r\n(Source: FireEye)\r\n
Heatmap of Triton attacker operating hours
\r\n(Source: FireEye)\r\n

Other tidbits and details from the report that tie the malware to the Russian facility include:

  • A program database (PDB) path was found that was part of a tested file that contained a string tied to a specific user. This person is believed to be active in Russian information security communities.
  • The unnamed person who appears to have developed the malware was a professor at CNIIHM, according to a now defunct social media profile.
  • Multiple files that use Cyrillic language.

The investigation surrounding the Triton attack and the people behind it is continuing. It's not clear if the malware infected a large number of critical infrastructures throughout the world, although the New York Times tied one attack to a petrochemical plant in Saudi Arabia.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34432
PUBLISHED: 2021-07-27
In Eclipse Mosquitto versions 2.07 and earlier, the server will crash if the client tries to send a PUBLISH packet with topic length = 0.
CVE-2021-20399
PUBLISHED: 2021-07-27
IBM Qradar SIEM 7.3.0 to 7.3.3 Patch 8 and 7.4.0 to 7.4.3 GA is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 196073.
CVE-2021-20562
PUBLISHED: 2021-07-27
IBM Sterling B2B Integrator Standard Edition 5.2.0.0 through 5.2.6.5_3 and 6.1.0.0 through 6.1.0.2 vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclos...
CVE-2020-18428
PUBLISHED: 2021-07-26
tinyexr commit 0.9.5 was discovered to contain an array index error in the tinyexr::SaveEXR component, which can lead to a denial of service (DOS).
CVE-2020-18430
PUBLISHED: 2021-07-26
tinyexr 0.9.5 was discovered to contain an array index error in the tinyexr::DecodeEXRImage component, which can lead to a denial of service (DOS).