Skip to navigation

Threat reportVulnerabilityTL-2026-1699

KARR Bluetooth Vulnerability Lets Nearby Attackers Unlock and Immobilize Over 2 Million Cars

highPATCHED

A single Bluetooth Low Energy (BLE) authentication key hardcoded in plaintext inside Acrisure Protection Group's KARR/SWDS aftermarket car alarm app is shared across every deployed unit, letting anyone within ~5 yards impersonate the legitimate app to unlock doors, sound horns/lights, and immobilize the engine on any of an estimated 2.2 million affected vehicles.

Key facts

IdentifiersTL-2026-1699
Also known asBLE Theft Auto
SeverityHIGH
Affected productsAcrisure Protection Group KARR / SWDS (SouthWest Dealer Services) Aftermarket Vehicle Security & Remote Immobilizer System (BLE-based); Rockledge Aftermarket BLE-based vehicle remote-control / anti-theft device
Weaknesses (CWE)CWE-798, CWE-321, CWE-294, CWE-522
ToolsKARR Security PoC Android application, WiGLE
MITRE ATT&CK techniquesT1005 Data from Local System, T1036 Masquerading, T1040 Network Sniffing, T1046 Network Service Discovery, T1095 Non-Application Layer Protocol, T1119 Automated Collection, T1120 Peripheral Device Discovery, T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services, T1529 System Shutdown/Reboot, T1552 Unsecured Credentials, T1567 Exfiltration Over Web Service and 6 more in the attack flow
MotivationFINANCIAL
Target sectorsautomotive, consumer, transport
Target regionsunited states of america, North America, canada, japan
Detection rules9 (1 shown free)
Sources13 cited sources

Detection coverage

As of 2026-07-25, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1699 across Splunk SPL, Microsoft KQL and Sigma, covering 29 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: KARR/SWDS BLE Recon & Companion-App Decompilation Toolchain (Exploitation)

Detects the exploitation-stage tradecraft behind the KARR/SWDS BLE Theft Auto attack: an endpoint spawning APK reverse-engineering tools (jadx, apktool, dex2jar, unzip against a .apk) against a file referencing the KARR/SWDS companion app, immediately followed by a process reading/writing a plaintext string resembling a hardcoded shared authentication key (research.json: 'Shared BLE authentication key extraction from mobile app', CWE-798/CWE-321/CWE-294). This is the step that recovers the single static key every deployed unit shares, enabling downstream impersonation of any KARR/SWDS-equipped vehicle.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1595, T1552, T1005, T1120
  • Data sources: sysmon, edr_process_telemetry, file_integrity_monitoring
  • Severity: high
  • Confidence: medium

Splunk SPL

index=endpoint sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| eval decompile_tool=if(match(lower(process_name), "jadx|apktool|dex2jar|jd-gui|baksmali"), 1, 0)
| where decompile_tool=1 AND (match(lower(CommandLine), "karr") OR match(lower(CommandLine), "swds") OR match(lower(CommandLine), "\.apk"))
| stats earliest(_time) as first_seen latest(_time) as last_seen count by Computer, User, process_name, CommandLine
| join type=left Computer
    [ search index=endpoint sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=11
      | where match(lower(TargetFilename), "auth_key|shared.?key|extracted_key")
      | stats count as key_file_writes by Computer ]
| where key_file_writes > 0
| table first_seen, last_seen, Computer, User, process_name, CommandLine, key_file_writes, count
| sort - first_seen

Microsoft KQL

let decompileTools = dynamic(["jadx", "apktool", "dex2jar", "jd-gui", "baksmali"]);
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FolderPath has_any(decompileTools) or ProcessCommandLine has_any(decompileTools)
| where ProcessCommandLine has_any("karr", "swds", ".apk")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine
| join kind=inner (
    DeviceFileEvents
    | where Timestamp > ago(24h)
    | where FileName has_any("auth_key", "extracted_key", "shared_key")
    | project KeyFileTime = Timestamp, DeviceName, KeyFileName = FileName
) on DeviceName
| where KeyFileTime between (Timestamp .. (Timestamp + 30m))
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, KeyFileTime, KeyFileName
| sort by Timestamp desc

Sigma

