Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

How your dashcam can be hacked, and how to protect yourself from the attack | Kaspersky official blog

0
Medium
Vulnerability
Published: Thu Nov 27 2025 (11/27/2025, 16:32:03 UTC)
Source: Kaspersky Security Blog

Description

How a dashcam can be hacked and turned it into a surveillance tool

AI-Powered Analysis

AILast updated: 11/27/2025, 16:46:09 UTC

Technical Analysis

The security threat involves the exploitation of vulnerabilities in dashcams, primarily through their Wi-Fi connectivity, which is often used for legitimate purposes like adjusting settings or downloading footage via a paired smartphone app. Despite many dashcams being offline (lacking cellular connectivity), their Wi-Fi interfaces create an attack surface. Researchers found that many dashcams use default or hardcoded passwords, weak authentication schemes, or rely on MAC address verification that can be spoofed. Attack methods include direct unauthorized file access bypassing password checks, MAC spoofing to impersonate authorized devices, and replay attacks capturing and reusing legitimate authentication exchanges. Once connected, attackers can download high-resolution video footage, audio recordings, and metadata including GPS coordinates and timestamps. This data can reveal detailed information about the vehicle’s movements, conversations inside the car, and identities of passengers or nearby individuals. The threat is exacerbated by the similarity in hardware and firmware across multiple dashcam brands, allowing a single exploit to compromise a large portion of devices. Researchers also demonstrated a worm-like malware that can propagate between dashcams in traffic, enabling mass compromise. Data exfiltration can occur directly to attacker-controlled devices or via cloud services, exploiting insecure cloud storage or vendor infrastructure. The attack can be staged at locations where vehicles stop or even while vehicles are moving in traffic. The implications include mass surveillance, privacy violations, and potential use in criminal or fraudulent schemes. Mitigation strategies include disabling wireless features, changing default credentials, disabling audio recording, and applying firmware updates. Vendors are urged to implement security by design, robust cryptography, and better authentication mechanisms to prevent such attacks.

Potential Impact

For European organizations, this threat poses significant privacy and security risks, especially for those relying on dashcams for fleet management, security, or insurance purposes. Compromised dashcams can leak sensitive location data, travel routes, and audio conversations, potentially exposing confidential business information or employee movements. The ability to track vehicles and record conversations could be exploited for corporate espionage, targeted surveillance, or blackmail. Mass compromise could lead to large-scale data harvesting, undermining trust in dashcam technology and cloud services. Additionally, infected dashcams acting as a botnet could be leveraged for further cyberattacks, increasing the attack surface of organizations. The threat also raises regulatory concerns under GDPR due to unauthorized processing and exposure of personal data. Organizations may face reputational damage, legal liabilities, and operational disruptions if their dashcams are compromised. The worm-like propagation mechanism increases the risk of rapid spread within urban environments, affecting multiple organizations simultaneously.

Mitigation Recommendations

1. Select dashcam models without Wi-Fi, Bluetooth, or LTE capabilities to eliminate remote attack vectors. 2. If wireless features are necessary, disable Wi-Fi, Bluetooth, and audio recording when not in use; physically disconnect microphones if possible. 3. Change default SSIDs and passwords immediately upon installation; avoid using hardcoded or manufacturer defaults. 4. Enable Wi-Fi auto-shutdown features to minimize exposure time and hide SSIDs to reduce discoverability. 5. Regularly update dashcam firmware and associated smartphone apps to apply security patches. 6. For fleet vehicles, implement network segmentation and monitor wireless traffic to detect unauthorized access attempts. 7. Evaluate cloud service security and restrict data synchronization features if cloud storage is insecure. 8. Vendors should adopt secure development lifecycle practices, including secure authentication, cryptographic protections, and vulnerability testing. 9. Conduct regular security audits and penetration testing on dashcam products and associated infrastructure. 10. Educate users and fleet managers about the risks and best practices for dashcam security.

Need more detailed analysis?Get Pro

Technical Details

Article Source
{"url":"https://www.kaspersky.com/blog/dashcam-hack-botnet-on-the-wheels/54839/","fetched":true,"fetchedAt":"2025-11-27T16:45:55.859Z","wordCount":2004}

Threat ID: 69288043d78caf05d336200b

Added to database: 11/27/2025, 4:45:55 PM

Last enriched: 11/27/2025, 4:46:09 PM

Last updated: 11/27/2025, 7:15:59 PM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats