Remotely unlocking electric scooters

August 21, 2026 ยท 3 min read

Remotely unlocking electric scooters

A company put a fleet of electric scooters in my city. I saw a lot of internet-connected devices on a backend nobody had tested yet, so I took a look.

I spent days on recon, reversing the mobile app, trying SQL injection and forged tokens. None of it worked. What got me in was a known username and a weak password.

Recon

I mapped the subdomains of . Most just redirected to the app store. Three were interesting:

  • www: a WordPress site;

  • api: the REST API used by the apps;

  • painel: an Angular panel for the company's operators.

Nothing linked to the panel. I found it by enumeration.

The panel

The panel's JavaScript loaded for anyone, so I read it and found dozens of endpoints: users, vehicles, maps, IoT devices, vouchers, payments. Every one returned 401 Unauthorized.

I tried the usual stuff:

  • forged admin tokens: rejected;

  • changing token data: rejected;

  • SQL injection on the login: nothing;

  • .git and .env: not exposed.

The auth was solid. I needed a real user.

Getting a username

The WordPress API listed its authors, which gave me one username: .

The panel's login returned different errors for "wrong password" and "user doesn't exist". So I checked: the same username existed on the panel too.

The password

There was no rate limiting on the login, so I brute forced it. A password worked after a while, and the account was an admin.

What I could access

Every 401 now returned data:

  • the live map with every scooter and its position;

  • docks, garages, and geofences;

  • the IoT device list;

  • app users (the panel showed over 400,000 records);

  • companies, permissions, transactions, and financial data.

Fleet map showing every scooter, its battery level, and its real position in the city.

Clicking a scooter showed its code, type, and location:

Map popup with vehicle code, type (Scooter), and location (Dock).

I could also edit vehicles, users, and vouchers, and turn on free rides for accounts.

The "Vehicle Registry" screen searching for a specific scooter; sensitive columns already redacted.

The vehicle form had Unlock, Lock, and Restart IoT buttons. Those send commands straight to the scooter.

Vehicle edit form with the Unlock, Lock, and Restart IoT buttons.

Unlocking a real scooter

I tested on one vehicle only: one unlock, one lock. The panel said both worked.

The message "Gravado com sucesso." ("Saved successfully.") shown by the panel after the command.

That message doesn't prove anything happened on the street, so a friend stood next to a scooter and filmed it while I sent the command. It unlocked and the lights turned on. Nobody paid, nobody touched it.

The scooter unlocking remotely: its lights turn on with nobody touching it.

What didn't work

Most of my time went here:

  • Mobile app: built with Flutter. Intercepting its traffic took many tries, and its only protection was a static token. Good for mapping the API, but it didn't get me in.

  • Big map queries: asking for the whole country killed my session. One of the few defenses I hit.

  • SQL injection and forged tokens: went nowhere.

The chain

  1. 01WordPress leaks a username
  2. 02The login confirms that user exists
  3. 03No rate limiting allows a brute force
  4. 04The password gives full admin access
  5. 05The panel can send IoT commands
  6. 06A scooter unlocks remotely

One password was the only thing between the internet and a button that unlocks real scooters. No 2FA, no rate limit, no extra check on IoT commands.

The fancy stuff failed. The basic stuff worked.