title: APK Decompilation Toolchain Targeting KARR/SWDS Companion App
id: 7a1e2c44-1b6f-4a9d-9e2a-3f6c0d8a1101
status: experimental
description: Detects execution of Android APK reverse-engineering tools (jadx, apktool, dex2jar, baksmali) referencing the KARR or SWDS aftermarket vehicle alarm companion app, the precursor step to extracting the hardcoded shared BLE authentication key documented in the BLE Theft Auto research.
references:
    - https://gbhackers.com/karr-bluetooth-vulnerability/
    - https://today.ucsd.edu/story/2-million-cars-with-anti-theft-systems-installed-by-dealers-are-at-higher-risk-of-theft
author: Threadlinqs Team
date: 2026-07-25
tags:
    - attack.reconnaissance
    - attack.t1595
    - attack.credential-access
    - attack.t1552
    - attack.t1120
    - cwe.798
logsource:
    category: process_creation
    product: windows
detection:
    selection_tool:
        Image|endswith:
            - '\jadx.exe'
            - '\apktool.bat'
            - '\dex2jar.bat'
            - '\baksmali.jar'
        CommandLine|contains:
            - 'jadx'
            - 'apktool'
            - 'dex2jar'
    selection_target:
        CommandLine|contains:
            - 'karr'
            - 'swds'
            - '.apk'
    condition: selection_tool and selection_target
falsepositives:
    - Legitimate Android mobile-app security research or QA teams performing routine reverse-engineering of unrelated APKs that happen to reference third-party filenames
    - Automated SAST/mobile-AppSec pipelines that decompile every ingested APK for policy scanning
level: high

Known false positives:

  • Legitimate mobile-AppSec / SAST teams routinely decompiling third-party APKs (including KARR's own) as part of vendor security assessments
  • Automated malware-analysis sandboxes that unpack every ingested APK regardless of vendor

Tuning notes: Scope the decompiler process allow-list to known corporate AppSec workstations/build agents; suppress when the source file hash matches a tracked internal vendor-assessment intake list rather than an unknown/user-downloaded APK.

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)
  • Hardcoded Shared BLE Auth-Key File Access Following App Teardown (Exploitation) · unlock with TL Creds
  • Rapid Multi-Command BLE GATT Replay Sequence (Unlock/Alarm-Disable/Horn/Immobilize) (Post-Exploitation) · unlock with TL Creds
  • Automated Crowdsourced Wireless-Database Querying for Single-Device Location Tracking (C2/Lateral Movement) · unlock with TL Creds
  • Fixed-Pattern BLE Peripheral Scan for Aftermarket Alarm Manufacturer Data (Exploitation) · unlock with TL Creds
  • Silent Engine-Immobilize Command With No Corresponding Owner-App Session (Post-Exploitation) · unlock with TL Creds
  • Outbound Web-Service Exfiltration of BLE Location/Tracking Data to Crowdsourced Signal Database (C2/Lateral Movement) · unlock with TL Creds
  • Masquerading Lookalike KARR/SWDS Companion App Sideload via MDM Inventory (Post-Exploitation) · unlock with TL Creds
  • Scripting Interpreter Opening Local BLE-to-IP Bridge Socket After BLE-Scan Artifact Write (C2/Lateral Movement) · unlock with TL Creds

Indicators of compromise

As of 2026-07-25, Threadlinqs Intelligence tracks 29 indicators of compromise for TL-2026-1699.

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

Technical analysis

UC San Diego researchers privately disclosed the flaw in January 2025; Acrisure shipped an opt-in firmware fix on July 20, 2026, roughly 18 months later, and the team is presenting the research ('BLE Theft Auto') at DEF CON and USENIX Security in August 2026.

KARR (also sold under the SWDS brand — SouthWest Dealer Services, an Acrisure Protection Group subsidiary that handles dealership installations) is a dealer-installed, subscription-based aftermarket vehicle security and remote-immobilizer system. The unit is mounted underneath the dashboard on the driver's side and communicates with an official companion smartphone app over Bluetooth Low Energy to arm/disarm the alarm, lock/unlock doors, sound the horn and lights, and remotely disable the ignition.

