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.

Attacks/Breaches

12/7/2018
04:30 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Criminals Use Locally Connected Devices to Attack, Loot Banks

Tens of millions of dollars stolen from at least eight banks in East Europe, Kasperksy Lab says.

Attackers, likely working for the same threat group, have looted tens of millions of dollars from at least eight banks in Eastern Europe after gaining initial access to their networks via devices connected directly to a local network.

In some cases, the attackers planted the devices at the banking institution's central office. In others, they were planted in a regional office or even an office in another country, Kaspersky Lab said in a report this week.

They then used the initial foothold to move deeper into the target organization's network, finding and manipulating systems in order to withdraw millions of dollars using ATMs and other services.

The "DarkVishnya" campaign, as Kaspersky Lab has named it, was a series of attacks on financial institutions, says Sergey Golovanov, security researcher at Kaspersky Lab. "What they all had in common was the use of a physical device that was connected to the local network and later scanned in order to access open resources," he says.

The attacks are another reminder that network perimeter defenses alone are not enough, Golovanov notes. "Cybercriminals can connect to the network leaving no trace and no logs in networking gear," he says.

In its report, Kaspersky Lab described the devices used in the DarkVishnya attacks as one of three types: a notebook or cheap laptop, a Raspberry Pi computer, or Bash Bunny, a Linux-based tool that can be plugged into a target computer's USB port to execute malicious payloads.

With each attack, the cybercriminals gained initial access to their target organization's building by pretending to be a courier, job seeker, or some other guise. They then connected their rogue devices to the banks' local networks in meeting rooms or to tables with built-in network sockets.

Each of the planted devices was remote-access-enabled via a built-in or USB-connected modem. The device would show up on the local network as an unknown computer, an external flash drive, or a keyboard. But finding it was hard because the device would typically be hidden or installed in a manner to blend in with the surroundings, Kaspersky Lab said in its report.

The attackers then remotely accessed their rogue devices and used them to scan the network for publicly accessible folders, Web servers, and other open resources. The main goal was to gather as much information as possible on servers and workstations used for making payments.  

Once the attackers discovered such systems, they tried brute-forcing their way in or finding data for logging into the systems using legitimate credentials.

"When a malicious program was installed on one of the computers, this program would not connect to external IP addresses belonging to the threat actors," Golovanov says. Instead, it would open a local TCP-port and let criminals connect to it, he says.

In situations where a firewall prevented the technique from working, the attackers would "use a server of one of the local computers on the network that already had permission to access the target system through the firewall," he says. "So some computers had local ports open, and some computers just had IP addresses of computers from the corporate network, not threat actors' external IP addresses."

Kaspersky Lab researchers estimate that the target banks suffered millions of dollars in direct losses from the attack via fraudulent ATM withdrawals and other services that provide banking clients with funds.

Golovanov says that while the attacks were identical and involved the same kind of rogue devices, Kaspersky Lab is currently not making any claims about the potential identity of the threat actors behind DarkVishnya.

Related Content:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RxVge02U
50%
50%
RxVge02U,
User Rank: Apprentice
12/10/2018 | 5:48:21 AM
Samish Leather

Thanks for sharing your thoughts and ideas on this one. Please keep posting about such articles as they really spread useful information. Dwayne Jhonson Christmas

 

Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
Architectural Analysis IDs 78 Specific Risks in Machine-Learning Systems
Jai Vijayan, Contributing Writer,  2/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9308
PUBLISHED: 2020-02-20
archive_read_support_format_rar5.c in libarchive before 3.4.2 attempts to unpack a RAR5 file with an invalid or corrupted header (such as a header size of zero), leading to a SIGSEGV or possibly unspecified other impact.
CVE-2019-20479
PUBLISHED: 2020-02-20
A flaw was found in mod_auth_openidc before version 2.4.1. An open redirect issue exists in URLs with a slash and backslash at the beginning.
CVE-2011-2498
PUBLISHED: 2020-02-20
The Linux kernel from v2.3.36 before v2.6.39 allows local unprivileged users to cause a denial of service (memory consumption) by triggering creation of PTE pages.
CVE-2012-2629
PUBLISHED: 2020-02-20
Multiple cross-site request forgery (CSRF) and cross-site scripting (XSS) vulnerabilities in Axous 1.1.1 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) add an administrator account via an addnew action to admin/administrators_add.php; or (2) c...
CVE-2014-3484
PUBLISHED: 2020-02-20
Multiple stack-based buffer overflows in the __dn_expand function in network/dn_expand.c in musl libc 1.1x before 1.1.2 and 0.9.13 through 1.0.3 allow remote attackers to (1) have unspecified impact via an invalid name length in a DNS response or (2) cause a denial of service (crash) via an invalid ...