Replying to @IlirAliu_
100 designs running side by side with zero changeovers is impressive. With AI agents routing every board, trusted coordination becomes part of quality control.
Redirect a hospital delivery robot without touching it. 🚩
A since-patched Pudu platform flaw could have let any authenticated user do it.
GB/T 45502's other doors: what it sees, the commands it replays, the updates it trusts.
vicone.com/blog/from-percept…
#PhysicalAICybersecurity
Replying to @MarioNawfal
Adorable, open source, and built to be tweaked. Our kind of robot 🤖 Sharing the results is how the whole community makes these better and safer.
Replying to @XRoboHub
Real homes at real pace is exactly what robots need to learn from. It's also 2M hours of people's kitchens. That data deserves vault-level care.
"What gets retested when its software changes?" is the question most demos skip. We'd add one more: who's allowed to change it.
Replying to @adcock_brett
Sharing the all-hands publicly is a rare move. Respect. Would love to see security alongside the roadmap as Figure scales this fast.
Robots ship once. Bugs keep shipping. 🚩
Supplier firmware, open-source libs, third-party services: new holes land after launch.
No SBOM? You can't say which robots a CVE hits. An attacker only needs one.
vicone.com/blog/when-cyber-r…
#PhysicalAICybersecurity #RoboticCybersecurity
Replying to @TheHumanoidHub
Clean recap of the call. "We need on the order of 10k Optimus bots" for data. That pipeline will be worth protecting as much as the hand.
Three gates before a robot ships: FCC, CRA, IEC 62443. 🚩
A hacker sees three targets: the radio, the 24h disclosure clock, the network zones.
Compliance gets you through the audit. Exploits never read it.
vicone.com/blog/fcc-cra-and-…
#PhysicalAICybersecurity #RoboticCybersecurity
Replying to @michellelsun @taurobots
One of the most honest physical AI deployment reviews we’ve seen.
But “they retain the data they collect for training purposes” — in your home.
That line deserved more attention. 👀
Replying to @rar2028
I like the fact that it joins the trend. Hope the security features come with it the same way.
Safety analysis calls it improbable.
Hackers call it a repro. 🚩
Find the input that triggers the hazard and the rare event fires again and again, even on cue.
Rarity isn't protection.
vicone.com/blog/can-a-robot-…
#PhysicalAICybersecurity #RoboticCybersecurity #PhysicalAI
No fence left to jump. Robots now work where people are. 🤖
Plant an instruction in data, compromise a tool, or abuse broad permissions: you steer the robot's next action, not just the agent's next answer.
vicone.com/blog/ai-agents-ca…
#PhysicalAICybersecurity #RoboticCybersecurity
Replying to @agilityrobotics @nyobolt
Congrats on Digit 5's 10:1 run-to-charge design. Faster cycles mean denser fleet ops — and denser remote-update windows to harden. 🤖
Replying to @BostonDynamics @CocaColaEP
Congrats on Spot going global with Coca-Cola. Plant-roaming fleets for leak hunts also widen the remote-ops and telemetry attack surface — lock those paths down. 🤖
Replying to @BostonDynamics
Watching Atlas come together in-house is a treat 🤖
Appreciate the pointers. Patching the hub firmware just to keep up with full IMU and compass rates is the unglamorous part nobody posts about. Going to dig into that DroneCAN module 🚩
The robot's Wi-Fi setup had a second user in mind.
UniPwn: hardcoded AES + auth bypass + command injection = root on Unitree Go2, G1, H1, B2 over BLE. Wormable: one owned bot hunts the next. Zero faults. 🚩
vicone.com/blog/why-cybersec…
#PhysicalAICybersecurity #RoboticCybersecurity
A hacked robot doesn't wait for your SOC.
Spoofed sensor, poisoned model, rogue API call → physical action in the next control cycle. Milliseconds, not minutes. 🤖
vicone.com/blog/how-physical…
#PhysicalAICybersecurity #RoboticCybersecurity
