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.

Scott Ferguson, Managing Editor, Light Reading

October 24, 2018

3 Min Read

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.

Read more about:

Security Now

About the Author(s)

Scott Ferguson

Managing Editor, Light Reading

Prior to joining Enterprise Cloud News, he was director of audience development for InformationWeek, where he oversaw the publications' newsletters, editorial content, email and content marketing initiatives. Before that, he served as editor-in-chief of eWEEK, overseeing both the website and the print edition of the magazine. For more than a decade, Scott has covered the IT enterprise industry with a focus on cloud computing, datacenter technologies, virtualization, IoT and microprocessors, as well as PCs and mobile. Before covering tech, he was a staff writer at the Asbury Park Press and the Herald News, both located in New Jersey. Scott has degrees in journalism and history from William Paterson University, and is based in Greater New York.

Keep up with the latest cybersecurity threats, newly discovered vulnerabilities, data breach information, and emerging trends. Delivered daily or weekly right to your email inbox.

You May Also Like


More Insights