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

checkLoop 1checkLoop 2checkLoop 3
12/18/2015
10:30 AM
Uri Rivner
Uri Rivner
Commentary
Connect Directly
Facebook
Twitter
LinkedIn
Google+
RSS
E-Mail vvv
50%
50%

When RATs Become a Social Engineer’s Best Friend

Hacking humans in the banking industry through rogue help desks is becoming a significant problem.

Jane, the senior fraud analyst in a top-tier bank, was looking at the latest series of reported online banking fraud cases and shook her head. This can’t be right, she decided. The fraudulent money transfer was coming from the victim’s device, which normally indicates some sort of Trojan-induced Man-in-the-Browser (MITB) attack designed to defeat device recognition and geo-location analysis. But these MITB attacks are normally picked up by the state-of-the-art malware detection service used by the bank.

She looked at the list of alerts and double-checked. There was nothing there. Was it some sort of new Trojan that went undetected by the system? If so, the Trojan operators must have known they have safe passage; they spent a long time in the account, and the money transfer they made was enormous. It’s as if they knew it wouldn’t be detected by any of the existing lines of defense. 

They were right about that, Jane thought, and picked up the phone to call the Internet user who reported the fraud. The story she heard made her realize she was facing something totally new… 

Remote Administration Tools, or RATs, started as completely harmless remote support tools, the kind that a help desk would use to support users whose PC needed attention. In fact, every major operating system, including mobile ones, have remote access protocols embedded in the OS level. But while RATs are a relatively new entrant in the growing arsenal of tools available to online banking fraudsters, state-sponsored hackers have been using them for a long time. Since 2009, wave after wave of Advanced Persistent Threats (APT) campaigns used spear phishing to install RATs on employee machines in thousands of corporations worldwide. These attacks create invisible tunnels that allow an outsider to completely control a victim’s device from anywhere. 

RAT capabilities based on VNC back-connect later appeared as a new feature in advanced banking Trojans such as Citadel, as well as a hoard of next-generation Zeus clones. The fraudsters learned from government hackers that RATs are an extremely powerful weapon, allowing attackers to not only harvest information or run automated scripts in browsers, but to actually gain full remote control of a device, and access a victim’s bank account from their own machine. 

Today, RATs are a popular tool commonly used by cybercriminals. Dyre is currently the most widespread Trojan that uses RAT; Dridex, whose operation was recently disrupted by law enforcement, was also heavily using a RAT capability. Other Trojans include Neverquest, Shifu and many Zeus clones that feature VNC functionality with back-connect. Recently, there has been a spinoff of these RAT attacks: Social RATs.

In this rapidly growing social engineering attack, the victim gets a phone call from someone claiming to be from their bank, internet provider, or other trusted third party. The fraudster then gets the victim to download a commercially available remote administration tool, such as TeamViewer, in order to help fix the “problem”. 

Providing a rogue help desk with remote access rights into your PC is not something most readers of this article would do, but good social engineering is, at times, extremely convincing and effective. The banking industry is particularly vulnerable due to its lack of effective fraud detection for remote access attacks.

After the RAT is installed?

While on the phone, attackers instruct victims to go through “security checks” to verify the safety of their accounts by logging into their bank accounts. Even after victims believe themselves to be logged out, an attacker can linger undetected. Part of the reason banks are experiencing a growing number of socially engineered attacks is because they are cheap to execute and offer a huge payoff to attackers; with limited technological training, attackers can send a quick email, or briefly chat over the phone, and access someone’s entire life savings.

A similar problem exists in corporate banking. From a regulatory perspective, there are no requirements for a bank to make a business customer whole if it lost money due to fraud. However, publicity surrounding large fraud cases has made many banks realize that while they do not have the obligation to do so, making customers confident in their online banking usage is in their best interest.

Social RAT attacks stretch this dilemma even further: first, they involve higher-than-usual monetary losses, and second, falling victim to a ploy in which you end up granting someone remote control over your device is viewed by many banks as crossing the line from naiveté to gross negligence. This spells trouble for business banking, as it could set a dangerous precedent where trust between banks and their customers erode quickly.

Two factors contribute to the success of rogue help desk RAT campaigns. First, users are familiar with the concept of help desks that ask permission to take over their device. So, given the right social engineering, they’ll be susceptible to manipulation. The second issue: existing security controls do not detect RATs. 

To help close the gaps, banks can protect themselves by educating customers about social engineering threats. Users should be encouraged to refuse unsolicited help and contact their banks or other financial institutions if they receive suspicious emails, text messages or phone calls.  Moreover, customers should be made aware of ways they can verify conversations with customer service representatives.

Uri Rivner, Co-Founder and Head of Cyber Strategy at BioCatch is recognized globally as an industry expert on cybercrime and advanced threats. He is a regular speaker in the leading security and cyber conferences, and writes a cyber-security blog read by thousands of ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industry’s conventional wisdom. Here’s a look at what they’re thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19777
PUBLISHED: 2019-12-13
stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main.
CVE-2019-19778
PUBLISHED: 2019-12-13
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer over-read in the function load_sixel at loader.c.
CVE-2019-16777
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of pa...
CVE-2019-16775
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would allow a package publi...
CVE-2019-16776
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain...
checkLoop 4