Unitree G1 Security Disaster

2025-09-30 · Source: sentdex · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Robotics & Autonomous Systems, Cybersecurity & Data Privacy · Depth: Intermediate, extended

Summary

Recent security vulnerabilities have been confirmed across Unitree's robot fleet, including the G1, H1, GOT, B2, and R1 models. The primary flaw involves remote code execution (RCE) on the main board, which runs proprietary code and is typically inaccessible to users. This RCE is facilitated by hard-coded, identical AES keys used for Bluetooth Low Energy (BLE) connections across all Unitree robots. Attackers can inject arbitrary terminal commands as root into the Wi-Fi credentials field during a BLE connection, effectively gaining full control. Additionally, the robots exhibit persistent telemetry, sending data to Unitree servers even after a reboot, contradicting Unitree's claim that robots are "designed for offline use." While Unitree acknowledged "network related issues" and promised fixes, the fundamental problem of hard-coded AES keys remains unaddressed, enabling man-in-the-middle attacks and forced Wi-Fi credential updates.

Key takeaway

For robotics engineers and researchers using Unitree robots, you must assume your robot is vulnerable to remote code execution and unauthorized data transmission. Immediately disable Bluetooth or physically remove the module to prevent local RCE. To mitigate persistent telemetry, configure Wi-Fi credentials to a non-existent network, as the robot will attempt to connect and transmit data even after a reboot, regardless of explicit authorization.

Key insights

Hard-coded AES keys in Unitree robots enable remote code execution and persistent, unauthorized telemetry.

Principles

• Proprietary main boards can hide critical vulnerabilities.
• Hard-coded, identical keys create fleet-wide security risks.

Method

Remote code execution is achieved by connecting via BLE using hard-coded AES keys, then injecting root commands into the Wi-Fi password field. Persistent telemetry is demonstrated by monitoring network traffic after updating Wi-Fi credentials via BLE.

In practice

• Disable Bluetooth or desolder modules to mitigate BLE vulnerabilities.
• Use junk Wi-Fi credentials to prevent unauthorized telemetry.
• Monitor network traffic for unexpected outbound connections.

Topics

• Remote Code Execution
• Bluetooth Low Energy
• Unitree Robots
• Robot Telemetry
• Cybersecurity Vulnerabilities

Best for: Robotics Engineer, AI Security Engineer, Software Engineer

Related on AIssential

• Unboxing the Unitree G1 Edu Humanoid — The Unitree G1 humanoid requires specific state transitions and foot pressure for stable operation, often undocumented.
• Tesla reveals two Robotaxi crashes involving teleoperators — Teleoperator intervention in Tesla Robotaxis has led to low-speed crashes, revealing safety challenges in autonomous vehicle deployment.
• OpenClaw Users Are Allegedly Bypassing Anti-Bot Systems — OpenClaw users are reportedly bypassing anti-bot systems, raising concerns about AI misuse and web security.
• Reinforcement learning with Unitree G1 humanoid - Dev w/ G1 P.5 — PPO-trained, compact RL policies can achieve precise robotic arm control despite sim-to-real challenges and inherent robot safety risks.
• Humanoid Robots Are Coming to Factory Floors — But the Hardware Isn’t Ready Yet — Humanoid robot hardware, not AI, is the critical bottleneck for industrial deployment due to environmental demands.
• Home Robot Safety Is All About Relationships — Domestic robot safety is relational, emerging from human-robot interaction, not just machine properties.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by sentdex.