T1011.001 Splunk · SPL

Detect Exfiltration Over Bluetooth in Splunk

Adversaries may attempt to exfiltrate data over Bluetooth rather than the command and control channel. If the command and control network is a wired Internet connection, an adversary may opt to exfiltrate data using a Bluetooth communication channel. Adversaries may choose to do this if they have sufficient access and proximity. Bluetooth connections might not be secured or defended as well as the primary Internet-connected channel because it is not routed through the same enterprise network. Real-world examples include the Flame malware's BeetleJuice module, which transmitted encoded data over Bluetooth and acted as a Bluetooth beacon to identify nearby Bluetooth-enabled devices.

MITRE ATT&CK

Tactic
Exfiltration
Technique
T1011 Exfiltration Over Other Network Medium
Sub-technique
T1011.001 Exfiltration Over Bluetooth
Canonical reference
https://attack.mitre.org/techniques/T1011/001/

SPL Detection Query

Splunk (SPL)
spl
index=wineventlog (sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" OR sourcetype="WinEventLog:Security")
| eval EventCode=coalesce(EventCode, event_id)
| where EventCode IN ("1", "11", "12", "13", 1, 11, 12, 13, 4688, 4657)
(
  [search sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
   (Image="*\\fsquirt.exe"
   OR Image="*\\btattach"
   OR Image="*\\btmgmt"
   OR Image="*\\hciconfig"
   OR Image="*\\hcitool"
   OR Image="*\\hcidump"
   OR Image="*\\bluetoothctl"
   OR Image="*\\rfcomm"
   OR Image="*\\obexftp"
   OR Image="*\\sdptool"
   OR CommandLine="*bluetooth*"
   OR CommandLine="*rfcomm*"
   OR CommandLine="*obex*"
   OR CommandLine="*hcitool*"
   OR CommandLine="*hciconfig*"
   OR CommandLine="*btmgmt*"
   OR CommandLine="*bluetoothctl*")
  | eval DetectionType="Bluetooth Tool Execution"]
)
OR
(
  [search sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" (EventCode=12 OR EventCode=13)
   (TargetObject="*Bluetooth*"
   OR TargetObject="*BTHPORT*"
   OR TargetObject="*BTHENUM*"
   OR TargetObject="*BthLE*"
   OR TargetObject="*RFCOMM*")
  | eval DetectionType="Bluetooth Registry Modification"]
)
OR
(
  [search sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=11
   (TargetFilename="*bluetooth*"
   OR TargetFilename="*rfcomm*"
   OR TargetFilename="*obex*"
   OR TargetFilename="*btooth*")
  | eval DetectionType="Bluetooth File Activity"]
)
| eval Image=coalesce(Image, NewProcessName)
| eval CommandLine=coalesce(CommandLine, CommandLine)
| eval User=coalesce(User, SubjectUserName)
| table _time, host, User, Image, CommandLine, ParentImage, ParentCommandLine, TargetObject, TargetFilename, DetectionType
| sort - _time
high severity medium confidence

Detects potential Bluetooth exfiltration activity using Sysmon Event ID 1 (Process Creation), Event ID 11 (File Create), and Event IDs 12/13 (Registry events). Identifies execution of known Bluetooth utilities such as hcitool, hciconfig, rfcomm, obexftp, bluetoothctl, and fsquirt.exe; Bluetooth-related registry key modifications under BTHPORT, BTHENUM, or Bluetooth driver paths; and file creation events in Bluetooth-related directories. Covers both Windows (fsquirt.exe) and Linux-style tools that may appear on managed endpoints.

Data Sources

Process: Process CreationFile: File CreationWindows Registry: Registry Key ModificationSysmon Event ID 1Sysmon Event ID 11Sysmon Event ID 12/13

Required Sourcetypes

XmlWinEventLog:Microsoft-Windows-Sysmon/OperationalWinEventLog:Security

False Positives & Tuning

  • IT administrators using Bluetooth utilities for device pairing, diagnostics, or inventory on managed endpoints
  • Developers building Bluetooth applications testing functionality on their workstations
  • Windows built-in Bluetooth file transfer wizard (fsquirt.exe) used by employees for legitimate personal file transfers
  • Bluetooth peripheral management tools (headset software, mouse/keyboard pairing utilities) running in background
Download portable Sigma rule (.yml)

Other platforms for T1011.001


Testing Methodology

Validate this detection against 5 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Enumerate Bluetooth Devices on Windows

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe and CommandLine containing 'Get-PnpDevice' and 'Bluetooth'. PowerShell ScriptBlock Log Event ID 4104 with the full enumeration command. No registry modification events, but PnpDevice queries may appear in Windows Plug and Play logs.

  2. Test 2Linux Bluetooth Device Scan with hcitool

    Expected signal: Linux auditd: execve syscall for hcitool with arguments 'scan' and 'lescan'. Syslog/daemon.log: bluetoothd activity logs showing scan initiation. If auditd is configured with execve monitoring: type=EXECVE msg= records with a0='hcitool' a1='scan'. Sysmon for Linux Event ID 1 if deployed.

  3. Test 3Transfer File via OBEX over Bluetooth on Linux

    Expected signal: Linux auditd/Sysmon: execve event for obexftp with arguments including '--bluetooth', a MAC address, and '--put' with the file path. File creation event for /tmp/bt_test_exfil.txt. The process will exit with an error but telemetry is generated. Syslog may show bluetoothd connection attempt to the specified MAC address.

  4. Test 4Python Bluetooth Exfiltration Script Execution (Windows/Linux)

    Expected signal: Sysmon Event ID 1: Process Create for python3.exe or python.exe with CommandLine referencing Bluetooth. Child process creation: powershell.exe spawned by python with 'Get-PnpDevice -Class Bluetooth'. Sysmon Event ID 1 for the child powershell.exe. PowerShell ScriptBlock Log Event ID 4104 for the enumeration command.

  5. Test 5Bluetooth Registry Key Inspection for Paired Devices

    Expected signal: Sysmon Event ID 1: Process Create for reg.exe with query arguments targeting BTHPORT. If PowerShell fallback executes: Sysmon Event ID 1 for powershell.exe with BTHPORT in CommandLine. Sysmon Event ID 12 (Registry key access) for HKLM\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices. PowerShell ScriptBlock Log Event ID 4104.

Unlock Pro Content

Get the full detection package for T1011.001 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections