Skip to navigation

Threat reportThreat IntelligenceTL-2026-2868

Attackers Abuse Microsoft SQL Server xp_cmdshell as Command and Base64 Data-Exfiltration Channel in Viva Aerobus-Linked Intrusion

highACTIVE

ThreatMon found an unauthenticated attacker staging/loot server (151.243.232.123) exposing a 17-item post-exploitation toolkit used against a Microsoft SQL Server in a Viva Aerobus-linked environment between 2026-09-25 and 2026-09-29. The actors ran OS commands and encoded PowerShell through xp_cmdshell, returned file contents as Base64 chunks in SQL query output, harvested credentials (Mimikatz, Credential Manager, browser, SSMS/DPAPI) and prepared lateral movement; the initial access vector is unknown and no downstream compromise or passenger-data theft is confirmed.

Key facts

IdentifiersTL-2026-2868
Also known asViva Aerobus-linked MSSQL intrusion, artex toolkit
SeverityHIGH
First disclosed
Affected productsMicrosoft SQL Server (xp_cmdshell enabled)
MalwareMimiKatz
ToolsMimikatz, cmd - S0106
MITRE ATT&CK techniquesT1003 OS Credential Dumping, T1005 Data from Local System, T1021.002 Remote Services: SMB/Windows Admin Shares, T1027 Obfuscated Files or Information, T1059.001 Command and Scripting Interpreter: PowerShell, T1059.003 Command and Scripting Interpreter: Windows Command Shell, T1110.003 Brute Force: Password Spraying, T1132.001 Data Encoding: Standard Encoding, T1505.001 Server Software Component: SQL Stored Procedures, T1552.001 Unsecured Credentials: Credentials In Files, T1555.003 Credentials from Password Stores: Credentials from Web Browsers, T1555.004 Credentials from Password Stores: Windows Credential Manager
MotivationUNKNOWN
Target sectorsaviation, transport
Target regionsmexico
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-10-03, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2868 across Splunk SPL, Microsoft KQL and Sigma, covering 20 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: SQL Server xp_cmdshell Enabled via sp_configure — Exploitation Phase

Detects SQL Server configuration-change event 15457 showing xp_cmdshell switched from 0 to 1. The artex toolkit relies on xp_cmdshell to run OS commands and encoded PowerShell under the SQL Server service account, so enablement is the earliest reliable host-side signal that a database session is being turned into an execution platform. Also matches SQL Server Audit events (33205) whose statement text invokes xp_cmdshell, flagging the cmd.exe / encoded-PowerShell execution itself.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1505.001, T1059.003, T1059.001
  • Data sources: windows_application_log, mssql_error_log
  • Severity: high
  • Confidence: high

Splunk SPL

index=windows sourcetype="WinEventLog:Application" (SourceName="MSSQLSERVER" OR SourceName="MSSQL$*") (EventCode=15457 OR EventCode=33205) Message="*xp_cmdshell*"
``` 15457 = config option changed ('from 0 to 1' = xp_cmdshell switched ON); 33205 = SQL Server Audit event whose statement runs xp_cmdshell ```
| where EventCode=33205 OR match(Message, "from 0 to 1")
| eval signal=case(EventCode=15457,"xp_cmdshell_enabled",match(Message,"(?i)powershell|-enc"),"xp_cmdshell_exec_powershell",match(Message,"(?i)cmd(\.exe)?\s+/c"),"xp_cmdshell_exec_cmd",true(),"xp_cmdshell_exec")
| stats count min(_time) as first_seen max(_time) as last_seen values(signal) as signals values(Message) as messages by host SourceName
| convert ctime(first_seen) ctime(last_seen)

Microsoft KQL

Event
| where TimeGenerated > ago(24h)
| where EventLog == "Application" and EventID in (15457, 33205)
| where Source startswith "MSSQL"
| where RenderedDescription has "xp_cmdshell"
| where EventID == 33205 or RenderedDescription has "from 0 to 1"
| extend Signal = case(EventID == 15457, "xp_cmdshell_enabled", RenderedDescription has_any ("powershell", "-enc"), "xp_cmdshell_exec_powershell", RenderedDescription has "cmd", "xp_cmdshell_exec_cmd", "xp_cmdshell_exec")
| project TimeGenerated, Computer, Source, EventID, Signal, RenderedDescription

Sigma

