Introduction
Security teams managing environments with QuickFox VPN need to activate incident response protocols immediately. According to Fortinet FortiGuard Labs, a sophisticated supply chain attack has been actively distributing a trojanized version of the QuickFox VPN and network acceleration tool since at least August 2025. This compromised installer delivers FDMTP, an unauthorized access mechanism that grants attackers persistent remote access to victim systems.
What makes this particularly concerning is the duration of the campaign—operating undetected for over a year—and the nature of the target audience. QuickFox is specifically designed for overseas Chinese users, suggesting a focused operation with potential geopolitical motivations. Organizations with users in this demographic or operating in regions where this tool is commonly used should assume potential compromise and initiate hunting operations immediately.
The supply chain vector—trojanizing a legitimate VPN installer—represents a sophisticated attack chain that bypasses traditional perimeter controls. Users downloading what they believe to be a legitimate privacy tool are instead installing a backdoor. This attack highlights the critical importance of software supply chain validation and the need for behavioral detection beyond signature-based approaches.
Technical Analysis
Affected Products and Platforms
- Product: QuickFox VPN and network acceleration tool
- Platform: Windows (all versions supporting QuickFox)
- Attack Vector: Trojanized Windows Installer (MSI)
- Compromise Window: Active since at least August 2025
- Payload: FDMTP (Full Device Management and Tunneling Protocol)
Attack Chain Breakdown
The attack operates through a carefully orchestrated supply chain compromise:
-
Initial Access: Users download a trojanized QuickFox installer from compromised or impersonated distribution channels. The installer appears legitimate, including proper digital signatures (if present) and expected file metadata.
-
Execution: The Windows installer (MSI) executes what appears to be standard installation routines while simultaneously deploying FDMTP components.
-
Payload Deployment: FDMTP is extracted and installed on the system, often masquerading as legitimate VPN components or system utilities.
-
Persistence Establishment: FDMTP establishes one or more persistence mechanisms including:
- Windows services with innocent-sounding names
- Scheduled tasks
- Registry run keys
- DLL search order hijacking
-
Command and Control: The malware initiates outbound connections to C2 infrastructure, likely using ports in the 8000-9000 range to blend with common web traffic.
-
Unauthorized Access: Attackers gain remote access capabilities including:
- Remote command execution
- File upload/download
- Credential harvesting
- Screen capture
- Keylogging
Exploitation Status
- In-the-wild exploitation: Confirmed active since August 2025
- Campaign Duration: Over 12 months as of publication
- CVE Status: No CVE assigned (supply chain compromise, not vulnerability-based)
- Detection Gaps: Traditional signature-based detection may fail due to the trojanized nature of the legitimate installer
Detection & Response
SIGMA Rules
---
title: QuickFox Trojanized Installer Execution
id: 8a5f2c91-4d73-4e8f-9a1b-7c6e5d4a3b2c
status: experimental
description: Detects execution of potentially trojanized QuickFox installer which has been identified as delivering FDMTP malware via supply chain attack.
references:
- https://thehackernews.com/2026/08/quickfox-supply-chain-attack-delivers.html
author: Security Arsenal
date: 2026/08/15
tags:
- attack.initial_access
- attack.t1195.002
- attack.supply_chain
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\msiexec.exe'
CommandLine|contains:
- 'QuickFox'
- 'quickfox'
condition: selection
falsepositives:
- Legitimate QuickFox installation (verify source integrity)
level: high
---
title: FDMTP Unusual Network Activity
id: 3b7c6d42-9e1a-4f5c-8b2d-1a4e5c8f7d3e
status: experimental
description: Detects network behavior consistent with FDMTP unauthorized access mechanism delivered via QuickFox supply chain attack.
references:
- https://thehackernews.com/2026/08/quickfox-supply-chain-attack-delivers.html
author: Security Arsenal
date: 2026/08/15
tags:
- attack.command_and_control
- attack.t1071
- attack.c2
logsource:
category: network_connection
product: windows
detection:
selection:
Initiated: 'true'
DestinationPort|between:
- 8000
- 9000
filter:
Image|endswith:
- '\quickfox.exe'
- '\QuickFox.exe'
condition: selection and not filter
falsepositives:
- Other VPN applications using similar ports
level: medium
---
title: FDMTP Process Persistence Mechanism
id: 6d9e2f48-5b7c-4a3e-9d1f-8c7b6a5d4e3c
status: experimental
description: Detects persistence mechanisms potentially associated with FDMTP malware delivered via trojanized QuickFox installer.
references:
- https://thehackernews.com/2026/08/quickfox-supply-chain-attack-delivers.html
author: Security Arsenal
date: 2026/08/15
tags:
- attack.persistence
- attack.t1543
- attack.create_service
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\sc.exe'
- '\powershell.exe'
CommandLine|contains:
- 'FDMTP'
- 'fdmtp'
condition: selection
falsepositives:
- Unknown
level: critical
KQL (Microsoft Sentinel / Defender)
// Hunt for QuickFox installer executions in the last 30 days
DeviceProcessEvents
| where Timestamp >= ago(30d)
| where FileName =~ "msiexec.exe" and ProcessCommandLine contains "QuickFox"
| extend SourceIP = InitiatingProcessAccountName, Hostname = DeviceName
| project Timestamp, Hostname, FileName, ProcessCommandLine, InitiatingProcessAccountName, InitiatingProcessFileName
| order by Timestamp desc
// Hunt for FDMTP-related network connections
DeviceNetworkEvents
| where Timestamp >= ago(30d)
| where RemotePort between (8000 .. 9000)
| where not(InitiatingProcessFileName has "quickfox")
| project Timestamp, DeviceName, InitiatingProcessFileName, RemoteIP, RemotePort, RemoteUrl
| order by Timestamp desc
// Check for FDMTP persistence via service creation
SecurityEvent
| where TimeGenerated >= ago(30d)
| where EventID == 4688
| where NewProcessName contains "sc.exe" and CommandLine contains "FDMTP"
| project TimeGenerated, Computer, SubjectUserName, NewProcessName, CommandLine
| order by TimeGenerated desc
Velociraptor VQL
-- Hunt for QuickFox installation artifacts
SELECT FullPath, Mtime, Atime, Size, SHA256
FROM glob(globs="C:\\Program Files\\QuickFox\\*")
WHERE NOT FullPath =~ 'uninstall'
-- Check for FDMTP-related services
SELECT Name, DisplayName, State, StartMode, PathName, ProcessId
FROM wmi(query="SELECT * FROM Win32_Service WHERE Name LIKE '%FDMTP%' OR DisplayName LIKE '%FDMTP%'")
-- Hunt for suspicious network connections on FDMTP-associated ports
SELECT Family, RemoteAddress, RemotePort, State, Pid, ProcessName, StartTime
FROM netstat()
WHERE RemotePort > 8000 AND RemotePort < 9000 AND NOT ProcessName =~ 'quickfox'
Remediation Script (PowerShell)
# QuickFox Supply Chain Attack Remediation Script
# Author: Security Arsenal
# Date: 2026-08-15
Write-Host "Starting QuickFox/FDMTP Remediation Process..." -ForegroundColor Yellow
# Check if QuickFox is installed
$quickfoxPaths = @(
"$env:ProgramFiles\QuickFox",
"${env:ProgramFiles(x86)}\QuickFox",
"$env:LOCALAPPDATA\QuickFox"
)
$quickfoxInstalled = $false
foreach ($path in $quickfoxPaths) {
if (Test-Path $path) {
$quickfoxInstalled = $true
Write-Host "QuickFox found at: $path" -ForegroundColor Red
}
}
if ($quickfoxInstalled) {
# Kill QuickFox processes
Write-Host "Terminating QuickFox processes..." -ForegroundColor Yellow
Get-Process | Where-Object { $_.ProcessName -like "*quickfox*" } | Stop-Process -Force -ErrorAction SilentlyContinue
# Check for FDMTP services
Write-Host "Checking for FDMTP services..." -ForegroundColor Yellow
$fdmtpServices = Get-WmiObject -Class Win32_Service | Where-Object { $_.Name -like "*FDMTP*" -or $_.DisplayName -like "*FDMTP*" -or $_.PathName -like "*FDMTP*" }
if ($fdmtpServices) {
foreach ($service in $fdmtpServices) {
Write-Host "Found FDMTP service: $($service.Name) - $($service.PathName)" -ForegroundColor Red
Stop-Service -Name $service.Name -Force -ErrorAction SilentlyContinue
& sc.exe delete $service.Name
}
} else {
Write-Host "No FDMTP services found." -ForegroundColor Green
}
# Check for FDMTP scheduled tasks
Write-Host "Checking for FDMTP scheduled tasks..." -ForegroundColor Yellow
$fdmtpTasks = Get-ScheduledTask | Where-Object { $_.TaskName -like "*FDMTP*" -or $_.Actions.Execute -like "*FDMTP*" }
if ($fdmtpTasks) {
foreach ($task in $fdmtpTasks) {
Write-Host "Found FDMTP task: $($task.TaskName)" -ForegroundColor Red
Unregister-ScheduledTask -TaskName $task.TaskName -Confirm:$false
}
} else {
Write-Host "No FDMTP scheduled tasks found." -ForegroundColor Green
}
# Remove QuickFox installation
Write-Host "Removing QuickFox installation..." -ForegroundColor Yellow
foreach ($path in $quickfoxPaths) {
if (Test-Path $path) {
Remove-Item -Path $path -Recurse -Force
Write-Host "Removed: $path" -ForegroundColor Green
}
}
# Check registry for QuickFox persistence
Write-Host "Checking registry for QuickFox persistence..." -ForegroundColor Yellow
$registryPaths = @(
"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 ($regPath in $registryPaths) {
$quickfoxReg = Get-ItemProperty -Path $regPath -ErrorAction SilentlyContinue | Get-Member | Where-Object { $_.Name -like "*QuickFox*" -or $_.Name -like "*FDMTP*" }
if ($quickfoxReg) {
foreach ($item in $quickfoxReg) {
Write-Host "Found registry persistence: $($item.Name) in $regPath" -ForegroundColor Red
Remove-ItemProperty -Path $regPath -Name $item.Name -Force -ErrorAction SilentlyContinue
}
}
}
Write-Host "QuickFox removal complete. System reboot recommended." -ForegroundColor Green
} else {
Write-Host "QuickFox not found on this system." -ForegroundColor Green
}
# Perform network connection check for FDMTP-associated ports
Write-Host "Checking for active FDMTP-associated network connections..." -ForegroundColor Yellow
Get-NetTCPConnection -State Established | Where-Object { $_.RemotePort -ge 8000 -and $_.RemotePort -le 9000 } | Select-Object LocalAddress, LocalPort, RemoteAddress, RemotePort, State, OwningProcess | ForEach-Object {
$process = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
if ($process -and $process.ProcessName -notlike "*quickfox*") {
Write-Host "Suspicious connection found: $($_.RemoteAddress):$($_.RemotePort) by $($process.ProcessName) (PID: $($_.OwningProcess))" -ForegroundColor Red
}
}
Write-Host "Remediation script completed." -ForegroundColor Green
Remediation
Immediate Actions Required
-
System Assessment: Identify all systems where QuickFox VPN is installed:
- Query software inventory systems (SCCM, Intune, Tanium, etc.)
- Conduct endpoint scans using provided detection rules
- Review VPN access logs for QuickFox connections
-
Isolation of Affected Systems:
- Immediately isolate systems with QuickFox from the network
- Preserve volatile memory (RAM) and acquire forensic disk images
- Do not simply uninstall—FDMTP may have established persistence mechanisms separate from the main application
- Document system state, running processes, and network connections
-
Complete Removal Procedure:
- Uninstall QuickFox using Windows Program and Features or MsiExec /X
- Execute the provided PowerShell remediation script
- Manually verify removal of:
- All QuickFox directories
- FDMTP-related services
- Persistence mechanisms in startup folders
- Scheduled tasks referencing FDMTP components
- Registry run keys (HKLM/HKCU\Software\Microsoft\Windows\CurrentVersion\Run)
- Any recently created hidden directories
-
Credential Reset: Assume all credentials used on compromised systems have been exfiltrated:
- Reset all local and domain credentials for affected users
- Revoke and reissue any SSH keys or certificates stored on compromised systems
- Review VPN access logs for unauthorized connection times and originating IPs
- Force password changes for accounts used on affected systems
-
Network Traffic Analysis:
- Review firewall and proxy logs for connections to unusual IPs on ports 8000-9000
- Hunt for data exfiltration patterns during the compromise timeframe
- Implement network blocks for known C2 infrastructure (consult threat intelligence feeds)
- Analyze DNS logs for suspicious domain resolutions
-
Reimaging Considerations: Given the sophistication and duration of this threat:
- Strongly consider reimaging affected systems from known-good media
- Perform fresh installation of operating system and applications
- Do not restore from backups created during the compromise window
- Implement Zero Trust principles when returning systems to production
Vendor Advisory Status
As of this publication, QuickFox has not released an official security advisory or statement regarding this compromise. Organizations should:
- Monitor the official QuickFox website and communication channels for security updates
- Verify any future downloads by checking digital signatures against known good values
- Consider alternative VPN solutions with transparent security practices until QuickFox addresses this compromise
- Consult threat intelligence feeds for updated IOC lists related to this campaign
Longer-term Hardening Recommendations
-
Software Supply Chain Controls:
- Implement Software Bill of Materials (SBOM) validation for all critical software
- Require code signing verification for all software installations
- Deploy application allowlisting (AppLocker, WDAC) to prevent unauthorized software execution
- Use dedicated systems for software testing before production deployment
- Implement application control policies that require approval for new software installations
-
Network Segmentation:
- Implement Zero Trust network access controls with continuous verification
- Segment VPN traffic from internal critical resources
- Deploy east-west traffic monitoring to detect lateral movement
- Implement microsegmentation to limit blast radius of compromised endpoints
-
Enhanced Monitoring Capabilities:
- Deploy EDR solutions with behavioral detection capabilities
- Implement continuous monitoring for supply chain compromise indicators
- Regularly review software installation logs across the enterprise
- Establish baseline behavior for VPN applications and alert on deviations
-
Security Awareness Training:
- Educate users on risks of downloading software from unofficial sources
- Establish clear policies for VPN client approval and usage
- Implement centralized software distribution to prevent shadow IT
Remediation Timeline
Given the active nature of this threat and its persistence for over 12 months, organizations should adhere to the following timeline:
- 0-24 hours: Complete system assessment and isolation of affected endpoints
- 0-48 hours: Complete forensic acquisition of critical systems
- 0-72 hours: Complete full remediation including credential reset and potential reimaging
- 7 days: Complete network traffic analysis and threat hunting across environment
- 14 days: Implement recommended hardening controls and updated detection rules
Organizations with confirmed compromises should consider this a high-severity incident requiring executive notification and potentially regulatory reporting depending on the nature of data exposed.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.