Late last year, a cyberattacker inadvertently shut down operations at a Saudi Arabian petrochemical plant while testing a highly sophisticated malware tool for manipulating its industrial safety systems.
In a new report this week, security vendor FireEye says it is now able to say with near certainty that a Russian government-backed research institute was involved in the attack, though the full extent of its involvement remains somewhat unclear.
The intrusion at the Middle East industrial facility attracted considerable attention for its use of TRITON, one of the few publicly known malware frameworks employed specifically for use against industrial control systems (ICS). TRITON, in fact, remains one of only three known instances of its type of malware. The other two are Stuxnet, which was used to destroy centrifuges at Iran's Natanz nuclear facility in 2010, and Industroyer, deployed in 2016 against Ukraine's power grid.
FireEye says its analysis shows that the Moscow-based Central Scientific Research Institute of Chemistry and Mechanics (CNIIHM) was involved in the activity that led to the deployment of TRITON on a Schneider Electric industrial safety system at the Saudi plant. The malware was designed to manipulate the behavior of the system in such a manner as to trigger conditions that could cause physical damage at the petrochemical plant in the same way Stuxnet did to Iran's nuclear processing facility. The attack came to light because something went awry and triggered an emergency shutdown at the Saudi plant.
FireEye says it has discovered several data points to support its assessment of CNIIHM's involvement in the intrusion with a high degree of confidence.
One of the biggest is an IP address registered to CNIIHM that was used for multiple purposes related to the attack, including network reconnaissance and specific malicious activity tied to TRITON. Another clue is that a lot of the observed malicious behavior occurred during time periods consistent with the Moscow time zone, where CNIIHM is located. Significantly, CNIIHM also has the expertise and skill required to orchestrate and help execute the development and deployment of TRITON.
"The malware they used during the intrusion was being refined in a sort of testing environment that we could observe," says John Hultquist, director intelligence analysis at FireEye. Investigation of that activity shows direct ties to CNIIHM and a particular individual in Moscow with specific connections to the research institute.
One of CNIIHM's roles appears to have been to basically try and refine the malware to a point where it wasn't being caught by antimalware tools at the target organization, Hultquist notes. "While they were testing this stuff, we did see them go back and forth from the testing environment to the target, which basically indicated to us [CNIIHM's involvement]," he says.
There is little doubt that the Russian technical research institute supported the development and subsequent refinement of the TRITON malware, though it is possible that others were involved, as well, Hultquist says. "They were a lot less consistent with operational security and left a lot of artifacts that indicated their involvement," he explains.
While it is theoretically possible that someone within CNIIHM is involved in the TRITON activity without the knowledge or approval of the institute, that seems highly unlikely, FireEye said in its report.
Hultquist says FireEye's research confirms that Russian threat actors have the capability to target ICS systems with malware capable of causing physical damage. "We have seen Russian actors repeatedly demonstrating motive and intent," he says. "They have had a history of carrying out aggressive [cyber] activity." That means organizations have to be prepared.
Dave Weinstein, vice president of threat research at Claroty, says FireEye's report underscores the degree of complexity tied to the TRITON malware framework. Researchers have known for some time that only a highly resourced actor could have pulled off the attack; the FireEye analysis, if accurate, would validate that assumption, he says.
From a geopolitical standpoint, it will be interesting to see how the latest revelations play out, especially given the current relationship between the US and Russia.
For enterprises, this attribution doesn't change much, Weinstein says. "Organizations that operate ICS systems are less interested in the 'who' and more in the 'how' [of an attack]," he says.
Fortunately, for the moment at least, the barriers to entry remain high for those wanting to pull off TRITON-like attacks. And nation-states like Russia that have the ability to develop and execute such attacks are generally bound by some degree of deterrence. "It is not necessarily in the interest of a threat actor to actually execute these tools" given the potential for retaliation, Weinstein says.
- TRITON Attacker Disrupts ICS Operations, While Botching Attempt to Cause Physical Damage
- Schneider Electric: TRITON/TRISIS Attack Used 0-Day Flaw in its Safety Controller System, and a RAT
- FireEye Finds New Clues in TRITON/TRISIS Attack
- 7 Ways Blockchain is Being Used for Security
Black Hat Europe returns to London Dec 3-6 2018 with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.