Back to Intelligence

AUDITTEAM Ransomware Gang: 8 Victims in 6 Days — RU/DE/IN/JP Targeting Analysis & Detection Rules

SA
Security Arsenal Team
September 14, 2026
12 min read

Classification: TLP:CLEAR | Report Date: 2026-09-14 | Source: ransomware.live dark web leak site monitoring | Analyst: Security Arsenal Threat Intelligence


Executive Summary

Security Arsenal's dark web monitoring of the AUDITTEAM ransomware leak site confirms 8 victim postings between 2026-09-09 and 2026-09-14 — a sustained operational tempo indicating an active campaign. Victims span Russia, Germany, India, and Japan, with confirmed targeting of the Technology and Transportation sectors. Notably, three of the eight postings are labeled "Paid Victim" entries, suggesting the gang is publishing proof-of-payment placeholders — a pressure tactic designed to demonstrate that other victims have paid and coerce holdouts.

Enterprise defenders in the affected sectors and geographies should treat this as an active-threat window. The correlation between this campaign's timeframe and the current CISA KEV cluster of edge-device and infrastructure-management CVEs (vCenter, Cisco FMC, Check Point) is assessed as moderate confidence for initial access.


Threat Actor Profile — AUDITTEAM

Attribution note: AUDITTEAM is a low-publicity operation with limited independent reporting. Profile elements below are derived from leak-site telemetry, posting behavior, and TTP overlap with comparable mid-tier crews. Confidence levels are annotated.

AttributeAssessmentConfidence
AliasesNone confirmed; "Audit Team" branding likely chosen to mimic legitimate audit/consulting firms in phishing luresLow
Operating modelAssessed closed or semi-private RaaS. Posting cadence and uniform victim-naming convention (masked strings + "Paid Victim ") suggest a small core team rather than a large affiliate programModerate
Ransom demandsNot publicly documented. Based on victim profile (mid-market technology and logistics firms), demands are estimated in the $150K–$2M USD range, consistent with mid-tier crewsLow
Initial accessAssessment centers on edge-device exploitation (VPN gateways, firewalls, management consoles) given the active KEV cluster, supplemented by credential phishing and exposed RDP. The "audit" branding supports invoice/audit-themed lure documentsModerate
Extortion modelDouble extortion confirmed — leak site publication with masked victim names, escalating to full naming if payment is not made. "Paid Victim" entries function as social proof of payment complianceHigh
Dwell timeEstimated 5–14 days based on posting cluster timing (batch postings on 09-09, 09-13, and 09-14 suggest staged detonation followed by batch leak publication)Low-Moderate

Current Campaign Analysis

Victim Breakdown (Last 100 Postings — 8 Total)

Victim (masked)SectorCountryPublished
Ne***oxTechnologyRU2026-09-14
Paid Victim F9CF4B639CAC1B18Not FoundRU2026-09-13
Paid Victim FDC699DE3A112669Not FoundDE2026-09-13
vi***inTransportationIN2026-09-13
TE***PBNot FoundRU2026-09-12
mo***alNot FoundDE2026-09-09
ki***jpNot FoundJP2026-09-09
my***ruTechnologyRU2026-09-09

Sector Targeting

  • Technology (2 confirmed): Likely targeted for downstream supply-chain leverage and high-value IP/source code exfiltration.
  • Transportation (1 confirmed): Consistent with industry-wide ransomware focus on logistics downtime sensitivity.
  • Not Found (5): Unclassified victims. The high proportion of uncategorized entries suggests either very recent compromises not yet enriched, or deliberate obfuscation of victims still in negotiation.

Geographic Concentration

  • Russia (4/8 — 50%): Unusual. Most Western-facing crews exclude RU/CIS targets. This distribution suggests AUDITTEAM is either a non-Russian-aligned actor, or deliberately operating in permissive jurisdictions. It does not reduce risk to Western enterprises — German victims confirm EU operations.
  • Germany (2/8), India (1/8), Japan (1/8): Spread across EMEA and APAC indicates opportunistic targeting via internet-facing vulnerability scanning rather than region-specific social engineering.

Victim Profile

Masked names and "Not Found" sector tags indicate small-to-mid-market organizations — companies large enough to pay but lacking mature SOC/MDR coverage. Estimated revenue band: $10M–$500M USD. Technology victims may be MSP-adjacent or software firms, raising downstream supply-chain risk.

Posting Frequency / Escalation

  • Cadence: Two batch drops (09-09: 3 victims; 09-12→09-14: 5 victims). This pulse pattern is consistent with a crew that detonates and exfiltrates in waves, then publishes in batches.
  • Escalation signal: The appearance of "Paid Victim " entries on 09-13 is notable — the gang is advertising payment compliance mid-campaign, typically a sign of an aggressive negotiation pipeline and more victims pending publication.

CVE Correlation (Initial Access Assessment)

The following actively exploited CVEs overlap with this campaign's window and represent the highest-probability access vectors:

  • CVE-2026-59310 — VMware vCenter Path Traversal (KEV 2026-08-18): Network-accessible path traversal against vCenter. Direct path to virtualization-layer ransomware deployment — the highest-impact scenario for mass encryption.
  • CVE-2026-20316 — Cisco FMC Hard-coded Password (KEV 2026-07-29): Trivially exploitable management-plane compromise of firewall infrastructure.
  • CVE-2026-50751 — Check Point Security Gateway Improper Authentication (KEV 2026-06-08): IKEv1 auth bypass on VPN gateways — a classic ransomware front door.
  • CVE-2024-1708 — ConnectWise ScreenConnect Path Traversal (KEV 2026-04-28): RCE against RMM tooling; strongly associated with technology-sector/MSP victims.
  • CVE-2026-48027 — Nx Console Embedded Malicious Code (KEV 2026-05-27): Supply-chain vector directly relevant to the Technology-sector victims (developer workstation compromise).

Priority action: If you operate vCenter, Cisco FMC, Check Point gateways, ScreenConnect, or Nx Console in your dev toolchain, treat these as emergency patch/verify items this week.


Detection Engineering

The following detections target the TTP chain assessed for this campaign: edge-device exploitation → tunnel/RMM establishment → lateral movement → staging/exfil → pre-encryption sabotage.

YAML
---
title: Edge Device Exploitation Followed by Suspicious Child Process
description: Detects web server, VPN, or management-plane processes spawning shells or script interpreters — consistent with post-exploitation of vCenter, Cisco FMC, Check Point, or ScreenConnect vulnerabilities as seen in the AUDITTEAM campaign window.
logsource:
  category: process_creation
  product: windows
detection:
  parent_processes:
    ParentImage|contains:
      - '\tomcat\'
      - '\vpxd'
      - '\ScreenConnect'
      - '\httpd'
      - '\nginx'
      - '\w3wp.exe'
  suspicious_children:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\rundll32.exe'
      - '\certutil.exe'
      - '\bitsadmin.exe'
  condition: parent_processes and suspicious_children
level: high
tags:
  - attack.initial_access
  - attack.t1190
  - attack.t1059
---
title: Lateral Movement via PsExec or WMI Remote Execution
description: Detects PsExec service installation and WMI-spawned processes — lateral movement tradecraft commonly observed in mid-tier ransomware intrusions between initial access and detonation.
logsource:
  category: process_creation
  product: windows
detection:
  selection_psexec:
    Image|endswith:
      - '\PSEXESVC.exe'
      - '\psexec.exe'
      - '\paexec.exe'
  selection_wmi:
    ParentImage|endswith: '\WmiPrvSE.exe'
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\rundll32.exe'
      - '\mshta.exe'
  condition: 1 of selection_*
level: high
tags:
  - attack.lateral_movement
  - attack.t1021.002
  - attack.t1047
  - attack.t1569.002
---
title: Pre-Ransomware Staging - Shadow Copy Deletion and Archive Exfiltration
description: Detects Volume Shadow Copy deletion, backup catalog tampering, and mass archive/exfil tooling (rclone, 7zip with password flags) — the final T-minus phase before encryption fires in double-extortion operations.
logsource:
  category: process_creation
  product: windows
detection:
  selection_vss:
    - Image|endswith: '\vssadmin.exe'
      CommandLine|contains:
        - 'delete shadows'
        - 'resize shadowstorage'
    - Image|endswith: '\wmic.exe'
      CommandLine|contains: 'shadowcopy'
    - Image|endswith: '\bcdedit.exe'
      CommandLine|contains: 'recoveryenabled'
  selection_exfil:
    - Image|endswith: '\rclone.exe'
    - Image|endswith:
        - '\7z.exe'
        - '\7za.exe'
        - '\rar.exe'
      CommandLine|contains:
        - ' -p'
        - ' -v'
        - ' a '
  condition: 1 of selection_*
level: critical
tags:
  - attack.impact
  - attack.t1490
  - attack.t1560.001
  - attack.exfiltration
  - attack.t1567
KQL — Microsoft Sentinel / Defender
// AUDITTEAM Pre-Ransomware Hunt: Staging, Lateral Movement, and Defense Evasion
// Microsoft Sentinel / Defender XDR — run over last 14 days
let Lookback = 14d;
let SuspiciousTools = dynamic(["rclone.exe", "psexec.exe", "psexesvc.exe", "paexec.exe",
  "anydesk.exe", "screenconnect", "ngrok.exe", "chisel.exe", "7z.exe", "rar.exe"]);