title: SQL Server xp_cmdshell Enabled via sp_configure
id: 7c1e4a52-3b0d-4f6e-9a21-5d8c0b7e1f31
status: experimental
description: Detects SQL Server event 15457 reporting that the xp_cmdshell configuration option was changed from 0 to 1, a prerequisite for OS command execution through the database engine.
references:
  - https://threatmon.io/an-open-server-an-exposed-toolkit-inside-a-viva-aerobus-linked-intrusion/
  - https://attack.mitre.org/techniques/T1505/001/
author: Threadlinqs Team
date: 2026/10/03
tags:
  - attack.persistence
  - attack.execution
  - attack.t1505.001
  - attack.t1059.003
  - attack.t1059.001
logsource:
  product: windows
  service: application
detection:
  selection_enable:
    Provider_Name|startswith: 'MSSQL'
    EventID: 15457
  selection_exec:
    Provider_Name|startswith: 'MSSQL'
    EventID: 33205
  keywords_option:
    - 'xp_cmdshell'
  keywords_enable:
    - 'from 0 to 1'
  condition: (selection_enable and keywords_option and keywords_enable) or (selection_exec and keywords_option)
falsepositives:
  - Database administrators enabling xp_cmdshell during approved maintenance or legacy application deployment
level: high

Known false positives:

  • Approved DBA maintenance or a legacy application that legitimately requires xp_cmdshell

Tuning notes: Correlate with a change ticket and the login that ran sp_configure; allow-list known DBA change windows. Event 15457 is only logged when the SQL Server error log is forwarded to the Windows Application log, so confirm forwarding is on. Event 33205 (execution branch) only appears when a SQL Server Audit capturing BATCH_COMPLETED_GROUP or SCHEMA_OBJECT_CHANGE_GROUP writes to the Application log; scope the audit filter to statements containing xp_cmdshell to limit volume.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • sqlservr.exe Spawning cmd.exe, PowerShell or LOLBins — Exploitation Phase · unlock with TL Creds
  • Mimikatz Execution, LSASS Dump and Credential Output Files — Post-Exploitation Phase · unlock with TL Creds
  • SQL Server Password Spraying — Failed Logins Across Many Accounts or Servers — Lateral Movement Phase · unlock with TL Creds
  • Base64-Encoded Commands and Chunked Data Under SQL Server Process — Exploitation Phase · unlock with TL Creds
  • artex Staging Directory and Toolkit File Creation on Windows Host — Post-Exploitation Phase · unlock with TL Creds
  • SQL Server Admin-Share Access, SQL Spray Scripts and Base64 Exfil Utilities — Lateral Movement Phase · unlock with TL Creds
  • Credential Manager, Vault and Browser Credential Extraction Scripts — Post-Exploitation Phase · unlock with TL Creds
  • SQL Server Outbound to Staging Server [indicator] or Download Cradle — C2 / Ingress Phase · unlock with TL Creds

Indicators of compromise

As of 2026-10-03, Threadlinqs Intelligence tracks 20 indicators of compromise for TL-2026-2868.

Sample indicators (3 of 20)

  • IP address: 151.243.232[.]123
  • File hash: c38f49ba68b891bb476510704cddf080798f3c70075e2a517e98e04e833f64fa
  • File hash: 33aeaaa3d57b7785ef2be5b8ccd39d534b8af50e0cd32a5036fdb64601a52fc9

Defanged, TLP:CLEAR. Full set of 20 indicators: unlock with TL Creds.

20 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Between 2026-09-25 and 2026-09-29, a Microsoft SQL Server in an environment linked to Mexican airline Viva Aerobus was used as an execution platform and data channel. ThreatMon identified the attacker's exposed staging and loot server at 151.243.232.123 during routine threat hunting. The server was an unauthenticated HTTP host with open directory listings, so unrelated internet hosts could enumerate loot directories and retrieve the offensive tooling. ThreatMon's public report (published 2026-10-01) is intentionally sanitized; victim IPs, hostnames, user identities, credentials, OAuth identifiers and partner configurations are withheld.

