How your dashcam can be hacked, and how to protect yourself from the attack | Kaspersky official blog
How a dashcam can be hacked and turned it into a surveillance tool
AI Analysis
Technical Summary
This threat involves the exploitation of security weaknesses in consumer dashcams, which are increasingly equipped with Wi-Fi connectivity to allow users to configure settings and download footage via mobile apps. Researchers found that many dashcams use default or hardcoded passwords, have weak authentication mechanisms, or allow bypassing authentication entirely through techniques such as direct file access, MAC address spoofing, and replay attacks. These vulnerabilities enable attackers to connect to the dashcam’s embedded Linux system and access stored high-resolution video and audio recordings tagged with GPS and timestamps. This data can reveal detailed information about the vehicle’s movements, conversations inside the car, and surroundings. The researchers demonstrated that a single malware payload could compromise multiple dashcam models due to shared hardware and firmware components sourced from common suppliers. They also developed a worm-like malware capable of spreading between dashcams in close proximity, such as in traffic jams, enabling mass compromise. Data exfiltration can be performed either directly to an attacker’s device or via cloud services integrated with some dashcams, including those with LTE connectivity. The harvested data can be analyzed using AI models to transcribe audio and summarize trips, facilitating surveillance and tracking. The threat is exacerbated by the widespread use of a few popular dashcam brands and the similarity of their security flaws. Mitigation is challenging for users but includes disabling wireless features, changing default credentials, disabling audio recording, and keeping firmware updated. Vendors must adopt secure development practices, implement robust cryptography, and eliminate hardcoded credentials to prevent such attacks.
Potential Impact
For European organizations and individuals, this threat poses significant privacy and security risks. Compromised dashcams can lead to unauthorized surveillance, exposing sensitive information such as travel routes, meeting locations, and private conversations. This can facilitate corporate espionage, targeted attacks, or criminal activities such as stalking or blackmail. The ability of malware to spread autonomously between vehicles increases the scale and speed of compromise, potentially affecting large urban areas. Organizations with vehicle fleets using vulnerable dashcams may face operational risks and data breaches. The integration of cloud services for data syncing further expands the attack surface, risking exposure of stored footage and metadata. The threat undermines trust in connected vehicle devices and may have regulatory implications under European data protection laws such as GDPR. The potential for mass surveillance and data harvesting also raises concerns for public safety and national security, especially in countries with high dashcam adoption and dense traffic environments.
Mitigation Recommendations
1. Vendors should implement Security by Design principles, eliminating hardcoded passwords and using strong cryptographic authentication for all wireless interfaces. 2. Firmware should be regularly updated to patch vulnerabilities and disable unnecessary services such as FTP or RTSP servers or secure them with unique, strong credentials. 3. Users should prefer dashcams without Wi-Fi, LTE, or Bluetooth capabilities where possible to reduce attack surface. 4. If wireless features are necessary, users must change default SSIDs and passwords, enable hidden SSID modes, and configure auto-shutdown timers for Wi-Fi. 5. Disable audio recording and physically disconnect microphones if feasible to prevent eavesdropping. 6. Turn off parking mode to avoid continuous wireless exposure when the vehicle is unattended. 7. Organizations managing vehicle fleets should audit dashcam models for vulnerabilities and enforce security policies including device configuration and firmware management. 8. Monitor network traffic for unusual connections from dashcams and segment vehicle device networks from critical IT infrastructure. 9. Advocate for industry-wide standards and certifications for connected vehicle device security to ensure baseline protections. 10. Raise user awareness about the risks and best practices for securing dashcams and related mobile apps.
Affected Countries
Germany, United Kingdom, France, Italy, Spain, Netherlands, Belgium, Poland, Sweden, Austria
How your dashcam can be hacked, and how to protect yourself from the attack | Kaspersky official blog
Description
How a dashcam can be hacked and turned it into a surveillance tool
AI-Powered Analysis
Technical Analysis
This threat involves the exploitation of security weaknesses in consumer dashcams, which are increasingly equipped with Wi-Fi connectivity to allow users to configure settings and download footage via mobile apps. Researchers found that many dashcams use default or hardcoded passwords, have weak authentication mechanisms, or allow bypassing authentication entirely through techniques such as direct file access, MAC address spoofing, and replay attacks. These vulnerabilities enable attackers to connect to the dashcam’s embedded Linux system and access stored high-resolution video and audio recordings tagged with GPS and timestamps. This data can reveal detailed information about the vehicle’s movements, conversations inside the car, and surroundings. The researchers demonstrated that a single malware payload could compromise multiple dashcam models due to shared hardware and firmware components sourced from common suppliers. They also developed a worm-like malware capable of spreading between dashcams in close proximity, such as in traffic jams, enabling mass compromise. Data exfiltration can be performed either directly to an attacker’s device or via cloud services integrated with some dashcams, including those with LTE connectivity. The harvested data can be analyzed using AI models to transcribe audio and summarize trips, facilitating surveillance and tracking. The threat is exacerbated by the widespread use of a few popular dashcam brands and the similarity of their security flaws. Mitigation is challenging for users but includes disabling wireless features, changing default credentials, disabling audio recording, and keeping firmware updated. Vendors must adopt secure development practices, implement robust cryptography, and eliminate hardcoded credentials to prevent such attacks.
Potential Impact
For European organizations and individuals, this threat poses significant privacy and security risks. Compromised dashcams can lead to unauthorized surveillance, exposing sensitive information such as travel routes, meeting locations, and private conversations. This can facilitate corporate espionage, targeted attacks, or criminal activities such as stalking or blackmail. The ability of malware to spread autonomously between vehicles increases the scale and speed of compromise, potentially affecting large urban areas. Organizations with vehicle fleets using vulnerable dashcams may face operational risks and data breaches. The integration of cloud services for data syncing further expands the attack surface, risking exposure of stored footage and metadata. The threat undermines trust in connected vehicle devices and may have regulatory implications under European data protection laws such as GDPR. The potential for mass surveillance and data harvesting also raises concerns for public safety and national security, especially in countries with high dashcam adoption and dense traffic environments.
Mitigation Recommendations
1. Vendors should implement Security by Design principles, eliminating hardcoded passwords and using strong cryptographic authentication for all wireless interfaces. 2. Firmware should be regularly updated to patch vulnerabilities and disable unnecessary services such as FTP or RTSP servers or secure them with unique, strong credentials. 3. Users should prefer dashcams without Wi-Fi, LTE, or Bluetooth capabilities where possible to reduce attack surface. 4. If wireless features are necessary, users must change default SSIDs and passwords, enable hidden SSID modes, and configure auto-shutdown timers for Wi-Fi. 5. Disable audio recording and physically disconnect microphones if feasible to prevent eavesdropping. 6. Turn off parking mode to avoid continuous wireless exposure when the vehicle is unattended. 7. Organizations managing vehicle fleets should audit dashcam models for vulnerabilities and enforce security policies including device configuration and firmware management. 8. Monitor network traffic for unusual connections from dashcams and segment vehicle device networks from critical IT infrastructure. 9. Advocate for industry-wide standards and certifications for connected vehicle device security to ensure baseline protections. 10. Raise user awareness about the risks and best practices for securing dashcams and related mobile apps.
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: 12/11/2025, 10:27:01 PM
Last updated: 1/11/2026, 10:20:53 PM
Views: 153
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-15506: Out-of-Bounds Read in AcademySoftwareFoundation OpenColorIO
MediumYARA-X 1.11.0 Release: Hash Function Warnings, (Sun, Jan 11th)
MediumCVE-2026-0843: SQL Injection in jiujiujia jjjfood
MediumCVE-2026-0842: Missing Authentication in Flycatcher Toys smART Sketcher
MediumCVE-2025-15505: Cross Site Scripting in Luxul XWR-600
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.