Researchers at UC San Diego's Department of Computer Science and Engineering — led by Professor Aaron Schulman with co-first authors Jerry Yu and Yibo Wei, building on Bluetooth-fingerprinting work by alumnus Nishant Bhaskar originating from a 2018 credit-card-skimmer detection project — reverse-engineered the official KARR mobile app and found that every KARR/SWDS unit shares one identical Bluetooth authentication key, stored in plaintext inside the app itself rather than being unique per device or per vehicle. Because the key cannot be changed or rotated, extracting it once from the app grants an attacker the ability to impersonate the legitimate app against any KARR/SWDS-equipped vehicle in Bluetooth range.

The researchers built a proof-of-concept Android application that replays the extracted key to send unauthorized BLE commands. From roughly five yards away, and without smashing a window or touching the vehicle, the PoC can unlock doors, disable the alarm, honk the horn, flash the lights, and — most seriously — prevent a parked vehicle's engine from starting, potentially stranding the driver. The attack executes silently: the vehicle emits only a brief beep and light flicker, and the owner receives no alert that a command was issued. In a live demonstration the team triggered horns and lights across multiple parked vehicles simultaneously ('mayhem mode'). The attack cannot start or drive a moving vehicle.

A compounding design flaw: dormant units — including the roughly one million owners who never opted into (or were unaware of) the paid subscription — still accept a single Bluetooth wake-up command that exposes the same command functionality, meaning an inactive/unsubscribed alarm is exploitable identically to an active one. Separately, KARR/SWDS units continue broadcasting an identifiable BLE signal while the vehicle is running and for up to 10 minutes after shutdown. Because these broadcasts are logged by crowdsourced wireless-signal databases such as WiGLE, an attacker can query a device's identifier over time to reconstruct a vehicle's parking/location history without ever approaching it, creating a stalking and surveillance risk independent of the unlock/immobilize attack.

Using WiGLE data and short field tests (97 active KARR units detected during a single 20-minute drive), the researchers estimate at least 2.2 million vehicles are affected nationwide (1.4 million confirmed), the large majority sold new by Honda, Toyota, Mazda, Ford, and Jeep dealerships across Southern California from 2017 to the present, with secondary distribution into Canada and Japan via the used-car resale market. A second aftermarket manufacturer, Rockledge, was evaluated in the same study; its devices require an attacker to intercept traffic during active use (a man-in-the-middle-style capture) rather than a one-time static key extraction, making it harder to exploit, but Rockledge did not respond to disclosure and the researchers could not fully validate its security.

UC San Diego privately disclosed the vulnerability to Acrisure in January 2025 and separately notified the National Highway Traffic Safety Administration given the vehicle-safety implications. Acrisure did not ship a firmware fix until July 20, 2026 — about 18 months later — and the fix is opt-in: owners must independently discover whether their vehicle has a KARR/SWDS unit (via driver-side window stickers or a small blinking-light module under the dash), install the KARR Security app even if they never subscribed, pair it to the vehicle, and manually apply the update. There is no over-the-air manufacturer recall path since the hardware is third-party/aftermarket, and physical removal requires dashboard disassembly (cutting and reconnecting wires). A KARR/Acrisure spokesperson characterized the flaw as 'highly complex' and 'low risk to customers under real-world conditions'; the lead researcher called it 'probably the worst' car-hacking issue publicly documented to date, noting the attack, once developed, is executable with standard consumer hardware. No CVE identifier has been publicly assigned to this issue. The researchers withheld precise reverse-engineering methodology to reduce replication risk and are presenting the peer-reviewed paper 'BLE Theft Auto: Evaluating the Security of Aftermarket BLE-based Automotive Remote Control Systems' at DEF CON 34 (Aug 9, 2026, Las Vegas) and USENIX Security 2026 (Aug 12, 2026, Baltimore, MD); the work was supported by NSF grant CNS-2239163.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System; T1119 Automated Collection

Defense Evasion

T1036 Masquerading

Credential Access

T1040 Network Sniffing; T1552 Unsecured Credentials

Discovery

T1046 Network Service Discovery; T1120 Peripheral Device Discovery

Command and Control

T1095 Non-Application Layer Protocol

Initial Access

T1190 Exploit Public-Facing Application

Lateral Movement

T1210 Exploitation of Remote Services

Impact

T1529 System Shutdown/Reboot; T1657 Financial Theft

Exfiltration

T1567 Exfiltration Over Web Service

Resource Development

T1587 Develop Capabilities

Reconnaissance