Execution: recovered scripts use the SQL Server xp_cmdshell extended stored procedure, when enabled, to run Windows commands (cmd.exe) and Base64-encoded PowerShell under the SQL Server service account. Rather than deploy separate C2 infrastructure, the tooling (exfil.py, upload.py) reads files, splits them into chunks, Base64-encodes them and returns them through SQL query output, turning the database session into both a command and an exfiltration channel. The working directory on the victim host was C:\Windows\Temp\artex. Timeline per ThreatMon: on 2026-09-25 at 16:20 a victim-side MSSQL server retrieved a payload from the staging server; at 16:21-16:23 an unrelated external host enumerated the staging server and its loot directories; at 16:30 self-test requests came from the staging host; at 18:04-18:05 additional external hosts retrieved tooling.

Credential access and lateral-movement preparation: artifacts include Mimikatz output (mdump.txt), cred_dec.txt, scripts for Windows credential store, Credential Manager/Vault and browser credential extraction (cred_dump.ps1, cred_enum.ps1, vault.cmd, vtest.ps1, chrome_dump.ps1), SSMS connection history, database usernames and DPAPI-protected saved passwords. sqlspray.ps1 and mssqltest.ps1 tested username/password combinations against other SQL targets (checking login identity and server-role membership), and the utilities also checked access to SMB administrative shares. Source code and configuration files referencing SQL connections, OAuth, mail, SFTP, payment and reporting integrations were collected (loot/, loot2/).

Limits of the evidence: the investigation did not establish how the attackers first entered the environment; no named malware family was identified (it is described as a toolkit, not a single implant); no link to other known campaigns was established; and there is no evidence of successful access to additional systems or theft of sensitive passenger, payment or business data. One ThreatMon page lists the handles Blackhatsect0r and DXQRTXX in a threat-actor field, but the sources provide no attribution narrative, so attribution is recorded as Unknown/low confidence.

MITRE ATT&CK techniques by tactic:

Credential Access

T1003 OS Credential Dumping; T1110.003 Brute Force: Password Spraying; T1552.001 Unsecured Credentials: Credentials In Files; T1555.003 Credentials from Password Stores: Credentials from Web Browsers; T1555.004 Credentials from Password Stores: Windows Credential Manager

Collection

T1005 Data from Local System

Lateral Movement

T1021.002 Remote Services: SMB/Windows Admin Shares

Defense Evasion

T1027 Obfuscated Files or Information

Execution

T1059.001 Command and Scripting Interpreter: PowerShell; T1059.003 Command and Scripting Interpreter: Windows Command Shell

Command and Control

T1132.001 Data Encoding: Standard Encoding

Persistence

T1505.001 Server Software Component: SQL Stored Procedures

Remediation

Immediate actions

  • Review historical network telemetry for connections to 151.243.232.123 and block it at the perimeter
  • Search endpoints for the published SHA256 hashes and for the C:\Windows\Temp\artex directory
  • Investigate unexpected xp_cmdshell activation (sp_configure 'xp_cmdshell') and any use of it
  • Alert on cmd.exe and powershell.exe (especially encoded commands) spawned by sqlservr.exe or the SQL Server service account
  • Assume all credentials that reached the exposed attacker infrastructure are compromised and rotate database, OAuth, mail and SFTP secrets

Workarounds

  • Disable xp_cmdshell where it is not required
  • Restrict SQL Server and SMB administrative-share access between hosts

Longer-term hardening

  • Run SQL Server service accounts with least privilege and restrict their outbound network access
  • Treat SSMS metadata (connection history, saved credentials, DPAPI-protected passwords) as sensitive credential-adjacent data
  • Do not store credentials or integration secrets in source code and configuration files
  • Monitor for SQL logins from unexpected hosts and for password spraying across SQL servers

Affected and fixed versions

  • Microsoft — SQL Server (xp_cmdshell enabled)

Timeline

  • At 18:04-18:05 additional external hosts retrieved post-exploitation tools and artifacts from the open server
  • At 16:30 self-test requests were observed originating from the staging host
  • At 16:21-16:23 an unrelated external host enumerated the unauthenticated staging server and its loot directories
  • At 16:20 a victim-side MSSQL server retrieved a payload from the attacker staging server locked-ioc-5; the intrusion window runs 2026-09-25 to 2026-09-29
  • End of the activity window ThreatMon associates with the exposed server (xp_cmdshell execution, credential harvesting, lateral-movement preparation)
  • ThreatMon published a sanitized report on the exposed staging server and 17-item toolkit found during routine threat hunting
  • Cyber Security News and other outlets reported the SQL Server command and exfiltration channel; initial access remains unknown and no passenger-data theft is confirmed

Sources cited

Previous and next in threat intel

Further reading

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats