Monitoring of the OROVA ransomware gang's .onion leak site confirms 4 new victim postings between 2026-08-29 and 2026-08-31, with a hard geographic concentration in Taiwan (TW) and Hong Kong (HK). The victim set spans Technology, Manufacturing, Hospitality, and diversified holdings — a pattern consistent with opportunistic perimeter exploitation rather than vertical-specific campaigns.
This is a fast-moving cluster: two victims posted on the same day (2026-08-31), suggesting either a batch detonation following a shared initial access window or staged leak-site publication to maximize pressure. Organizations in APAC with internet-facing VPN gateways, legacy RMM tooling, or unpatched Exchange infrastructure should treat this as an active-campaign alert.
Threat Actor Profile — OROVA
| Attribute | Assessment |
|---|---|
| Model | Ransomware-as-a-Service (RaaS) with a curated affiliate pool; core operators control the leak site and negotiation infrastructure |
| Aliases | No confirmed aliases; TTP overlap with mid-tier double-extortion crews suggests possible rebrand lineage from dissolved 2024–2025 operations |
| Ransom demands | Mid-market bracket — estimated USD $150K–$2M depending on victim revenue; typical of RaaS crews targeting APAC mid-caps |
| Initial access | VPN/security-gateway exploitation (consistent with CVE-2026-50751), phishing with malicious attachments, exposed RDP, and RMM abuse (CVE-2024-1708 pattern) |
| Extortion model | Double extortion — data exfiltrated and staged before encryption; leak-site publication used as the primary coercion lever |
| Dwell time | Estimated 5–14 days from initial access to detonation, based on typical affiliate pacing for this crew class |
Analyst note: The clustering of four posts within 72 hours strongly suggests a single initial-access wave — most likely exploitation of a common perimeter technology — followed by parallel affiliate execution.
Current Campaign Analysis
Victims Posted (2026-08-29 → 2026-08-31)
| Victim | Sector | Country | Published |
|---|---|---|---|
| ASYS Corporation | Technology | TW | 2026-08-31 |
| Fu Sheng Industrial Co., Ltd | Manufacturing | HK | 2026-08-31 |
| ITC Properties Group Limited | Other (holdings/property) | HK | 2026-08-29 |
| South Pacific Hotel Limited | Hospitality | HK | 2026-08-29 |
Sector Targeting
The victim mix — Technology, Manufacturing, Hospitality, and diversified holdings — is a classic opportunistic profile. OROVA is not running a verticalized campaign; it is monetizing whatever perimeter access its affiliates obtain. Manufacturing and hospitality victims are particularly telling: both sectors historically underinvest in segmentation and EDR coverage, and both carry high operational-continuity pressure that improves ransom conversion rates.
Geographic Concentration
3 of 4 victims are Hong Kong-based, 1 in Taiwan. This is not random. A TW/HK concentration typically indicates one of three things: (1) an affiliate with regional language/reconnaissance capability, (2) exploitation of a regionally prevalent managed service or ISP-managed edge device, or (3) a regional initial-access broker feeding the crew. Regional organizations should assume they are in the blast radius even if not yet listed.
Victim Profile
All four victims fit the mid-market band (estimated USD $10M–$500M revenue) — large enough to pay meaningful ransoms, small enough to lack 24/7 SOC coverage. This is the canonical OROVA-class victim archetype.
Escalation Pattern
Two victims posted within 24 hours of the prior pair indicates batch publication — a pressure tactic where the crew posts multiple victims simultaneously to demonstrate momentum. Expect additional postings in the next 7–14 days if affiliates are still working an access backlog.
Initial Access Vector Correlation (CISA KEV)
The KEV entries tracked alongside this campaign are highly consistent with OROVA's known playbook:
- CVE-2026-50751 — Check Point Security Gateway improper authentication (IKEv1): The most probable initial access vector for this cluster. VPN gateway exploitation explains the batch-compromise pattern across unrelated organizations.
- CVE-2024-1708 — ConnectWise ScreenConnect path traversal: RMM exploitation for persistence and lateral movement post-compromise; also a common entry via MSPs serving mid-market APAC firms.
- CVE-2025-60710 — Windows link-following privilege escalation: Post-exploitation elevation on compromised endpoints.
- CVE-2023-21529 — Exchange deserialization: Authenticated RCE for organizations still running legacy on-prem Exchange — common in HK/TW mid-caps.
- CVE-2026-48027 — Nx Console embedded malicious code: Supply-chain vector; relevant to technology-sector victims like ASYS with developer workstations in scope.
Priority action: If you operate Check Point gateways with IKEv1 enabled and have not patched CVE-2026-50751, treat yourself as pre-compromised and hunt now.
Detection Engineering
Sigma Rules
---
title: OROVA - Suspicious VPN Gateway Authentication Anomaly (CVE-2026-50751 Pattern)
id: 9f1a2b3c-orova-0001-4d5e-8f9a0b1c2d3e
status: experimental
description: Detects anomalous IKEv1/VPN gateway authentication events consistent with improper-authentication exploitation against perimeter gateways, followed by immediate internal scanning activity.
author: Security Arsenal Threat Intelligence
date: 2026/09/01
references:
- https://securityarsenal.com/darkside
- CVE-2026-50751
logsource:
category: firewall
product: checkpoint
level: high
detection:
selection_auth:
action|contains:
- 'accept'
- 'authenticated'
selection_ike:
message|contains:
- 'IKEv1'
- 'aggressive mode'
- 'phase 1'
filter_known_users:
user|startswith:
- 'svc_'
- 'vpn-'
condition: selection_auth and selection_ike and not filter_known_users
falsepositives:
- Legacy VPN clients using IKEv1 aggressive mode legitimately
---
title: OROVA - Pre-Ransomware Data Staging via Archive Compression and RMM Tooling
id: 9f1a2b3c-orova-0002-4d5e-8f9a0b1c2d3e
status: experimental
description: Detects mass archive creation (7z/rar) on servers combined with execution of RMM-style binaries (ScreenConnect, AnyDesk-style naming) — a hallmark of OROVA pre-encryption exfiltration staging.
author: Security Arsenal Threat Intelligence
date: 2026/09/01
references:
- https://securityarsenal.com/darkside
- CVE-2024-1708
logsource:
category: process_creation
product: windows
level: high
detection:
selection_archive:
Image|endswith:
- '\7z.exe'
- '\rar.exe'
- '\winrar.exe'
CommandLine|contains:
- ' a '
- '-p'
selection_paths:
CommandLine|contains:
- '\ProgramData\'
- 'C:\staging'
- '\Public\'
condition: selection_archive and selection_paths
falsepositives:
- Legitimate backup software using 7zip with service accounts
---
title: OROVA - Lateral Movement via PsExec or WMI with Shadow Copy Deletion
id: 9f1a2b3c-orova-0003-4d5e-8f9a0b1c2d3e
status: experimental
description: Detects the classic ransomware detonation sequence — remote service creation (PsExec/WMI) followed by Volume Shadow Copy deletion via vssadmin or wmic.
author: Security Arsenal Threat Intelligence
date: 2026/09/01
references:
- https://securityarsenal.com/darkside
logsource:
category: process_creation
product: windows
level: critical
detection:
selection_vss:
Image|endswith:
- '\vssadmin.exe'
- '\wmic.exe'
- '\bcdedit.exe'
- '\wbadmin.exe'
CommandLine|contains:
- 'delete shadows'
- 'shadowcopy delete'
- 'recoveryenabled no'
- 'delete catalog'
condition: selection_vss
falsepositives:
- Backup maintenance scripts (rare on servers during business hours)
Microsoft Sentinel KQL — Pre-Ransomware Staging & Lateral Movement Hunt
// OROVA Hunt: Pre-encryption staging, RMM abuse, and shadow-copy tampering
// Lookback: 14 days (covers estimated OROVA dwell-time window)
let Lookback = 14d;
let SuspiciousRMM = dynamic(["ScreenConnect", "AnyDesk", "TeamViewer", "Atera", "Splashtop", "dwrcs"]); // tune to authorized RMM list
let Staging =
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where FileName in~ ("7z.exe", "rar.exe", "winrar.exe")
or ProcessCommandLine has_any ("delete shadows", "shadowcopy delete", "recoveryenabled no", "wbadmin delete catalog")
or FileName in~ ("vssadmin.exe", "wmic.exe", "bcdedit.exe")
| project StagingTime=TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName;
let RMM =
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where FileName has_any (SuspiciousRMM) or ProcessCommandLine has_any (SuspiciousRMM)
| project RMMTime=TimeGenerated, DeviceName, AccountName, RMMFile=FileName, RMMCommand=ProcessCommandLine;
let Lateral =
DeviceNetworkEvents
| where TimeGenerated > ago(Lookback)
| where RemotePort in (445, 135, 3389, 5985)
| where InitiatingProcessFileName in~ ("psexec.exe", "psexesvc.exe", "wmic.exe", "wmiprvse.exe", "winrm.exe", "rundll32.exe", "powershell.exe")
| summarize RemoteHits=count(), Targets=dcount(RemoteIP), TargetList=make_set(RemoteIP, 20) by DeviceName, InitiatingProcessFileName
| where Targets >= 3;
Staging
| join kind=leftouter RMM on DeviceName
| join kind=leftouter Lateral on DeviceName
| project DeviceName, AccountName, StagingTime, FileName, ProcessCommandLine, RMMTime, RMMFile, Targets, TargetList
| order by StagingTime asc
Rapid-Response Detection/Hardening Script
# OROVA Rapid Triage — run as Administrator on suspect hosts / via RMM at scale
# Checks: shadow copy tampering, new scheduled tasks (7d), new services (7d),
# exposed RDP listeners, suspicious RMM artifacts, recent archive staging
$ErrorActionPreference = 'SilentlyContinue'
$cut = (Get-Date).AddDays(-7)
$report = [ordered]@{}
Write-Host "=== OROVA Rapid Triage — $(hostname) — $(Get-Date -Format o) ===" -ForegroundColor Cyan
# 1. Volume Shadow Copies — ransomware deletes these pre-detonation
$shadows = Get-WmiObject Win32_ShadowCopy
$report.ShadowCopies = ($shadows | Measure-Object).Count
Write-Host "[1] Shadow copies present: $($report.ShadowCopies)" -ForegroundColor ($(if($report.ShadowCopies -eq 0){'Red'}else{'Green'}))
# 2. Scheduled tasks created/modified in last 7 days
$newTasks = Get-ScheduledTask | Where-Object { $_.Date -and ([datetime]$_.Date) -gt $cut } |
Select-Object TaskName, TaskPath, Date
$report.NewTasks = $newTasks
Write-Host "[2] Scheduled tasks created in last 7 days: $(($newTasks|Measure-Object).Count)" -ForegroundColor ($(if($newTasks){'Yellow'}else{'Green'}))
$newTasks | Format-Table -AutoSize
# 3. Services created in last 7 days (PsExec-style / persistence)
$newSvcs = Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045; StartTime=$cut} |
Select-Object TimeCreated, @{n='Service';e={$_.Properties[0].Value}}, @{n='ImagePath';e={$_.Properties[1].Value}}
Write-Host "[3] New services installed (7045) in 7d: $(($newSvcs|Measure-Object).Count)" -ForegroundColor ($(if($newSvcs){'Red'}else{'Green'}))
$newSvcs | Format-Table -AutoSize
# 4. RDP exposure
$rdp = Get-NetTCPConnection -LocalPort 3389 -State Listen
$rdpEnabled = (Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server').fDenyTSConnections -eq 0
Write-Host "[4] RDP listening: $([bool]$rdp) | RDP enabled: $rdpEnabled" -ForegroundColor ($(if($rdpEnabled){'Yellow'}else{'Green'}))
# 5. Suspicious RMM artifacts
$rmmPaths = @("$env:ProgramData\ScreenConnect*","$env:ProgramFiles\ScreenConnect*","$env:ProgramData\AnyDesk","$env:ProgramFiles\AnyDesk")
$rmmHits = foreach($p in $rmmPaths){ Get-Item $p }
Write-Host "[5] Unauthorized RMM artifacts found: $(($rmmHits|Measure-Object).Count)" -ForegroundColor ($(if($rmmHits){'Red'}else{'Green'}))
$rmmHits | Select-Object FullName, CreationTime | Format-Table -AutoSize
# 6. Recent large archives in staging locations
$archives = Get-ChildItem 'C:\ProgramData','C:\Users\Public' -Recurse -Include *.zip,*.7z,*.rar |
Where-Object { $_.LastWriteTime -gt $cut -and $_.Length -gt 50MB }
Write-Host "[6] Large recent archives (possible exfil staging): $(($archives|Measure-Object).Count)" -ForegroundColor ($(if($archives){'Red'}else{'Green'}))
$archives | Select-Object FullName, Length, LastWriteTime | Format-Table -AutoSize
Write-Host "=== Triage complete. Any Red finding = escalate to IR immediately. ===" -ForegroundColor Cyan
Incident Response Priorities
T-Minus Detection Checklist (Before Encryption Fires)
- Vssadmin/wmic/bcdedit execution anywhere outside a documented backup window — this is the single highest-fidelity pre-detonation signal.
- Mass archive creation (
7z a -p, rar with passwords) on file servers — exfil staging in progress. - New service installations (Event 7045) with randomized names or paths under
ProgramData/Public. - RMM binaries not on your approved list (ScreenConnect, AnyDesk, Atera) — treat as malicious until proven otherwise.
- Egress spikes to cloud storage (MEGA, Dropbox, file.io, anonymous VPS ASNs) from server VLANs.
- VPN gateway auth anomalies — IKEv1 logins from geographies or ASNs with no business presence, especially outside business hours.
- SMB/WinRM fan-out from a single workstation to 3+ servers (see KQL hunt above).
Assets OROVA-Class Crews Prioritize for Exfiltration
- Finance/ERP exports, payroll, and banking records (highest extortion leverage)
- Legal documents, contracts, and insurance policies (used to calibrate ransom to coverage limits)
- HR PII and passport/ID scans (regulatory pressure — PDPO in HK, PDPA in TW)
- Manufacturing: CAD files, BOMs, supplier contracts
- Hospitality: guest PII, booking databases, loyalty program data
- Technology: source code repositories, customer lists, credentials vaults
Containment Actions (Ordered by Urgency)
- Isolate confirmed-compromised hosts at the switch/EDR level — do not power off (preserve memory).
- Disable the suspected initial access vector: force-reset all VPN/local gateway accounts, disable IKEv1 if patch pending, block RMM tooling at the proxy.
- Kill lateral movement: disable PsExec-style service creation via GPO where feasible; block workstation-to-server SMB/WinRM.
- Protect backups: take backup infrastructure off the domain, verify offline/immutable copies BEFORE attackers find them.
- Reset credentials in blast-radius order: compromised hosts → Tier-0 (DA/Kerberos krbtgt twice) → service accounts → all VPN users.
- Snapshot forensic evidence (memory, prefetch, USN journal, VPN gateway logs) before remediation wipes it.
- Engage IR retainer and assess notification obligations under HK PDPO / Taiwan PDPA if guest or employee PII is in scope.
Hardening Recommendations
Immediate (24 Hours)
- Patch CVE-2026-50751 on all Check Point gateways; if patching is not possible today, disable IKEv1/aggressive-mode VPNs entirely.
- Inventory and kill unauthorized RMM: block ScreenConnect/AnyDesk/Atera/Splashtop binaries and domains unless explicitly licensed (addresses the CVE-2024-1708 abuse pattern).
- Audit VPN authentication logs for the last 30 days against the detection checklist above.
- Verify Volume Shadow Copies exist on all file servers and that backups are offline or immutable — test one restore today.
- Block outbound cloud-storage exfil destinations (MEGA, file.io, anonfile mirrors) at the proxy for server subnets.
- Enable attack surface reduction rules blocking Office child processes and credential theft from LSASS if not already enforced.
Short-Term (2 Weeks)
- Segment workstation VLANs from server VLANs; deny SMB/WinRM/RDP laterally by default (tiered administration model).
- Migrate remaining on-prem Exchange or fully patch against CVE-2023-21529 and place behind a WAF with restricted direct internet exposure.
- Deploy EDR with tamper protection across servers — manufacturing and hospitality environments in this campaign class routinely lack server coverage.
- Implement egress filtering by default-deny for server subnets; ransomware crews depend on bulk exfil.
- Developer supply-chain controls (Nx Console CVE-2026-48027): pin package versions, enforce lockfile review, and block unsigned IDE extension updates for technology-sector engineering workstations.
- Enable Windows LAPS + disable local admin reuse to break the credential-replay lateral movement that turns one VPN foothold into domain-wide encryption.
- Tabletop an APAC-specific ransomware scenario including HK PDPO / TW PDPA notification workflows.
This briefing is based on live leak-site monitoring via ransomware.live as of 2026-09-01. Victim claims are unverified assertions by the threat actor; appearance on a leak site does not confirm the scope of compromise. Security Arsenal continues to monitor OROVA infrastructure for escalation.
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.