T1591 Gather Victim Org Information; T1592 Gather Victim Host Information; T1595 Active Scanning; T1596 Search Open Technical Databases

Remediation

Patches

  • Acrisure Protection Group firmware update for KARR/SWDS units, released July 20, 2026, distributed exclusively through the KARR Security mobile app

Immediate actions

  • Check the driver-side window for a 'KARR' or 'SWDS' sticker and look underneath the dashboard for a small module with a blinking light to determine whether the vehicle has an affected unit installed
  • Download the official KARR Security mobile app and pair it with the vehicle even if a subscription was never purchased, then apply the July 20, 2026 firmware update immediately
  • If unsure whether a unit is installed, contact the selling dealership directly, since roughly half of owners are unaware a KARR/SWDS system exists on their vehicle

Workarounds

  • Request dealership or installer removal of the KARR/SWDS unit from the dashboard if the firmware update cannot or will not be applied
  • Minimize time parked in extended, unattended public locations where the ~5-yard BLE proximity attack and passive location-tracking risk are most exploitable

Longer-term hardening

  • Aftermarket BLE-based vehicle security vendors should move from a single shared authentication key embedded in the companion app to per-device, rotatable, uniquely provisioned keys
  • Firmware updates for safety-relevant aftermarket automotive hardware should be pushed automatically or through a mandatory channel rather than gated behind an opt-in subscription app
  • Regulators such as NHTSA should evaluate disclosure-to-patch service-level expectations for aftermarket automotive security devices given the roughly 18-month gap observed in this case
  • Reduce or randomize BLE advertisement persistence after vehicle shutdown to close the location-tracking and post-shutdown remote-activation window
  • Disable or gate the dormant-unit BLE wake-up command so unsubscribed/inactive alarms are not remotely exploitable

Affected and fixed versions

  • Acrisure Protection Group — KARR / SWDS (SouthWest Dealer Services) Aftermarket Vehicle Security & Remote Immobilizer System (BLE-based)
    Vulnerable versions: All KARR/SWDS units manufactured and sold 2017-2026 running pre-July 20, 2026 firmware, including dormant/never-subscribed units
    Fixed in: Firmware update released July 20, 2026, applied via the KARR Security mobile app
  • Rockledge — Aftermarket BLE-based vehicle remote-control / anti-theft device
    Vulnerable versions: Unspecified — evaluated by researchers in the same study; requires interception of traffic during active use rather than one-time static key extraction, making it harder to exploit than KARR/SWDS, but not confirmed unaffected since Rockledge did not respond to disclosure
    Fixed in: Not disclosed in public reporting

Timeline

  • UC San Diego PhD student Nishant Bhaskar first identifies persistent Bluetooth device fingerprints from KARR-branded hardware while researching credit-card-skimmer detection, seeding the later BLE Theft Auto investigation.
  • UC San Diego researchers privately disclose the shared, hardcoded BLE authentication key vulnerability in KARR/SWDS devices to manufacturer Acrisure Protection Group.
  • Researchers validate the scale of exposure using WiGLE wireless-signal data and short field drives, including detecting 97 actively broadcasting KARR units during a single 20-minute Southern California test.
  • Acrisure Protection Group releases a firmware update for KARR/SWDS devices, distributed exclusively through the KARR Security mobile app, roughly 18 months after private disclosure.
  • Researchers notify the National Highway Traffic Safety Administration of the vulnerability given its vehicle-safety implications.
  • AppleInsider and The Drive publish early coverage of the newly available KARR firmware patch and the underlying Bluetooth vulnerability.
  • GBHackers, Cybersecurity News, CyberPress, TheCyberExpress, Popular Science, SC Media, and Jalopnik publish detailed technical coverage of the KARR/SWDS Bluetooth vulnerability.
  • Malwarebytes publishes follow-on analysis detailing the dormant-unit BLE wake-up command, silent no-owner-alert command execution, and the Rockledge comparison.
  • Researchers are scheduled to present the 'BLE Theft Auto' findings at DEF CON 34 in Las Vegas.
  • Researchers are scheduled to present the peer-reviewed paper 'BLE Theft Auto: Evaluating the Security of Aftermarket BLE-based Automotive Remote Control Systems' at the USENIX Security Symposium in Baltimore, MD.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 13 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