Hunter-Case-05 - Velociraptor tool abused for remote access
- Velociraptor incident response tool abused for remote access
1.) Information
Hunter Blue's day started everyday with researching the cyber security news for new Threat Huntings tasks to execute them on customer datalakes.
-> Interesting report from Sophos covering malicious Velociraptor use https://news.sophos.com/en-us/2025/08/26/velociraptor-incident-response-tool-abused-for-remote-access/
Checking out this msi:
they used Velociraptor version 0.73.4.
Server likley installed on ~04/08/2025 10:03:15 (self signed certificate)
As the article suggested unexpected processes communicating to workers\.dev would detect this particular instance.
Matthew Green created a Velociraptor inception artifact a while ago to find unauthorised instances that uses yara and other methods https://github.com/rapid7/Rapid7-Labs/blob/main/Vql/VelociraptorInception.yaml
You should investigate the initial Entry and Execution to search through the logs with these IoCs / IoAs to find the right artifacts for Threat Hunting.
1.1) Information Links and Research
Affected Component: Velociraptor Investigation Tool
Root Cause: deployment of the legitimate open-source Velociraptor digital forensics and incident response (DFIR) tool
Exploitation: used the tool to download and execute Visual Studio Code with the likely intention of creating a tunnel to an attacker-controlled command and control (C2) server
2.) Indicators of Compromise
2.1) Executions from Threat Actor - Steps
tool to download and execute Visual Studio Code with the likely intention
creating a tunnel to an attacker-controlled command and control (C2) server. Enabling the tunnel option in Visual Studio Code
Windows msiexec utility to download an installer (v2.msi) from a Cloudflare Workers domain (files[.]qaubctgg[.]workers[.]dev)
staging folder for attacker tools, including the Cloudflare tunneling tool and the Radmin remote administration tool
file installed Velociraptor, which is configured to communicate with C2 server velo[.]qaubctgg[.]workers[.]dev
encoded PowerShell command to download Visual Studio Code (code.exe) from the same staging folder and executed it with the tunnel option enabled.
installed code.exe as a service and redirected the output to a log file
msiexec Windows utility again to download additional malware (sc.msi) from the workers[.]dev folder
2.2) Indicators of Compromise - Executions
3.) Initial Access
Threat actors often abuse remote monitoring and management (RMM) tools. In some instances, they leverage preexisting tools on the targeted systems.
They used the tool to download and execute Visual Studio Code with the likely intention of creating a tunnel to an attacker-controlled command and control (C2) server
4.) Finding through Threat Hunting
We hunted through the Datalake logs in the whole infrastructure...
5.) Mitigation
To mitigate exposure to this malware, organizations use available controls to review and restrict access using the indicators listed in Table 1. The domains may contain malicious content, so consider the risks before opening them in a browser.
Indicator
Type
Context
files[.]qaubctgg[.]workers[.]dev
Domain name
Hosted tools used in August 2025 Velociraptor campaign
velo[.]qaubctgg[.]workers[.]dev
Domain name
C2 server used in August 2025 Velociraptor campaig
Table 1
6.) Detection and Hunting
6.1) Sigma Rules
6.2) Linux Commandline Hunting
6.3) Hunting Queries Microsoft Defender XDR
6.4) Hunting Queries Palo Cortex XDR
6.5) Hunting Queries Tanium EDR
7.) Conclusion and Learning for a Hunter Blue
The Velociraptor incident reveals attackers pivoting to using incident response tools to gain a foothold in a network and minimize the amount of malware they deploy
its definitely necessary to check during Hunting or Initial Triage how Malware was staged
-> showcasing how fruitful Compromise Assessment Hunting and Time Line Analysis can be and should be used in such cases -> it is essential.
Last updated