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
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 the Executive Editor of Dark Reading. 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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest 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
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-30477
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of replies to messages sent by outgoing webhooks to private streams meant that an outgoing webhook bot could be used to send messages to private streams that the user was not intended to be able to send messages to.
CVE-2021-30478
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the can_forge_sender permission (previously is_api_super_user) resulted in users with this permission being able to send messages appearing as if sent by a system bot, including to other organizations hosted by the sa...
CVE-2021-30479
PUBLISHED: 2021-04-15
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the all_public_streams API feature resulted in guest users being able to receive message traffic to public streams that should have been only accessible to members of the organization.
CVE-2021-30487
PUBLISHED: 2021-04-15
In the topic moving API in Zulip Server 3.x before 3.4, organization administrators were able to move messages to streams in other organizations hosted by the same Zulip installation.
CVE-2020-36288
PUBLISHED: 2021-04-15
The issue navigation and search view in Jira Server and Data Center before version 8.5.12, from version 8.6.0 before version 8.13.4, and from version 8.14.0 before version 8.15.1 allows remote attackers to inject arbitrary HTML or JavaScript via a DOM Cross-Site Scripting (XSS) vulnerability caused ...