SOC Prime Bias: High

13 Nov 2026 09:15 UTC

Silver Fox Campaign Expands Beyond ValleyRAT

Author Photo
SOC Prime Team linkedin icon Follow
Silver Fox Campaign Expands Beyond ValleyRAT
shield icon

Detection stack

  • AIDR
  • Alert
  • ETL
  • Query

Summary

An investigation uncovered a China-nexus operation deploying the ValleyRAT backdoor between August and October 2026. The campaign uses DLL side-loading with renamed legitimate signed programs to execute loaders that establish C2 communications. The activity is linked to the Silver Fox intrusion set through shared registrar infrastructure and overlapping registration details.

Investigation

VMRay Labs analyzed 44 loader builds and decrypted their configurations, identifying 25 samples associated with the operation. Researchers traced infrastructure relationships through a shared Gname registrar account and a common file-sharing delivery host. The evidence suggests a Chinese-speaking operator conducting activity primarily during UTC+8 working hours.

Mitigation

Defenders should hunt for unsigned DLLs stored alongside renamed legitimate signed executables. Monitor for the creation of registry keys used for fileless payload storage and suspicious scheduled tasks. Organizations should also block identified C2 domains and IP addresses associated with the ValleyRAT infrastructure.

Response

Upon detection, isolate affected systems to prevent continued remote access through the ValleyRAT backdoor. Inspect the HKCU\Console registry key for malicious payloads and check for unauthorized kernel drivers. Conduct a forensic review of recent downloads from file-sharing services, including kaiwyrey.eu.cc.

Attack Flow

Detections

LOLBAS WScript / CScript (via process_creation)

SOC Prime Team
12 Nov 2026

Suspicious LOLBAS MSHTA Defense Evasion Behavior by Detection of Associated Commands (via process_creation)

SOC Prime Team
12 Nov 2026

Suspicious Scheduled Task (via audit)

SOC Prime Team
12 Nov 2026

Suspicious Command and Control by Unusual Top Level Domain (TLD) DNS Request (via dns)

SOC Prime Team
12 Nov 2026

IOCs (HashMd5) to detect: Beyond ValleyRAT: inside a China-nexus Silver Fox operation

SOC Prime AI Rules
12 Nov 2026

IOCs (SourceIP) to detect: Beyond ValleyRAT: inside a China-nexus Silver Fox operation

SOC Prime AI Rules
12 Nov 2026

IOCs (DestinationIP) to detect: Beyond ValleyRAT: inside a China-nexus Silver Fox operation

SOC Prime AI Rules
12 Nov 2026

ValleyRAT C2 Communication Detection [Windows Network Connection]

SOC Prime AI Rules
12 Nov 2026

Detection of ValleyRAT Core Storage in Registry [Windows Registry Event]

SOC Prime AI Rules
12 Nov 2026

Simulation Execution

  • Attack Narrative & Commands: The adversary has successfully established a foothold on the Windows endpoint. To maintain control and receive further instructions, the ValleyRAT malware attempts to beacon out to its hardcoded Command and Control (C2) infrastructure. The attacker uses a specific domain (taku788.club) to resolve the C2 IP address and subsequently initiates a connection to the known malicious IP 192.252.183.157. This action is intended to bypass standard firewall rules by mimicking standard web traffic, but it relies on the specific infrastructure identified by threat intelligence.

  • Regression Test Script:

    # ValleyRAT C2 Simulation Script
    # Purpose: Generate telemetry matching the specific IP and Domain in the detection rule.
    
    $C2_Domain = "taku788.club"
    $C2_IP = "192.252.183.157"
    
    Write-Host "[*] Simulating ValleyRAT C2 Communication..." -ForegroundColor Cyan
    
    # 1. Simulate DNS Resolution for the malicious domain
    Write-Host "[+] Step 1: Simulating DNS lookup for $C2_Domain"
    try {
        $resolved = [System.Net.Dns]::GetHostAddresses($C2_Domain)
        Write-Host "[!] Note: DNS resolution failed as expected in a sandbox, proceeding to direct IP connection." -ForegroundColor Yellow
    } catch {
        Write-Host "[!] DNS resolution failed (Normal for simulation without real domain)." -ForegroundColor Gray
    }
    
    # 2. Simulate the actual TCP connection to the C2 IP to trigger the Network Connection detection
    Write-Host "[+] Step 2: Initiating TCP connection to $C2_IP on port 80"
    try {
        $tcpClient = New-Object System.Net.Sockets.TcpClient
        # We use a timeout to prevent the script from hanging indefinitely
        $connect = $tcpClient.BeginConnect($C2_IP, 80, $null, $null)
        $wait = $connect.AsyncWaitHandle.WaitOne(2000, $false)
    
        if (-not $wait) {
            Write-Host "[!] Connection attempt completed (Telemetry should be generated)." -ForegroundColor Green
            $tcpClient.Close()
        } else {
            Write-Host "[!] Connection successful (unlikely in controlled lab)." -ForegroundColor Red
        }
    } catch {
        Write-Host "[!] Connection failed, but Sysmon should have captured the attempt." -ForegroundColor Green
    }
    
    Write-Host "[*] Simulation Complete." -ForegroundColor Cyan
  • Cleanup Commands:

    # No persistent changes were made to the system during this simulation.
    # If any temporary files were created, they should be deleted here.
    Write-Host "[*] Cleanup complete. No artifacts remain." -ForegroundColor Green