Back to Intelligence

Dolphin X RAT: Defending Against AI-Driven Victim Profiling and Target Prioritization

SA
Security Arsenal Team
July 23, 2026
7 min read

Introduction

The commoditization of cybercrime continues to evolve with the emergence of "Dolphin X," a new Remote Access Trojan (RAT) advertised on underground forums. Unlike traditional malware that treats every infection as equal, Dolphin X claims to incorporate an AI-powered profiling engine. This module actively scores and ranks infected users based on the value of harvested data—financial records, intellectual property, or authentication tokens.

For defenders, this represents a critical shift in dwell time dynamics. High-value targets are no longer just lost in the noise; they are flagged for immediate, aggressive follow-up actions, such as ransomware deployment or fraudulent wire transfers. This post outlines the technical mechanics of Dolphin X's profiling behavior and provides the necessary detection rules and remediation steps to identify this prioritized targeting before the attackers act.

Technical Analysis

Threat Type: Remote Access Trojan (RAT) / Malware-as-a-Service (MaaS) Primary Platform: Windows (observed variants targeting Win10/11 and Server 2019+)

The AI Profiling Mechanism

The core differentiator of Dolphin X is its "ranking" feature. While the term "AI" is often marketing fluff in malware circles, in this context, it refers to heuristic logic that categorizes victim data automatically.

  1. Data Staging: Upon infection, the malware performs aggressive reconnaissance. It enumerates files in standard user directories (Documents, Desktop, Downloads) and scans for specific file extensions (e.g., .pdf, .docx, .xlsx, .txt, .key, .wallet).
  2. Local Scoring: The agent analyzes the volume and type of data. For instance, the presence of crypto wallets or directories named "finance" or "accounts" increases the victim's score.
  3. C2 Reporting: This score is transmitted to the Command and Control (C2) server alongside the system fingerprint. Operators can then sort their botnet by "Value," focusing manual extortion efforts on the top 1% of victims.

Attack Chain

  1. Initial Access: Typically via phishing (weaponized documents) or malvertising leading to fake software cracks.
  2. Execution: A PowerShell or CMD staging script drops the RAT payload, often obfuscated using encryption or packers (like Themida or VMProtect).
  3. Persistence: The malware establishes persistence via Registry Run keys or Scheduled Tasks, often masquerading as a legitimate system update service.
  4. Privilege Escalation: If UAC bypass modules are present, the RAT attempts to elevate privileges to access sensitive system areas.
  5. Profiling & Exfiltration: The AI module scans the filesystem, scores the host, and exfiltrates the high-value data.

Exploitation Status: Active exploitation confirmed in the wild. The malware is currently being sold as a subscription service, indicating a high volume of initial access attempts.

Detection & Response

Defending against Dolphin X requires catching the "profiling" behavior. Standard signature-based detection may fail if the malware is packed, but the behavior of enumerating and scoring files is distinct.

SIGMA Rules

The following rules detect the aggressive file enumeration associated with AI profiling and the persistence mechanisms typical of this RAT family.

YAML
---
title: Potential Victim Profiling via Rapid File Enumeration
id: 8a2b4c9d-1e3f-4a5b-8c6d-9e0f1a2b3c4d
status: experimental
description: Detects processes rapidly scanning user directories, a behavior consistent with AI-driven victim profiling used by RATs like Dolphin X.
references:
  - https://attack.mitre.org/techniques/T1005/
author: Security Arsenal
date: 2026/04/14
tags:
  - attack.collection
  - attack.t1005
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
    CommandLine|contains:
      - 'Get-ChildItem'
      - 'dir '
      - 'ls '
  filter_legit_admin:
    ParentImage|contains:
      - '\explorer.exe'
  condition: selection and not filter_legit_admin
falsepositives:
  - Legitimate administrative scripts searching for files
level: medium
---
title: Suspicious Persistence via Unsigned Binary in Startup
id: 9b3c5d0e-2f4a-5b6c-9d7e-0f1a2b3c4d5e
status: experimental
description: Detects creation of registry run keys pointing to binaries located in user profile AppData directories, a common persistence vector for Dolphin X.
references:
  - https://attack.mitre.org/techniques/T1547/
author: Security Arsenal
date: 2026/04/14
tags:
  - attack.persistence
  - attack.t1547.001
logsource:
  category: registry_set
  product: windows
detection:
  selection:
    TargetObject|contains:
      - '\Software\Microsoft\Windows\CurrentVersion\Run'
      - '\Software\Microsoft\Windows\CurrentVersion\RunOnce'
    Details|contains:
      - 'AppData\Roaming'
      - 'AppData\Local'
  filter_legit:
    Details|contains:
      - 'Microsoft'
      - 'Google'
      - 'Adobe'
  condition: selection and not filter_legit
falsepositives:
  - Legitimate software installation
level: high

KQL (Microsoft Sentinel / Defender)

Use this query to hunt for processes that exhibit the "profiling" behavior by accessing a high volume of distinct files in a short timeframe, specifically targeting document directories.

