Triton Safety Instrumented System Attack was a campaign employed by TEMP.Veles which leveraged the Triton malware framework against a petrochemical organization.[1] The malware and techniques used within this campaign targeted specific Triconex Safety Controllers within the environment.[2] The incident was eventually discovered due to a safety trip that occurred as a result of an issue in the malware.[3]
ID | Name | Description |
---|---|---|
G0088 | TEMP.Veles |
Domain | ID | Name | Use | |
---|---|---|---|---|
Enterprise | T1595 | Active Scanning |
In the Triton Safety Instrumented System Attack, TEMP.Veles engaged in network reconnaissance against targets of interest.[4] |
|
Enterprise | T1059 | .001 | Command and Scripting Interpreter: PowerShell |
In the Triton Safety Instrumented System Attack, TEMP.Veles used a publicly available PowerShell-based tool, WMImplant.[4] |
Enterprise | T1587 | .001 | Develop Capabilities: Malware |
In the Triton Safety Instrumented System Attack, TEMP.Veles developed, prior to the attack, malware capabilities that would require access to specific and specialized hardware and software.[5] |
Enterprise | T1573 | Encrypted Channel |
In the Triton Safety Instrumented System Attack, TEMP.Veles used cryptcat binaries to encrypt their traffic.[4] |
|
Enterprise | T1056 | .003 | Input Capture: Web Portal Capture |
In the Triton Safety Instrumented System Attack, TEMP.Veles captured credentials as they were being changed by redirecting text-based login codes to websites they controlled.[1] |
Enterprise | T1036 | .005 | Masquerading: Match Legitimate Name or Location |
In the Triton Safety Instrumented System Attack, TEMP.Veles renamed files to look like legitimate files, such as Windows update files or Schneider Electric application files. |
Enterprise | T1027 | .005 | Obfuscated Files or Information: Indicator Removal from Tools |
In the Triton Safety Instrumented System Attack, TEMP.Veles modified files based on the open-source project cryptcat in an apparent attempt to decrease anti-virus detection rates.[4] |
Enterprise | T1588 | .002 | Obtain Capabilities: Tool |
In the Triton Safety Instrumented System Attack, TEMP.Veles used tools such as Mimikatz and other open-source software.[4] |
Enterprise | T1003 | .001 | OS Credential Dumping: LSASS Memory |
In the Triton Safety Instrumented System Attack, TEMP.Veles used Mimikatz.[2] |
Enterprise | T1053 | .005 | Scheduled Task/Job: Scheduled Task |
In the Triton Safety Instrumented System Attack, TEMP.Veles installed scheduled tasks defined in XML files.[4] |
ICS | T0830 | Adversary-in-the-Middle |
In the Triton Safety Instrumented System Attack, TEMP.Veles changed phone numbers tied to certain specific accounts in a designated contact list. They then used the changed phone numbers to redirect network traffic to websites controlled by them, thereby allowing them to capture and use any login codes sent to the devices via text message.[1] |
|
ICS | T0807 | Command-Line Interface |
In the Triton Safety Instrumented System Attack, TEMP.Veles’ tool took one option from the command line, which was a single IP address of the target Triconex device.[5] |
|
ICS | T0872 | Indicator Removal on Host |
In the Triton Safety Instrumented System Attack, TEMP.Veles would programmatically return the controller to a normal running state if the Triton malware failed. If the controller could not recover in a defined time window, TEMP.Veles programmatically overwrote their malicious program with invalid data.[5] |
|
ICS | T0867 | Lateral Tool Transfer |
In the Triton Safety Instrumented System Attack, TEMP.Veles made attempts on multiple victim machines to transfer and execute the WMImplant tool.[4] |
|
ICS | T0828 | Loss of Productivity and Revenue |
In the Triton Safety Instrumented System Attack, TEMP.Veles tripped a controller into a failed safe state, which caused an automatic shutdown of the plant, this resulted in a pause of plant operations for more than a week. Thereby impacting industrial processes and halting productivity.[5] |
|
ICS | T0843 | Program Download |
In the Triton Safety Instrumented System Attack, TEMP.Veles downloaded multiple rounds of control logic to the Safety Instrumented System (SIS) controllers through a program append operation.[5] |
|
ICS | T0886 | Remote Services |
In the Triton Safety Instrumented System Attack, TEMP.Veles utilized remote desktop protocol (RDP) jump boxes, poorly configured OT firewalls [1], along with other traditional malware backdoors, to move into the ICS environment.[2][1] |
|
ICS | T0853 | Scripting |
In the Triton Safety Instrumented System Attack, TEMP.Veles used a publicly available PowerShell-based tool, WMImplant.[4] |
|
ICS | T0855 | Unauthorized Command Message |
In the Triton Safety Instrumented System Attack, TEMP.Veles leveraged Triton to send unauthorized command messages to the Triconex safety controllers.[2] |
|
ICS | T0859 | Valid Accounts |
In the Triton Safety Instrumented System Attack, TEMP.Veles used valid credentials when laterally moving through RDP jump boxes into the ICS environment.[2] |
ID | Name | Description |
---|---|---|
S0002 | Mimikatz | |
S1009 | Triton |
TEMP.Veles leveraged Triton to interact and disrupt Triconex safety instrumented systems throughout this campaign.[4][2][5] |