Exfiltration of data is often, arguably the most important stage in any Red Team engagement. But did you ever realize that one of the most known and exploited infil technique can be abused?
Last updated
Was this helpful?
Last week I got a call from one of my old Red Teamer friend. He was struggling to exfiltrate the data out of an Active Directory network. The proxy was setup to block almost all popular cloud services that could be used to exfiltrate the data.
I asked him, why don't you use your C2 channel for exfiltration, it is surely the most obvious way, right? He had a valid concern of being burnt. Lucky for him, he had hands on keyboard access and this means that he can login into the target machine and perform actions via typing on the keyboard and leveraging the mouse. Learn more about hands-on-keyboard activity.)
I suggested a technique that I used multiple times back in the day, when I used to Red Team for my clients and that's "Exfiltration using Remote Desktop Protocol". A cool, slow and easy technique to exfiltrate data that's often underrated, overlooked and undetected (almost everywhere).
The attack in simple words is:
The attacker has hands on keyboard access to the victim's workstation/server.
The attacker creates a malicious Windows server/workstation on the cloud or hosts it anywhere where it is accessible to the victim machine. This can be typically achieved by creating a malicious Windows server on Public cloud environments.
The attacker connects to the malicious windows server using RDP protocol.
By the very nature of RDP protocol, the attacker will be able to copy data out of the victim machine and safely disconnect.
The attacker connects to the malicious windows server from another location and copies the data into another infrastructure.
A lot of you must already know how the attacks happen. It's a simple copy and paste of data into the specific server.
When creating an RDP connection, using advanced settings, a user can map the drive on a local machine to a remote machine. This can be achieved by using the Local Resources tab > More on the Remote Desktop Connection dialog box.
Firewall
Firewall is arguably one of the easiest ways of detecting this type of exfiltration. While my setup (pfSense) doesn't support streaming of traffic volume, a few handful of firewalls actually report this data and allow for identification of data exfiltration over RDP.
Endpoint Agents (XDR/EDR/Zeek, etc)
During my assessments trying out with multiple popular EDR/XDR products, I have observed that none of these products currently are capable of detecting data exfiltration through this method. While it's possible to detect traffic volume anomaly using Zeek, unavailability of a stable Zeek release for Windows is a challenge.
While identifying traffic volume is a challenge, the instance of connecting to an RDP server itself can easily be detected. If you know a specific user isn't supposed to connect to a server over RDP, that's definitely suspicious.
Sample detection scenarios:
User connects to an RDP server from a public cloud that's not typically associated with their usage pattern?
For instance, the user might connect
This can be a very good tactic to bypass security controls
Interestingly, the situation he's in isn't a rare scenario. Often ransomware operators have hands on keyboard access. So this attack scenario is applicable for companies of all sizes (because Ransomware gangs don't discriminate