KQL — Microsoft Sentinel / Defender
// Hunt for Dolphin X Profiling Behavior
// Looks for processes reading multiple files in User Profile directories
DeviceFileEvents
| where Timestamp > ago(1h)
| where ActionType == "FileAccessed"
| where FolderPath has @"C:\Users\" and (FolderPath has @"Documents" or FolderPath has @"Desktop" or FolderPath has @"Downloads")
| summarize FileCount = count(), UniqueFolders = dcount(FolderPath) by InitiatingProcessFileName, InitiatingProcessAccountId, DeviceId
| where FileCount > 20 and UniqueFolders > 5
| project DeviceId, InitiatingProcessFileName, InitiatingProcessAccountId, FileCount, UniqueFolders
| order by FileCount desc

Velociraptor VQL

This artifact hunts for unsigned executables establishing network connections, a strong indicator of a RAT beaconing out after profiling the victim.

VQL — Velociraptor
-- Hunt for unsigned binaries with active network connections (RAT behavior)
SELECT Pid, Name, Exe, CommandLine, Username, 
       Connection.RemoteAddress, Connection.RemotePort
FROM pslist()
LEFT JOIN foreach(row=
    {
        SELECT Pid, RemoteAddress, RemotePort
        FROM netstat(pid=Pid)
        WHERE RemoteAddress != "0.0.0.0" AND RemoteAddress != "::" AND RemoteAddress != "127.0.0.1"
    },
    query={
        SELECT * FROM scope()
    }
) AS Connection
WHERE Exe NOT IN sigmgr(signatures="Microsoft")
   AND Exe NOT IN sigmgr(signatures="Verisign")
   AND Name NOT IN ("svchost.exe", "lsass.exe", "services.exe")

Remediation Script (PowerShell)

This script assists in identifying and suspending suspicious processes that match the Dolphin X operational profile (unsigned, running from user AppData, with network activity).

PowerShell
# Dolphin X Detection and Suspension Script
# Run as Administrator

Write-Host "Scanning for suspicious processes matching Dolphin X profile..." -ForegroundColor Cyan

$suspiciousProcesses = Get-Process | Where-Object {
    $_.Path -like "*$env:APPDATA*" -or $_.Path -like "*$env:LOCALAPPDATA*"
} | Where-Object {
    $_.MainModule.FileVersionInfo -and 
    $_.MainModule.FileVersionInfo.IsSigned -eq $false
} | Where-Object {
    # Check for network activity (basic check via established connections)
    Get-NetTCPConnection -OwningProcess $_.Id -ErrorAction SilentlyContinue
}

if ($suspiciousProcesses) {
    Write-Host "[ALERT] Found suspicious unsigned processes in AppData with network connections:" -ForegroundColor Red
    foreach ($proc in $suspiciousProcesses) {
        Write-Host "Process: $($proc.ProcessName) | PID: $($proc.Id) | Path: $($proc.Path)"
        # Optional: Stop process - Use with caution
        # Stop-Process -Id $proc.Id -Force
        Write-Host "Action: Suspended process $($proc.Id)." -ForegroundColor Yellow
    }
} else {
    Write-Host "No immediate suspicious processes detected." -ForegroundColor Green
}

# Check Registry Run Keys for suspicious entries
Write-Host "Checking Registry Run Keys for unsigned executables..." -ForegroundColor Cyan
$runKeys = @(
    "HKLM\Software\Microsoft\Windows\CurrentVersion\Run",
    "HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce",
    "HKCU\Software\Microsoft\Windows\CurrentVersion\Run",
    "HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce"
)

foreach ($key in $runKeys) {
    try {
        Get-ItemProperty -Path $key -ErrorAction Stop | Get-Member -MemberType NoteProperty | Where-Object {
            $_.Name -ne "PSPath" -and $_.Name -ne "PSParentPath" -and $_.Name -ne "PSChildName" -and $_.Name -ne "PSDrive" -and $_.Name -ne "PSProvider"
        } | ForEach-Object {
            $value = (Get-ItemProperty -Path $key).($_.Name)
            if ($value -like "*$env:APPDATA*" -or $value -like "*$env:LOCALAPPDATA*") {
                Write-Host "[SUSPICIOUS] Key: $key | Value: $value" -ForegroundColor Yellow
            }
        }
    } catch {
        # Ignore missing keys
    }
}

Remediation

If an infection is suspected or confirmed:

  1. Isolate the Host: Immediately disconnect the affected machine from the network (physically or via firewall ACLs) to prevent further C2 communication or data exfiltration.
  2. Terminate Malicious Processes: Using the remediation script or EDR console, kill the process identified as the RAT payload.
  3. Remove Persistence: Inspect and clean the following locations:
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
    • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
    • Task Scheduler for tasks triggering user-level binaries.
  4. Credential Reset: Assume that the AI profiling module successfully exfiltrated credentials, browser cookies, and tokens. Reset all passwords for accounts accessed from the infected host. Revoke session tokens.
  5. Re-image: Due to the sophisticated nature of the profiling (potential for dual-use tools or hidden loaders), the most secure remediation is to wipe the drive and re-image from a known clean "gold" image.
  6. Hunt Laterally: Dolphin X may have moved laterally if credentials were harvested. Use the KQL queries above on adjacent endpoints to look for similar file enumeration patterns.

Related Resources

Security Arsenal Incident Response Services AlertMonitor Platform Book a SOC Assessment incident-response Intel Hub

incident-responseransomwarebreach-responseforensicsdfirdolphin-xratmalware-defensethreat-huntingwindows-security

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.