The MachineRecord
RegistryTMR-0208

An 'out of control' humanoid robot caused a disturbance in China, alarming engineers nearby.

No harmmalfunctionhumanoidUnitree Robotics
Date of incident
2025-05-03
Location
China
Model
H1
Sources
6
EscalationFollow-up
Timeline

How the event developed

  1. 2025-05-03Follow-up

    An 'out of control' humanoid robot caused a disturbance in China, alarming engineers nearby.

    asiae.co.kr
  2. 2025-05-04Report

    Industrial robot malfunctioned due to a coding error in China, injuring workers in a viral video incident.

    timesofindia.indiatimes.com
  3. 2025-05-06Follow-up

    A Unitree H1 humanoid robot suspended from a crane at a testing facility in China malfunctioned due to a reported coding error, flailing its arms and legs wildly, knocking over a computer and sending equipment flying while two engineers scrambled to avoid being hit.

    interestingengineering.com
  4. 2025-05-07Follow-up

    A Unitree H1 humanoid robot malfunctioned during testing at a factory in China, flailing its arms and legs uncontrollably while suspended by a crane, knocking over equipment and forcing two nearby engineers to back away.

    e.vnexpress.net
  5. 2025-05-07Follow-up

    A Unitree H1 humanoid robot malfunctioned and flailed its arms and legs wildly at what is believed to have been a public demonstration or testing setting in China, coming dangerously close to two nearby handlers without confirmed injury.

    newatlas.com
  6. 2025-05-07Follow-up

    A Unitree H1 humanoid robot malfunctioned during a factory test in China, flailing uncontrollably while suspended from a crane, striking one worker and causing two engineers to flee before another engineer stabilized it.

    postapocalypticmedia.com
Sources

Every claim above traces to one of these

Links are never hidden behind a paywall of ours. We store the date each source was captured, because news links rot and a dead link with a capture date is still evidence.

Right of reply

Named in this case?

Any company named here can submit a response. We publish it in the case unedited, and mark the case as awaiting a response the moment a request arrives. Target turnaround is five working days.