Classification: TLP:CLEAR | Publication Date: 2026-08-06 | Source: Live monitoring of BARRACUDA .onion leak site via ransomware.live
Executive Summary
BARRACUDA's dark web leak site has posted 4 new victims in a 48-hour window (2026-08-05 through 2026-08-06), spanning three countries (China, United States, South Korea) and three sectors (Manufacturing, Healthcare, Technology). The compressed posting cadence suggests either a batch-detonation event — multiple intrusions reaching extortion stage simultaneously — or an intentional publication burst designed to maximize pressure on non-paying victims. Manufacturing represents 50% of this posting wave, consistent with the broader 2026 trend of ransomware crews prioritizing industrial firms with low downtime tolerance.
Organizations operating Check Point Security Gateways, Cisco FMC, Microsoft Exchange, or ConnectWise ScreenConnect should treat this briefing as an immediate patching and threat-hunting trigger.
1. Threat Actor Profile — BARRACUDA
| Attribute | Assessment |
|---|---|
| Aliases | BARRACUDA (leak site branding); no confirmed overlap with Barracuda Networks the vendor — a deliberate naming confusion tactic |
| Operating Model | Assessed RaaS (Ransomware-as-a-Service) with affiliate-driven intrusions; leak site infrastructure and negotiation handled by core operators |
| Ransom Demands | Typically USD $250K–$3M, scaled to victim revenue; healthcare/dental victims see lower initial demands ($100K–$500K) reflecting smaller org size |
| Initial Access | Edge device exploitation (VPN gateways, firewalls), exposed RDP, phishing with macro-enabled documents, and abuse of remote access tooling (ScreenConnect-class RMM) |
| Extortion Model | Double extortion — data exfiltration prior to encryption, leak-site publication in waves with countdown timers |
| Average Dwell Time | Estimated 5–14 days from initial access to detonation; exfiltration staging typically occurs 48–96 hours pre-encryption |
| Confidence | Moderate — based on victimology patterns, posting cadence, and KEV correlation |
Analyst Note: The gang's victim mix (a dental practice alongside industrial manufacturers) is characteristic of affiliate-model operations where access quality varies — one affiliate exploits opportunistic edge-device access at SMBs while another runs deliberate campaigns against mid-market industrial targets.
2. Current Campaign Analysis
Recent Leak Site Postings
| Victim | Sector | Country | Published |
|---|---|---|---|
| RS Automation Co., Ltd. | Manufacturing | CN | 2026-08-06 |
| Ferrell / Skyline Implants & Periodontics / Dr. Scott Ferguson | Healthcare | Unknown (likely US) | 2026-08-05 |
| Micro-Comm Inc. | Technology | US | 2026-08-05 |
| Namyang Industrial Co., Ltd. / NAMYANG NEXMO | Manufacturing | KR | 2026-08-05 |
Sector Targeting
- Manufacturing (50%) — RS Automation (industrial automation components) and Namyang Industrial are classic ransomware targets: mid-market revenue ($10M–$500M est.), OT/IT convergence, high downtime cost, and historically weak endpoint visibility on production networks.
- Healthcare (25%) — The dental/periodontics practice fits the SMB healthcare pattern: weak perimeter, outsourced IT, high PHI value for extortion leverage despite small ransom potential.
- Technology (25%) — Micro-Comm Inc. (SCADA/telemetry monitoring for water utilities) is the most strategically concerning victim. Compromise of a utility-monitoring vendor creates downstream supply-chain risk to critical infrastructure operators.
Geographic Concentration
Asia-Pacific (CN, KR) represents 50%+ of this wave — a notable shift from the historically US/Western-Europe-heavy victimology of most Western ransomware crews. This may indicate an affiliate with regional language capability and targeting infrastructure in APAC.
Posting Frequency / Escalation
4 postings in ~48 hours against a baseline of intermittent activity indicates a batch event. When multiple victims appear simultaneously, the intrusions likely occurred days to weeks apart but reached the extortion-publication stage together — meaning additional victims from the same campaign wave may already be encrypted but not yet posted. If you are a mid-market manufacturer or healthcare SMB, assume elevated targeting for the next 14 days.
CVE Correlation — Probable Initial Access Vectors
The following CISA KEV entries with confirmed ransomware use align with BARRACUDA's observed access tradecraft:
| CVE | Product | KEV Added | Relevance |
|---|---|---|---|
| CVE-2026-50751 | Check Point Security Gateway (IKEv1 improper auth) | 2026-06-08 | Primary suspect — edge VPN auth bypass matches gang's entry profile and 8-week head start before this campaign wave |
| CVE-2026-20131 | Cisco Secure FMC deserialization | 2026-03-19 | Firewall management plane compromise enables full perimeter control |
| CVE-2024-1708 | ConnectWise ScreenConnect path traversal | 2026-04-28 | RMM abuse — matches affiliate tradecraft for SMB victims (dental practice) |
| CVE-2023-21529 | Microsoft Exchange deserialization | 2026-04-13 | Legacy Exchange persistence vector |
| CVE-2026-48027 | Nx Console embedded malicious code | 2026-05-27 | Supply-chain/dev-tooling vector; possible link to technology-sector victim |
The ~8-week gap between CVE-2026-50751's KEV listing and this victim wave is consistent with a realistic intrusion lifecycle: exploit → access broker handoff or affiliate detonation → exfil → publish.
3. Detection Engineering
Sigma Rules
---
title: BARRACUDA Ransomware - Suspicious Authentication Anomaly on VPN/Edge Gateway
id: 7f3a1c2e-8b41-4e5a-9c1d-barracuda001
status: experimental
description: Detects anomalous successful VPN/IKEv1 authentication from unusual source IPs followed by internal lateral authentication, consistent with edge gateway exploitation (CVE-2026-50751 class) used by BARRACUDA affiliates for initial access.
author: Security Arsenal Threat Intelligence
date: 2026/08/06
references:
- https://securityarsenal.com/darkside
logsource:
category: authentication
product: vpn
detection:
selection_success:
event.outcome: success
selection_suspicious_geo:
source.ip|cidr:
- '103.0.0.0/8'
- '45.0.0.0/8'
- '185.0.0.0/8'
- '193.0.0.0/8'
filter_known_users:
user.name|contains:
- 'svc-vpn'
- 'healthcheck'
condition: selection_success and selection_suspicious_geo and not filter_known_users
falsepositives:
- Traveling executives on roaming networks
level: high
tags:
- attack.initial_access
- attack.t1133
- attack.t1190
---
title: BARRACUDA Ransomware - PsExec or WMI Remote Service Execution
id: 8a4b2d3f-9c52-4f6b-ad2e-barracuda002
status: experimental
description: Detects remote service creation via PsExec-style named pipes or WMI process call create, a hallmark lateral movement technique used by BARRACUDA affiliates prior to ransomware deployment.
author: Security Arsenal Threat Intelligence
date: 2026/08/06
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'
selection_service_install:
EventID: 7045
ServiceFileName|contains:
- 'ADMIN$'
- '\\127.0.0.1'
- 'AppData\\Local\\Temp'
condition: 1 of selection_*
falsepositives:
- Legitimate administrative tooling (SCCM, PDQ) - tune by service name and admin host
level: high
tags:
- attack.lateral_movement
- attack.t1021.002
- attack.t1569.002
- attack.t1047
---
title: BARRACUDA Ransomware - Pre-Encryption Data Staging and Shadow Copy Deletion
id: 9b5c3e4a-0d63-4a7c-be3f-barracuda003
status: experimental
description: Detects the canonical pre-detonation sequence observed in BARRACUDA intrusions - mass archive creation (7z/rar) in staging directories combined with Volume Shadow Copy deletion and backup catalog tampering.
author: Security Arsenal Threat Intelligence
date: 2026/08/06
logsource:
category: process_creation
product: windows
detection:
selection_archive:
Image|endswith:
- '\7z.exe'
- '\7za.exe'
- '\rar.exe'
- '\winrar.exe'
CommandLine|contains:
- ' a '
- '-mx'
- '-hp'
selection_staging_path:
CommandLine|contains:
- '\\ProgramData\\'
- '\\PerfLogs\\'
- 'C:\\Temp\\'
- '\\Users\\Public\\'
selection_vss:
Image|endswith:
- '\vssadmin.exe'
- '\wmic.exe'
- '\bcdedit.exe'
- '\wbadmin.exe'
CommandLine|contains:
- 'delete shadows'
- 'shadowcopy delete'
- 'delete catalog'
- 'recoveryenabled no'
condition: (selection_archive and selection_staging_path) or selection_vss
falsepositives:
- Backup administrators running legitimate archive jobs - allowlist by service account
level: critical
tags:
- attack.collection
- attack.t1560.001
- attack.impact
- attack.t1490
KQL — Microsoft Sentinel Hunt Query: Pre-Ransomware Staging & Lateral Movement
// BARRACUDA campaign hunt: staging, exfil tooling, and lateral movement chain
// Hunt window: 14 days (covers assessed dwell time)
let Lookback = 14d;
let SuspiciousTools = dynamic(["rclone.exe","megacmd.exe","filezilla.exe","winscp.exe","psexec.exe","psexesvc.exe","7z.exe","rar.exe","nltest.exe","adfind.exe","sharpview.exe","seatbelt.exe"]);
let StagingPaths = dynamic(["\\ProgramData\\","\\PerfLogs\\","\\Users\\Public\\","C:\\Temp\\"]);
// Phase 1: Discovery + staging tool execution on servers
let StagingEvents =
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where FileName in~ (SuspiciousTools)
or (ProcessCommandLine has_any (StagingPaths) and ProcessCommandLine has_any (" a "," -mx"," -hp","zip"))
| project StagingTime=TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName;
// Phase 2: VSS deletion / backup sabotage on same devices within 72h
let SabotageEvents =
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where ProcessCommandLine has_any ("delete shadows","shadowcopy delete","delete catalog","recoveryenabled no","wbadmin delete")
| project SabotageTime=TimeGenerated, DeviceName, SabotageCmd=ProcessCommandLine, AccountName;
// Phase 3: correlate — same device, sabotage follows staging (kill chain ordering)
StagingEvents
| join kind=inner SabotageEvents on DeviceName
| where SabotageTime > StagingTime and SabotageTime < StagingTime + 72h
| summarize StagingFirstSeen=min(StagingTime), SabotageFirstSeen=min(SabotageTime),
Tools=make_set(FileName), Accounts=make_set(AccountName)
by DeviceName
| extend HoursBetween = datetime_diff("hour", SabotageFirstSeen, StagingFirstSeen)
| sort by SabotageFirstSeen desc;
PowerShell — Rapid Exposure & Pre-Detonation Triage Script
# BARRACUDA Rapid Triage - run on suspect hosts or via remote session sweep
# Checks: exposed RDP, recent scheduled tasks, shadow copies, suspicious staging dirs, new local admins
$Report = @{}; $now = Get-Date
# 1. RDP exposure and NLA status
$rdp = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server'
$nla = Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp'
$Report.RDPEnabled = ($rdp.fDenyTSConnections -eq 0)
$Report.NLAEnabled = ($nla.UserAuthentication -eq 1)
$Report.RDPPort = (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').PortNumber
# 2. Scheduled tasks created in last 7 days (persistence / remote deploy staging)
$Report.RecentTasks = Get-ScheduledTask | Where-Object {
$_.Date -and ([datetime]$_.Date) -gt $now.AddDays(-7) -and
$_.TaskPath -notlike '\Microsoft*'
} | Select-Object TaskName, TaskPath, Date, @{n='Action';s={$_.Actions.Execute}} | Format-List
# 3. Volume Shadow Copies - ransomware deletes these; absence on a server is a red flag
$Report.ShadowCopies = (Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue | Measure-Object).Count
# 4. Suspicious staging directories with recent large archives
$Report.StagingFiles = Get-ChildItem 'C:\ProgramData','C:\PerfLogs','C:\Users\Public' -Recurse -ErrorAction SilentlyContinue |
Where-Object { $_.Length -gt 50MB -and $_.LastWriteTime -gt $now.AddDays(-7) -and
$_.Extension -match '\.(zip|rar|7z|tar|gz)$' } |
Select-Object FullName, Length, LastWriteTime
# 5. Local admins added in last 14 days
$Report.NewAdmins = Get-LocalGroupMember -Group 'Administrators' -ErrorAction SilentlyContinue |
ForEach-Object { $m=$_; Get-LocalUser -Name $m.Name.Split('\')[-1] -ErrorAction SilentlyContinue } |
Where-Object { $_ -and $_.PasswordLastSet -gt $now.AddDays(-14) } | Select-Object Name, PasswordLastSet
# 6. Recent 7045 service installs (PsExec-style lateral movement artifact)
$Report.NewServices = Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045; StartTime=$now.AddDays(-7)} -ErrorAction SilentlyContinue |
Select-Object TimeCreated, @{n='Service';s={$_.Properties[0].Value}}, @{n='Binary';s={$_.Properties[1].Value}}
$Report | ConvertTo-Json -Depth 4 | Out-File "$env:TEMP\barracuda_triage_$(hostname)_$(Get-Date -Format yyyyMMdd_HHmm).json"
Write-Host "[+] Triage complete. Review output JSON in $env:TEMP" -ForegroundColor Green
if (-not $Report.NLAEnabled -and $Report.RDPEnabled) { Write-Warning "[!] RDP exposed WITHOUT NLA - immediate containment action required" }
if ($Report.ShadowCopies -eq 0) { Write-Warning "[!] Zero shadow copies on host - possible pre-detonation sabotage" }
4. Incident Response Priorities
T-Minus Detection Checklist (Before Encryption Fires)
- Archive staging — multi-GB
.rar/.7zfiles appearing inProgramData,PerfLogs, orUsers\Publicon file servers - Exfil tooling —
rclone.exe,megacmd.exe, or WinSCP running under service accounts; large outbound transfers (>5GB/day) to unfamiliar cloud storage or offshore IPs - Backup sabotage precursors —
vssadmin delete shadows,wbadmin delete catalog,bcdedit ... recoveryenabled no, or backup agent service stops - Lateral movement burst — sudden 7045 service-install events across multiple servers from a single admin workstation
- EDR tampering — defensive product services stopped, sensor uninstalls, or
Set-MpPreference -DisableRealtimeMonitoring $true
Critical Assets Historically Prioritized for Exfiltration
- Manufacturing victims: CAD/design files, PLC/SCADA configs, ERP exports, customer contracts, QA documentation
- Healthcare victims: PHI databases, billing records, imaging archives — maximum regulatory extortion leverage
- All victims: Finance/AR data, executive mailboxes, HR records (used for secondary extortion of employees/customers)
Containment Actions — Ordered by Urgency
- Isolate affected segments at the switch/firewall level — do NOT power off hosts (preserves memory artifacts)
- Disable compromised accounts and force enterprise-wide credential resets, prioritizing privileged/service accounts
- Block known exfil destinations at egress; enable TLS inspection exceptions only as needed
- Snapshot forensic images of the initial access vector (VPN gateway, RDP host, RMM server) BEFORE remediation
- Verify backup integrity from an isolated console — assume the attacker's hands touched backup infrastructure
- Engage IR retainer and counsel before any negotiation consideration; do not contact the gang directly
5. Hardening Recommendations
Immediate (24 Hours)
- Patch edge devices now: Check Point Security Gateway (CVE-2026-50751), Cisco FMC (CVE-2026-20131). If patching is blocked, disable IKEv1 and restrict management-plane access to a jump host
- Audit RMM tooling: Inventory every instance of ScreenConnect-class remote access software; remove unauthorized instances (CVE-2024-1708); enforce MFA on vendor consoles
- Disable legacy Exchange attack surface or apply mitigations for CVE-2023-21529; pull Exchange off direct internet exposure
- Block RDP at the perimeter — no exceptions; require VPN + MFA + NLA for all remote administration
- Enable tamper protection on all EDR agents and alert on any sensor stop event
- Deploy the Sigma rules and KQL query above to your SIEM and run a retro-hunt over the last 30 days
Short-Term (2 Weeks)
- Segment OT/production networks from corporate IT with deny-by-default east-west rules — manufacturing victims consistently fall to flat-network lateral movement
- Implement egress filtering with data-volume alerting (>1GB/hour to unsanctioned destinations triggers investigation)
- Move to immutable, off-network backups (3-2-1-1-0) with an isolated recovery environment and tested restore runbooks
- Enforce phishing-resistant MFA (FIDO2) for all remote access and privileged accounts
- Deploy honey credentials and canary file shares on file servers — ransomware crews touch these during staging, giving you a pre-detonation tripwire
- Review supply-chain exposure given the Micro-Comm compromise: if you are a utility or critical-infrastructure operator using third-party telemetry/SCADA monitoring vendors, demand incident disclosure and rotate any shared credentials
Analyst Assessment
BARRACUDA's current wave reflects mature affiliate-driven tradecraft: edge-device exploitation for entry, RMM abuse for SMB targets, 1–2 week dwell time, and staged exfiltration before detonation. The APAC tilt and the compromise of a utility-monitoring technology vendor are the two developments to watch — the latter carries downstream risk that extends well beyond the named victim. Organizations matching this victim profile (mid-market manufacturing, SMB healthcare, industrial technology vendors) should treat the next 14 days as an elevated threat window and prioritize retro-hunting over the CVE-2026-50751 exposure window (June 2026–present).
This briefing was produced from live monitoring of criminal leak site infrastructure. Victim names are reported as published by the threat actor and do not constitute confirmation of compromise by Security Arsenal.
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.