5 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The author details their experience with an Ãike electric scooter after the company went bankrupt, leading to concerns over app functionality. They reverse engineer the scooter's app to regain control, uncovering security flaws and the complexities of its communication with the scooter via Bluetooth.
If you do, here's more
A few years back, the author bought an Ãike T electric scooter for city commuting after becoming frustrated with rental options. Despite its high price and the availability of technically superior scooters, they chose the Ãike because it was a local product designed and manufactured in Estonia. The scooter was ambitious, featuring custom components and a sister company that offered rental services. Unfortunately, Ãike went bankrupt, raising concerns about sourcing replacement parts and the reliance on a cloud-based app for essential functions, which was already losing features.
To address the decreasing functionality, the author began reverse engineering the scooter and its app. The app was built using React Native and utilized a newer compilation method that made reverse engineering complex. However, they found a critical security flaw that allowed control over any Ãike scooter. The reverse engineering process involved using tools like Pilfer's hermes_rs project for the bytecode and Vineflower for Kotlin code, alongside Frida to monitor Bluetooth communications.
By hooking into Bluetooth functions, the author could intercept and analyze commands sent to the scooter. They focused on GATT characteristics, which are essential for Bluetooth communication. Their Frida script printed out details of the communication, revealing UUIDs and values associated with various commands. This analysis not only demonstrated a flaw in the scooter's security but also highlighted the challenges of maintaining a locally manufactured product heavily reliant on proprietary technology.
Questions about this article
No questions yet.