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.

Perimeter

6/14/2019
09:10 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Triton Attackers Seen Scanning US Power Grid Networks

The development follows speculation and concern among security experts that the attack group would expand its scope to the power grid.

The attackers behind the epic Triton/Trisis attack that in 2017 targeted and shut down a physical safety instrumentation system at a petrochemical plant in Saudi Arabia now have been discovered probing the networks of dozens of US and Asia-Pacific electric utilities.

Industrial-control system (ICS) security firm Dragos, which calls the attack group XENOTIME, says the attackers actually began scanning electric utility networks in the US and Asia-Pacific regions in late 2018 using similar tools and methods the attackers have used in targeting oil and gas companies in the Middle East and North America.

The findings follow speculation and concern among security experts that the Triton group would expand its scope into the power grid. To date, the only publicly known successful attack was that of the Saudi Arabian plant in 2017. In that attack, the Triton/Trisis malware was discovered embedded in a Schneider Electric customer's safety system controller. The attack could have been catastrophic, but an apparent misstep by the attackers inadvertently shut down the Schneider Triconex Emergency Shut Down (ESD) system.

Dragos said in a report published today that there's no evidence at this point that XENOTIME could actually wage a cyberattack that would result in "a prolonged disruptive or destructive event on electric utility operations," but that the hacking group's newly discovered activity around power grid providers is concerning. 

"XENOTIME, the most dangerous cyberthreat in the world, provides a prime example of threat proliferation in ICS. What was once considered an 'oil and gas threat' is now an electric threat, too," says Sergio Caltagirone, vice president of threat intelligence at Dragos. "Dragos expects this overlapping targeting will continue across sectors, from power, to water, to manufacturing, and more."

FireEye Mandiant earlier this year revealed that it discovered the Triton/Trisis attack code installed at an industrial organization, marking the first publicly revealed attack by the Triton/Trisis group since the original incident at the Saudia Arabian plant. FireEye analysts found a set of custom Triton/Trisis tools tied to this second victim's organization and the attackers inside the victim's corporate IT network. They declined to reveal the identity of the victim organization.

Meanwhile, the Triton/XENOTIME group in 2018 also compromised several ICS vendors, raising concerns of them waging supply chain-style attacks.

Related Content:

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/20/2019 | 5:53:13 PM
Triton Attack Comment
My question is why don't we have a ICS group that looks into all of the security issues associated with the US to come up with viable solutions like:

-> Blocking overseas addresses at the ISP layer

-> Create a security dashboard where threat intelligence is shared amoung energy companies, this prescriptive procedure allows organizations who are on the grid to keep ahead of the game especially when actors attack a specific site and they can view the remedy on how to thwart the attack

-> Utilize IPv6 as a way to communicate over the web using IPSec AES256 ESP/AH tunnels

-> Work with IBM and Deep Learning to identify the vulnerabilities in real-time (machine learning at the highest level)

-> Take the best of all Hardened linux machines and create a parallel processing OS that uses docker containers for application level processing where changes are made within a specific time period

-> Simultaneous authorization - Keys are unclocked by two people (similar to nuclear authorization)

-> Distributed NMS network is used to monitor traffic and external communication, anything not on the grid, it gets blocked

-> IP address range limited to devices that are allowed on the network (IPv6 only), only external power companies are able to communicate with the grid and their location is verified by GPS tracking system, if the object moves (routers/switches/firewalls, then someone is notified).

-> Cloud is used as a backup and/or DR resource if the onsite system is compromised, the command and control of the ICS environment can be moved to the cloud (direct connect to multiple CSP - Cloud Service Providers).

-> System recovery should be done in minutes instead of hours

By the way, Schneider Electric was the company who reported on it, AIM Triton overflow was affected

A Windows resolution to address it would be to run the following (complete analysis - https://bit.ly/2XeECIS)
Write-Host " "
Write-Host "Block Triton ICS Port 39929"
Write-Host "---------------------------"

$Name = "Triton-ICS-Attack-Port-UDP-39929"
$Triton = (Get-NetFirewallRule -DisplayName $Name)
$TPort = (Get-NetFirewallrule -DisplayName $Name | Get-NetFirewallPortFilter).LocalPort
if ( ( ($Triton).DisplayName -eq $Name) -And ($TPort -eq 39929) ) {
    Write-Host $Name "exists - ok"
} else {
    New-Netfirewallrule -Action Block -Enabled True -Direction Inbound -LocalPort 39929 \n
-RemoteAddress Localsubnet -Name $Name -Profile Any -Protocol UDP \n
-DisplayName $Name -RemotePort 1502 -Description "Triton-ICS-Attack-Port-39929" Get-NetFirewallRule -Name $Name }


Block Triton ICS Port 39929
-------------------------------
Triton-ICS-Attack-Port-UDP-39929 exists - ok

Linux Perspective:

iptables -I INPUT 1 -p UDP -m multiport -d 192.168.0.0/16 -s 0.0.0.0/0 --dport 39929 --sport 1502 -m conntrack --ctstate NEW,RELATED,ESTABLISHED -j DROP

or

ufw deny in proto udp from 0.0.0.0/0 port 1502 to 192.168.0.0/16 port 39929 comment "Triton Attack UDP 1502 and 39929" (this is an ex., the default network could on the 172.16 or 10. Network)

Todd
Aviation Faces Increasing Cybersecurity Scrutiny
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/22/2019
Microsoft Tops Phishers' Favorite Brands as Facebook Spikes
Kelly Sheridan, Staff Editor, Dark Reading,  8/22/2019
Capital One Breach: What Security Teams Can Do Now
Dr. Richard Gold, Head of Security Engineering at Digital Shadows,  8/23/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-15540
PUBLISHED: 2019-08-25
filters/filter-cso/filter-stream.c in the CSO filter in libMirage 3.2.2 in CDemu does not validate the part size, triggering a heap-based buffer overflow that can lead to root access by a local Linux user.
CVE-2019-15538
PUBLISHED: 2019-08-25
An issue was discovered in xfs_setattr_nonsize in fs/xfs/xfs_iops.c in the Linux kernel through 5.2.9. XFS partially wedges when a chgrp fails on account of being out of disk quota. xfs_setattr_nonsize is failing to unlock the ILOCK after the xfs_qm_vop_chown_reserve call fails. This is primarily a ...
CVE-2016-6154
PUBLISHED: 2019-08-23
The authentication applet in Watchguard Fireware 11.11 Operating System has reflected XSS (this can also cause an open redirect).
CVE-2019-5594
PUBLISHED: 2019-08-23
An Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") in Fortinet FortiNAC 8.3.0 to 8.3.6 and 8.5.0 admin webUI may allow an unauthenticated attacker to perform a reflected XSS attack via the search field in the webUI.
CVE-2019-6695
PUBLISHED: 2019-08-23
Lack of root file system integrity checking in Fortinet FortiManager VM application images of all versions below 6.2.1 may allow an attacker to implant third-party programs by recreating the image through specific methods.