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.

IoT/Embedded Security //

Botnet

End of Bibblio RCM includes -->
6/7/2018
08:05 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now

VPNFilter Malware Targets More Routers Than Originally Thought

In an update to its research into the VPNFilter botnet malware, Cisco Talos researchers increased the number of routers that were targeted.

The VPNFilter botnet malware, which security researchers discovered last month, targeted many more routers than originally thought, according to new analysis.

In a June 6 blog, researchers at Cisco Talos added several names to the list of home and small-business routers the malware targeted before being shut down by the FBI at the end of May. That list now includes devices from Asus, D-Link, Huawei, Ubiquiti, UPVEL and ZTE.

Originally, researchers and law enforcement found VPNFilter targeted different routers and other devices from Linksys, MikroTik, Netgear and TP-Link. Overall, about 500,000 devices in dozens of countries were suspected of being infected; that number is now likely to go much higher. (See FBI Knocks Out VPNFilter Malware That Infected 500K Routers.)

A full list of all the targeted routers and serial numbers for these devices can be found at the end of Talos' technical analysis of the VPNFilter malware.

A diagram of the VPNFilter botnet malware\r\n(Source: Cisco Talos)
A diagram of the VPNFilter botnet malware
\r\n(Source: Cisco Talos)

First discovered by the Secret Service of Ukraine, and then analyzed by Talos and Symantec, VPNFilter is a sophisticated piece of malware that attempted to create a malicious botnet network from routers and Network Attached Storage (NAS) devices used primarily by small businesses, as well as home consumers.

The malware is a three-stage attack and in order to dismantle it, FBI agents seized control of the domain that housed Stage 1 of the attack. Since then the agency, as well as the Justice Department, has urged anyone using one of the devices listed to reboot and restart their routers. (See FBI Urges Businesses & Consumers to Reboot Routers .)

The US government believes VPNFilter is the work of a Russian-backed group called Sofacy, also known as Fancy Bear or APT28.

In addition to the list of suspected routers, Talos offered some additional details about VPNFilter's structure.


Now entering its fifth year, the 2020 Vision Executive Summit is an exclusive meeting of global CSP executives focused on navigating the disruptive forces at work in telecom today. Join us in Lisbon on December 4-6 to meet with fellow experts as we define the future of next-gen communications and how to make it profitable.

Originally, researchers found a three-stage attack. The first stage reloads the malware after a reboot -- in a normal reboot, this would erase the infection -- making the malware particularly difficult to stop.

The second stage contains the main payload. Stage 3 consists of plugins that work with the second-stage payload. When the FBI seized the domains during its investigation, agents took control of the servers that were part of Stage 1, meaning the malware could not regenerate itself.

The new research found two additional plugins that are part of Stage 3.

The first, called "ssler," can inject malicious content into web traffic that passes through a network device, and then allows an attack to execute a man-in-the-middle attack. According to the blog post:

With this new finding, we can confirm that the threat goes beyond what the actor could do on the network device itself, and extends the threat into the networks that a compromised network device supports.

The second plugin is called "dstr." It offers a kill command that removes all traces of VPNFilter from a device, then renders that device unusable.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2289
PUBLISHED: 2022-07-03
Use After Free in GitHub repository vim/vim prior to 9.0.
CVE-2022-2288
PUBLISHED: 2022-07-03
Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.
CVE-2022-2290
PUBLISHED: 2022-07-03
Cross-site Scripting (XSS) - Reflected in GitHub repository zadam/trilium prior to 0.52.4, 0.53.1-beta.
CVE-2022-2287
PUBLISHED: 2022-07-02
Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.
CVE-2022-34911
PUBLISHED: 2022-07-02
An issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before 1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account creation, when it sets the page title to "Welcome" followed by the username, the usern...