Pudu Robotics' fleet management platform let anyone with network access command any of its 100,000+ robots
In August 2025, a security researcher disclosed that every API in Pudu Robotics' robot fleet management platform lacked authentication validation. The system checked whether a token existed but did not verify whether it carried valid authorization. As a result, any party with network access to the platform could send commands to any robot in a fleet that then exceeded 100,000 units globally. The researcher tried to reach Pudu across multiple channels for approximately three weeks. Pudu responded only after the researcher alerted major clients, including the Japanese restaurant chains Skylark and Zensho. Pudu then patched the vulnerability and set up a formal security response centre.
What the AI did
Pudu's service robots, which navigate and act on their own, could be sent commands by anyone with network access to the company's fleet management platform, because the platform's APIs did not check whether access tokens carried valid authorization.
Added to the register November 15, 2026 · 1 source
- Developer
- Pudu Robotics (Shenzhen Pudu Technology Co., Ltd.)
- When it happened
- August 2025
- First reported
- Not stated in the sources
What this means for you
Could this affect you?
If you run Pudu service robots managed through its fleet management platform. Businesses running Pudu robots through its fleet management platform at the time had robots that anyone with network access to the platform could send commands to. Those businesses included major clients such as the Japanese restaurant chains Skylark and Zensho. Pudu has since patched the flaw.
What to check
- Confirm your Pudu fleet platform runs the patched version.
- Prefer private deployment so operational data stays on your own infrastructure.
- Segment robots from sensitive networks.
- Independently review the platform's login and permission checks before adding more robots.
Areas of your AI programme this touches
Every fact and its source (7)
- Vulnerability disclosedAugust 2025“In August 2025, a security researcher publicly known as BobDaHacker disclosed critical fleet vulnerabilities”[1]
- ExposureAny party with network access could command any robot“any party with network access to the management platform could send commands to any robot in the fleet”[1]
- Deployed robots at the timeMore than 100,000“Pudu's deployed base at the time exceeded 100,000 units globally.”[1]
- Disclosure attemptsAbout three weeks without response“The researcher contacted Pudu directly across multiple channels for approximately three weeks.”[1]
- Clients alertedSkylark and Zensho“including Japanese restaurant chains Skylark and Zensho”[1]
- Company responsePatched and set up a Security Response Center“Pudu subsequently patched the vulnerability, established a formal PUDU Security Response Center”[1]
- FindingFleet management APIs lacked authentication validation“The system checked whether a token existed but did not verify whether it carried valid authorization.”[1]
Sources
- Pudu Robotics Puts One AI Model in Three Robots. The FCC Has Banned Its Humanoid and Quadruped From US Markets.techtimes.com · November 9, 2026
How this record is classified. Severity S (3/5): real harm to one organisation, data exposed, or a containment failure. OECD level: hazard, an event that could plausibly have led to harm. Evidence: Reported, meaning press reporting only.
The facts in At a glance and in Every fact and its source are quoted from the sources listed. The summary, What the AI did and What this means for you are written from those sources and checked against them automatically before publication. Records reflect what has been disclosed, not everything that has happened. Incidents are found through news feeds and the GDELT Project.