let ToolHits = DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where FileName in~ (SuspiciousTools)
    or ProcessCommandLine has_any ("rclone", "psexec", "shadowcopy delete",
        "delete shadows", "recoveryenabled no", "wbadmin delete")
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine,
    InitiatingProcessAccountName, InitiatingProcessFileName;
let RareRemoteLogons = DeviceLogonEvents
| where TimeGenerated > ago(Lookback)
| where LogonType in ("RemoteInteractive", "Network")
| where RemoteDeviceName !in~ ("", "localhost")
| summarize RDPConnections = count(), DistinctSources = dcount(RemoteIP),
    Sources = make_set(RemoteIP, 5)
    by DeviceName, AccountName, bin(TimeGenerated, 1h)
| where DistinctSources >= 3;
let NewAdminSessions = DeviceEvents
| where TimeGenerated > ago(Lookback)
| where ActionType == "ServiceInstalled"
| where AdditionalFields has_any ("PSEXESVC", "ScreenConnect", "AnyDesk");
union ToolHits,
    (RareRemoteLogons | project TimeGenerated, DeviceName,
        FileName = "RDP/NetworkLogonAnomaly",
        ProcessCommandLine = strcat("Sources: ", Sources),
        InitiatingProcessAccountName = AccountName,
        InitiatingProcessFileName = "") ,
    (NewAdminSessions | project TimeGenerated, DeviceName,
        FileName = "SuspiciousServiceInstall",
        ProcessCommandLine = tostring(AdditionalFields),
        InitiatingProcessAccountName = "", InitiatingProcessFileName = "")
| summarize FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated),
    IndicatorCount = count(), Indicators = make_set(FileName)
    by DeviceName, InitiatingProcessAccountName
| where IndicatorCount >= 2
| order by IndicatorCount desc;
PowerShell
<#
.SYNOPSIS
  AUDITTEAM Rapid Triage — pre-ransomware indicator sweep
.DESCRIPTION
  Checks: (1) exposed RDP config, (2) scheduled tasks created in last 7 days,
  (3) Volume Shadow Copy status, (4) recently installed suspicious services.
  Run elevated on critical servers (hypervisors, file servers, DCs, backup hosts).
#>
$Report = @()
$Cutoff = (Get-Date).AddDays(-7)

Write-Host "=== [1/4] RDP Exposure Check ===" -ForegroundColor Cyan
$rdpEnabled = (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server').fDenyTSConnections -eq 0
$nlaEnabled = (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -ErrorAction SilentlyContinue).UserAuthentication
if ($rdpEnabled) {
    $Report += "[RISK] RDP ENABLED. NLA: $(if($nlaEnabled -eq 1){'On'}else{'OFF - CRITICAL'})"
    Get-NetTCPConnection -LocalPort 3389 -State Listen -ErrorAction SilentlyContinue |
        ForEach-Object { $Report += "  -> Listening on $($_.LocalAddress):3389" }
} else { $Report += "[OK] RDP disabled" }

Write-Host "=== [2/4] Scheduled Tasks (last 7 days) ===" -ForegroundColor Cyan
Get-ScheduledTask | Where-Object {
    $info = $_ | Get-ScheduledTaskInfo -ErrorAction SilentlyContinue
    ($_.Date -and ([datetime]$_.Date) -gt $Cutoff)
} | ForEach-Object {
    $action = ($_.Actions | Select-Object -First 1).Execute
    $Report += "[REVIEW] Task '$($_.TaskName)' created $($_.Date) -> $action"
}

Write-Host "=== [3/4] Volume Shadow Copy Status ===" -ForegroundColor Cyan
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
if (-not $shadows) {
    $Report += "[CRITICAL] NO shadow copies present - possible vssadmin deletion (pre-encryption indicator)"
} else {
    $Report += "[OK] $($shadows.Count) shadow copies. Oldest: $(($shadows | Sort-Object InstallDate | Select-Object -First 1).InstallDate)"
}
# Hunt vssadmin deletion artifacts in event log
$vssDelete = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4682; StartTime=$Cutoff} -ErrorAction SilentlyContinue
if ($vssDelete) { $Report += "[ALERT] $($vssDelete.Count) audit-policy/system events in window - review for tampering" }

Write-Host "=== [4/4] Suspicious Recently-Installed Services ===" -ForegroundColor Cyan
$suspiciousSvc = 'PSEXESVC|ScreenConnect|AnyDesk|TeamViewer|rclone|ngrok|chisel'
Get-CimInstance Win32_Service | Where-Object { $_.Name -match $suspiciousSvc -or $_.PathName -match $suspiciousSvc } |
    ForEach-Object { $Report += "[ALERT] Service '$($_.Name)' state=$($_.State) path=$($_.PathName)" }

