Back to Intelligence

CVE-2026-105133 & CVE-2026-105134: AhsayCBS Exploited to Deploy Web Shells and XMRig Miners — Detection and Remediation Guide

SA
Security Arsenal Team
October 15, 2026
12 min read

Singapore-based Ahsay Backup has released new security updates for AhsayCBS (Cloud Backup Suite) after it was determined that earlier patches for two vulnerabilities — CVE-2026-105133 and CVE-2026-105134 — were incomplete. Threat actors have already been observed exploiting this flaw chain in the wild to deploy web shells and XMRig cryptocurrency miners on vulnerable backup servers.

This should set off alarms for every organization running AhsayCBS. Backup infrastructure is a crown-jewel target: it holds copies of your most sensitive data, it often runs with elevated privileges, and it is frequently excluded from the aggressive EDR and hardening policies applied elsewhere precisely because teams fear breaking backup jobs. Attackers understand this. A web shell on a backup server is not just a persistence mechanism — it is a staging point for data theft, ransomware preparation, and backup destruction ahead of an encryption event.

The fact that these are re-fixes for previously incomplete patches matters. If your organization applied the original vendor update and moved on, there is a high probability you are still exposed. Treat this as an unpatched environment until you have verified the new build is deployed.

Technical Analysis

Affected Product

  • Product: AhsayCBS (Cloud Backup Suite), the centralized management server component of Ahsay's backup platform
  • Vendor: Ahsay Backup (Singapore)
  • Deployment models: On-premises and MSP-hosted backup servers, commonly running on Windows Server and Linux, exposing web management interfaces on TCP 443/8443 by default
  • CVEs: CVE-2026-105133 and CVE-2026-105134

Attack Chain

Based on the vendor and reporting, the two vulnerabilities are chained by attackers:

  1. CVE-2026-105133 is leveraged to sidestep authentication on the AhsayCBS web console, giving an unauthenticated remote attacker access to functionality that should sit behind the login boundary.
  2. CVE-2026-105134 is then used to execute arbitrary commands on the underlying operating system, effectively converting an authentication bypass into full remote code execution on the backup server.

Post-exploitation behavior observed in the wild follows a familiar playbook:

  • Web shell deployment into web-accessible directories served by the AhsayCBS application, giving the attacker durable, re-entrant access even if the original entry point is closed. Because AhsayCBS is a Java-based application, expect JSP web shells dropped under the application's web directories (e.g., paths under the AhsayCBS installation such as webapps or console-served directories).
  • XMRig cryptocurrency miner deployment, indicating financially motivated actors monetizing access opportunistically. XMRig on a backup server is also a tripwire: if you find a miner, assume a web shell and full command execution preceded it, and investigate accordingly — miners are rarely the endgame.

Exploitation Status

  • Confirmed active exploitation in the wild. This is not a theoretical issue.
  • Prior patches were incomplete, meaning environments that patched against the initial advisory may still be vulnerable. Verification of the current fixed build is mandatory.
  • Check the CISA Known Exploited Vulnerabilities (KEV) catalog and the vendor advisory for the latest status; given confirmed exploitation, KEV inclusion — with its attendant federal remediation deadlines — is a realistic outcome and a good proxy for urgency in private-sector prioritization.

Why Backup Servers Are High-Value Targets

From an IR perspective, AhsayCBS sits in a dangerous intersection: internet-reachable management interface (frequently exposed for MSP remote administration), broad local privileges (backup agents and services routinely run as SYSTEM or root to read all files), and trust relationships with every protected endpoint. Ransomware operators specifically hunt backup consoles to delete or encrypt backups before detonating payloads. Even if the current campaign is miner-focused, the access being sold or reused later for ransomware staging is a standard progression.

Detection & Response

The detections below target the observable behaviors described in this campaign: the AhsayCBS service spawning unexpected child processes, web shell files appearing in application web directories, and XMRig miner execution. Tune the installation paths to match your environment before deployment.

Sigma Rules

The first rule catches the core post-exploitation behavior: the AhsayCBS Java/service process spawning command interpreters — the hallmark of CVE-2026-105134 command execution. The second catches web shell file creation in AhsayCBS web directories. The third catches XMRig deployment.

YAML
---
title: AhsayCBS Process Spawning Command Shell or Script Interpreter
id: 3f8a1c94-7b2e-4d5a-9c61-0e4f8a2b6d71
status: experimental
description: Detects the AhsayCBS Java/service process spawning cmd.exe, PowerShell, or shell interpreters, consistent with post-authentication-bypass command execution via CVE-2026-105133/CVE-2026-105134.
references:
  - https://thehackernews.com/2026/10/ahsaycbs-flaws-exploited-to-deploy-web.html
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/10/15
tags:
  - attack.execution
  - attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|contains:
      - '\AhsayCBS\'
      - '\cbs\'
    ParentImage|endswith:
      - '\java.exe'
      - '\javaw.exe'
      - '\cbs.exe'
      - '\cbsr.exe'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\mshta.exe'
      - '\rundll32.exe'
      - '\certutil.exe'
      - '\bitsadmin.exe'
      - '\curl.exe'
  condition: selection_parent and selection_child
falsepositives:
  - AhsayCBS pre/post backup job scripts legitimately invoking cmd.exe or PowerShell — baseline scheduled job behavior and exclude known administrative script paths
level: high
---
title: Web Shell File Created in AhsayCBS Web Directory
id: 8c2d5e17-4a9b-4f38-b6c2-7d1e9a3f5b08
status: experimental
description: Detects creation of JSP or script files within AhsayCBS web-accessible directories, consistent with web shell deployment following exploitation of CVE-2026-105133/CVE-2026-105134.
references:
  - https://thehackernews.com/2026/10/ahsaycbs-flaws-exploited-to-deploy-web.html
  - https://attack.mitre.org/techniques/T1505/003/
author: Security Arsenal
date: 2026/10/15
tags:
  - attack.persistence
  - attack.t1505.003
logsource:
  category: file_event
  product: windows
detection:
  selection_path:
    TargetFilename|contains:
      - '\AhsayCBS\webapps\'
      - '\AhsayCBS\webapp\'
      - '\AhsayCBS\tomcat\webapps\'
      - '\AhsayCBS\www\'
      - '\AhsayCBS\console\'
  selection_ext:
    TargetFilename|endswith:
      - '.jsp'
      - '.jspx'
      - '.war'
      - '.aspx'
      - '.php'
  condition: selection_path and selection_ext
falsepositives:
  - Legitimate AhsayCBS updates deploying new web application files — correlate with scheduled maintenance windows and verified vendor installer processes
level: critical
---
title: XMRig Cryptocurrency Miner Execution
id: 1e6b9d42-3c7a-4e15-a84f-2b8c6d0e9a43
status: experimental
description: Detects execution artifacts of the XMRig Monero miner, observed being deployed on exploited AhsayCBS servers. Covers process names and common command-line arguments for mining pool configuration.
references:
  - https://thehackernews.com/2026/10/ahsaycbs-flaws-exploited-to-deploy-web.html
  - https://attack.mitre.org/techniques/T1496/
author: Security Arsenal
date: 2026/10/15
tags:
  - attack.impact
  - attack.t1496
logsource:
  category: process_creation
  product: windows
detection:
  selection_name:
    Image|endswith:
      - '\xmrig.exe'
      - '\xmrig-notls.exe'
  selection_cli:
    CommandLine|contains:
      - '--donate-level'
      - '--coin='
      - 'stratum+tcp://'
      - 'stratum+ssl://'
      - 'pool.minexmr'
      - 'xmrpool'
      - 'supportxmr'
      - '--randomx-mode'
  condition: selection_name or selection_cli
falsepositives:
  - None expected in enterprise environments; any hit warrants investigation
level: high

KQL — Microsoft Sentinel / Defender

This query hunts across process creation for AhsayCBS spawning shells, XMRig indicators, and web-shell-like file drops under AhsayCBS directories. It assumes Defender for Endpoint is deployed on backup servers (DeviceProcessEvents / DeviceFileEvents). If you ingest AhsayCBS host logs via Syslog/CEF, the second query covers Linux deployments.

KQL — Microsoft Sentinel / Defender
// Hunt: AhsayCBS post-exploitation — shell spawning, web shell drops, XMRig
let Lookback = 14d;
let SuspiciousChildren = dynamic(["cmd.exe","powershell.exe","pwsh.exe","wscript.exe","cscript.exe","mshta.exe","rundll32.exe","certutil.exe","bitsadmin.exe","curl.exe"]);
let MinerIndicators = dynamic(["xmrig","--donate-level","stratum+tcp://","stratum+ssl://","pool.minexmr","xmrpool","supportxmr"]);
union
(
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where InitiatingProcessFolderPath has_any ("AhsayCBS", "\\cbs\\")
       or InitiatingProcessFileName has_any ("cbs", "java")
    | where FileName in~ (SuspiciousChildren)
    | project TimeGenerated, DeviceName, Hunt="AhsayCBS spawned shell/script interpreter",
              InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName
),
(
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName has_any (MinerIndicators) or ProcessCommandLine has_any (MinerIndicators)
    | project TimeGenerated, DeviceName, Hunt="XMRig miner execution",
              InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName
),
(
    DeviceFileEvents
    | where TimeGenerated > ago(Lookback)
    | where FolderPath has_all ("AhsayCBS") and FolderPath has_any ("webapps", "webapp", "tomcat", "www", "console")
    | where FileName endswith ".jsp" or FileName endswith ".jspx" or FileName endswith ".war"
        or FileName endswith ".aspx" or FileName endswith ".php"
    | project TimeGenerated, DeviceName, Hunt="Web shell file in AhsayCBS web directory",
              FolderPath, FileName, InitiatingProcessFileName, InitiatingProcessCommandLine
)
| order by TimeGenerated desc;

