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.

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.

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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...