Write-Host "`n================ TRIAGE REPORT ================" -ForegroundColor Yellow
$Report | ForEach-Object { Write-Host $_ }
$Report | Out-File "$env:TEMP\auditteam_triage_$(Get-Date -Format 'yyyyMMdd_HHmm').txt"

Incident Response Priorities

T-Minus Detection Checklist (Before Encryption Fires)

If AUDITTEAM's playbook follows the standard mid-tier crew pattern, you have a 5–14 day dwell window. Hunt for these in order:

  1. Edge-device anomalies — new admin accounts on VPN/firewall/management consoles; web server processes spawning shells (Sigma rule 1 above).
  2. Unexpected RMM presence — ScreenConnect, AnyDesk, or TeamViewer installations not deployed by IT (primary persistence channel).
  3. Lateral movement burst — PsExec service installs, WmiPrvSE-spawned commands, RDP connections from 3+ distinct sources to a single host within an hour (KQL query above).
  4. Discovery commandsnet group "Domain Admins", nltest /dclist, bloodhound-style LDAP enumeration, arp -a sweeps.
  5. Staging indicators — 7z/rar with password flags on servers, rclone configs appearing in user profiles, large outbound transfers (>5GB) to unfamiliar cloud storage endpoints.
  6. Pre-detonation sabotagevssadmin delete shadows, bcdedit recoveryenabled no, wbadmin delete catalog, backup-agent service stops. This is your final warning — typically minutes to hours before encryption.

Exfiltration Priorities (Assessed for This Crew)

Based on the Technology/Transportation targeting mix:

  • Technology victims: Source code repositories, customer databases, signing certificates, CI/CD secrets, support ticketing archives (credential goldmine).
  • Transportation victims: Shipment/customer PII, contracts and pricing, dispatch/telematics data, insurance and compliance documents (regulatory leverage).
  • Universal: Domain controller ntds.dit, finance/AP records, executive mailboxes, cyber-insurance policy documents (used to calibrate ransom demands).

Containment Actions — Ordered by Urgency

  1. Isolate edge devices under investigation — take compromised VPN/firewall/management appliances offline; do NOT reboot (preserve volatile memory for forensics).
  2. Kill unauthorized RMM/tunneling — block ScreenConnect/AnyDesk/ngrok/chisel at the egress proxy and EDR; hunt enterprise-wide, not just on the patient-zero host.
  3. Force credential rotation — domain admins, service accounts, VPN users, and any credentials stored on compromised management planes. Assume ntds.dit theft if a DC was touched.
  4. Block egress to consumer cloud storage — Mega, pCloud, Dropbox personal, and rclone-default endpoints; alert on bulk outbound from server VLANs.
  5. Protect backups immediately — verify offline/immutable copies are actually offline; disable backup-catalog deletion rights; snapshot hypervisor datastores.
  6. Segment server VLANs from workstations — emergency ACLs if flat network; ransomware detonation typically follows within 24–72h of staging detection.

Hardening Recommendations

Immediate (24 Hours)

  • Patch or mitigate the KEV cluster: CVE-2026-59310 (vCenter), CVE-2026-20316 (Cisco FMC), CVE-2026-50751 (Check Point), CVE-2024-1708 (ScreenConnect). If patching is impossible, remove the management interfaces from internet exposure today.
  • Audit internet-facing services: enumerate everything listening on the perimeter; disable unused VPN profiles; enforce MFA on all remote access.
  • Deploy the three Sigma rules and the KQL query above to your SIEM; run the triage script on domain controllers, hypervisors, file servers, and backup hosts.
  • Verify shadow copies exist on all critical servers — absence is itself a detection.
  • Block unauthorized RMM at proxy/EDR: ScreenConnect, AnyDesk, ngrok, chisel, rclone.

Short-Term (2 Weeks)

  • Management-plane segmentation: vCenter, firewall managers, and backup consoles must live in a dedicated, access-controlled admin VLAN with jump-host-only access.
  • Immutable/offline backups with tested restore — assume online backups will be targeted for deletion before encryption.
  • EGP (egress) policy enforcement: default-deny outbound from server subnets; allowlist required update/management destinations only.
  • Developer toolchain integrity (Technology sector): pin and verify IDE extension versions given the Nx Console supply-chain CVE (CVE-2026-48027); implement artifact signing verification in CI/CD.
  • Deploy canary/decoy artifacts — honey credentials and canary files on file servers to catch pre-encryption enumeration early.
  • Tabletop this scenario: run an IR exercise built on the T-minus checklist above with Technology and Transportation business units.

Security Arsenal continues to monitor the AUDITTEAM leak site for new victim postings, escalation to full-name disclosure, and infrastructure changes. Subscribers to AlertMonitor receive real-time alerts when new victims matching their sector or geography are posted.

Related Resources

Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub

Is your security operations ready?

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