// Linux AhsayCBS hosts via Syslog ingestion — shells spawned by java/cbs and miner indicators
Syslog
| where TimeGenerated > ago(14d)
| where ProcessName in~ ("java", "cbs")
   or SyslogMessage has_any ("/bin/sh", "/bin/bash", "wget ", "curl ", "xmrig", "stratum+tcp")
| where SyslogMessage has_any ("AhsayCBS", "xmrig", "stratum+tcp", "/bin/sh", "/bin/bash")
| project TimeGenerated, Computer, ProcessName, SyslogMessage
| order by TimeGenerated desc;

Velociraptor VQL

Use this artifact for rapid triage of suspected AhsayCBS hosts — it pulls suspicious child processes, recently created script files in web directories, and listening/outbound network connections in one pass.

VQL — Velociraptor
-- AhsayCBS compromise triage: shells spawned by service, web shell drops, miner processes
LET procs = SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(cmd\.exe|powershell|wscript|mshta|certutil|bitsadmin|xmrig|stratum\+tcp|donate-level)'
   OR Name =~ '(?i)(xmrig|cmd\.exe|powershell\.exe)'

LET webshells = SELECT FullPath AS ShellPath, Size, Mtime AS Modified
FROM glob(globs=['C:/AhsayCBS/webapps/**/*.jsp', 'C:/AhsayCBS/webapps/**/*.jspx',
                 'C:/AhsayCBS/**/webapps/**/*.war', 'C:/AhsayCBS/www/**/*.jsp',
                 '/opt/ahsaycbs/webapps/**/*.jsp', '/usr/local/ahsaycbs/webapps/**/*.jsp'],
          accessor='auto')
WHERE Modified > (now() - 30 * 24 * 3600)

LET conns = SELECT Pid, Name, RemoteAddress, RemotePort, Status
FROM netstat()
WHERE RemotePort IN (3333, 4444, 5555, 7777, 14444)
   OR RemoteAddress =~ '(?i)(minexmr|xmrpool|supportxmr|nanopool|hashvault)'

SELECT * FROM procs
UNION ALL
SELECT NULL AS Pid, NULL AS Ppid, 'WEBSHELL_FILE' AS Name, ShellPath AS CommandLine,
       NULL AS Exe, NULL AS Username, Modified AS CreateTime FROM webshells
UNION ALL
SELECT Pid, NULL AS Ppid, 'MINER_CONNECTION: ' + Name AS Name,
       RemoteAddress + ':' + RemotePort AS CommandLine, NULL AS Exe, NULL AS Username, NULL AS CreateTime FROM conns

Remediation & Verification Script

Run this on Windows-based AhsayCBS servers to verify the installed build, check for known web shell artifacts, and look for miner persistence. It is read-only — it does not modify the system — so it is safe to run before change-control-approved patching.

PowerShell
# AhsayCBS CVE-2026-105133 / CVE-2026-105134 verification and triage script
# Run elevated. Read-only: collects evidence, does not remediate.

$Report = @()

# 1. Verify AhsayCBS installation and version
$cbsPath = "C:\Program Files\AhsayCBS"
if (-not (Test-Path $cbsPath)) { $cbsPath = "C:\AhsayCBS" }
if (Test-Path $cbsPath) {
    $ver = Get-ChildItem $cbsPath -Recurse -Filter "*.properties" -ErrorAction SilentlyContinue |
           Select-String -Pattern "version" -ErrorAction SilentlyContinue | Select-Object -First 5
    $Report += "[INFO] AhsayCBS found at $cbsPath"
    $Report += $ver | ForEach-Object { "[INFO] $($_.Line)" }
} else {
    $Report += "[WARN] AhsayCBS not found in default paths - verify install location"
}

# 2. Scan web directories for recently modified script files (potential web shells)
$webDirs = @("$cbsPath\webapps", "$cbsPath\webapp", "$cbsPath\www", "$cbsPath\console")
foreach ($dir in $webDirs) {
    if (Test-Path $dir) {
        Get-ChildItem $dir -Recurse -Include *.jsp,*.jspx,*.war,*.aspx,*.php -ErrorAction SilentlyContinue |
        Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-30) } |
        ForEach-Object { $Report += "[ALERT] Recently modified web file: $($_.FullName) ($($_.LastWriteTime))" }
    }
}

# 3. Check for miner processes and suspicious children of AhsayCBS services
Get-Process | Where-Object { $_.Name -match 'xmrig|minerd|cryptonight' } |
    ForEach-Object { $Report += "[ALERT] Miner process running: $($_.Name) PID $($_.Id) Path $($_.Path)" }

# 4. Check persistence locations commonly abused by miner/web-shell campaigns
$runKeys = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run",
           "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run"
foreach ($key in $runKeys) {
    Get-ItemProperty $key -ErrorAction SilentlyContinue | ForEach-Object {
        $_.PSObject.Properties | Where-Object { $_.Value -match 'xmrig|AppData|Temp' } |
        ForEach-Object { $Report += "[ALERT] Suspicious Run key: $($_.Name) = $($_.Value)" }
    }
}
Get-ScheduledTask | Where-Object { $_.Actions.Execute -match 'powershell|cmd|xmrig' -and
    $_.Actions.Arguments -match 'EncodedCommand|stratum|donate' } |
    ForEach-Object { $Report += "[ALERT] Suspicious scheduled task: $($_.TaskName)" }

# 5. Check listening ports for unexpected services
Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue |
    Where-Object { $_.LocalPort -notin 80,443,135,445,3389,5985,8443 } |
    ForEach-Object {
        $proc = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
        $Report += "[INFO] Listener $($_.LocalPort) -> $($proc.Name) ($($proc.Path))"
    }

$Report | Out-File "C:\AhsayCBS_Triage_$(Get-Date -Format yyyyMMdd_HHmm).txt"
$Report
Write-Host "`nTriage complete. Review ALERT lines, then apply the latest AhsayCBS build per vendor advisory."

Remediation

  1. Apply the new vendor fixes immediately. The previous AhsayCBS patches for CVE-2026-105133 and CVE-2026-105134 were incomplete — do not assume a previously "patched" server is safe. Download the current fixed build from Ahsay's official channels and apply it to every AhsayCBS server, including replication and standby instances. Reference the vendor advisory at https://www.ahsay.com (navigate to Support → Security Advisories) and the original reporting at https://thehackernews.com/2026/10/ahsaycbs-flaws-exploited-to-deploy-web.html for build-specific guidance. Monitor the CISA KEV catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) for inclusion and associated remediation deadlines.

  2. Remove internet exposure of the AhsayCBS management console. The console should never be directly reachable from the internet. Place it behind a VPN or zero-trust access gateway, restrict by source IP allowlist to known admin and agent networks, and block inbound access to the management ports (443/8443) from untrusted networks at the perimeter.

  3. Hunt before you patch. Patching does not remove existing implants. Before and after applying the update, sweep every AhsayCBS host for web shells in web-accessible directories, miner processes, and unexpected child processes of the AhsayCBS service using the detections above. If you find a web shell, treat it as a full compromise: isolate the host, preserve forensic images, rotate all credentials the server could access (backup encryption keys, service accounts, storage credentials), and scope for lateral movement — backup servers touch everything.

  4. Harden the service account and host. Run AhsayCBS under a least-privilege service account where the architecture permits, apply EDR with tamper protection to backup servers (no exclusions for the AhsayCBS directories in process-monitoring — only in on-access scanning if performance demands it), and enable command-line process auditing (Windows Event 4688 with command line, or auditd on Linux) so the Sigma logic above has telemetry to work with.

  5. Validate your backups' integrity and recoverability. Given that backup infrastructure is the target, confirm backup jobs are completing, test a restore, and ensure at least one offline or immutable backup copy exists that the AhsayCBS server itself cannot modify or delete.

  6. For MSPs running AhsayCBS multi-tenant: a single compromised CBS instance exposes every tenant's backup data. Prioritize these servers above all others, notify tenants per your contractual obligations if compromise is confirmed, and audit API keys and tenant credentials after patching.

Bottom Line

An authentication-bypass-to-RCE chain on backup infrastructure, confirmed exploited in the wild, with incomplete prior patches — this is the definition of a patch-and-hunt emergency. Deploy the new AhsayCBS fixes, verify with the triage script and detections above that no web shell or miner preceded the patch, and permanently remove direct internet exposure from your backup consoles. The organizations that get hurt here will be the ones that patched the original advisory months ago and assumed the risk was closed.

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.