San Francisco: rider says a Waymo robotaxi stayed stopped and support declined to move it while two men attacked the car with the rider inside (9 May 2026)
At about 3:30 a.m. on 9 May 2026 a Waymo robotaxi with a rider in the front passenger seat was at a stoplight at Pierce and Lombard streets in San Francisco when a man grabbed its front bumper and the vehicle stopped. The rider told the San Francisco Chronicle and NBC Bay Area that two men then struck the windshield and windows and climbed onto the car while it stayed stationary. The rider says Waymo support staff on the car intercom declined to move it, saying it was obstructed, although the rider saw nothing blocking it, and remembers about 10 minutes before the men left. The Chronicle reports that the car's remote assistant had noticed the car was not moving and decided to call police. The Chronicle reports that officers arrived at 3:46 a.m. The police report, as described by both outlets, identifies Waymo as the victim of malicious mischief and the rider as a witness. Police officials say the rider told officers of no injury. The rider later felt pain behind an ear that the rider believes came from glass, and sought therapy. Waymo spokespeople did not comment on the account in the reporting, and Waymo told the rider in an email that it was unable to access any footage without proper legal justification. The account is the rider's as reported by the Chronicle (16 July 2026) and NBC Bay Area (16 July 2026). The police report was not inspected and is known only through the outlets' descriptions.
- AI system
- Waymo Driver
- Waymo
- Occurred
- 9 May 2026
- Reported
- 16 July 2026
- Event location
- United States
- What the AI did
- Acted on the person’s behalf
- Reported harm
- Psychological Distress
- Whose AI use
- Their own AI use
- Setting
- Everyday life
- Evidence
- AI involvement reported · Causal attribution alleged · 3 sources, 2 underlying accounts
- 6 claims: 6 reported. 7 open questions
- People reported harmed
- At least 1 person
AI system as recorded: Waymo driverless robotaxi (autonomous vehicle), with remote support staff reachable through the car intercom
Reported harm
The rider told the Chronicle and NBC Bay Area that the rider feared being killed while the car was attacked and stayed stationary. The Chronicle reports that the rider later felt pain behind an ear that the rider thought came from glass and sought therapy. Police officials say the rider told officers at the scene that the rider was not injured. No medical or therapy record was inspected.
What remains unknown
- No Waymo vehicle log, footage or statement on the specific account was inspected. Waymo spokespeople were not available to the Chronicle and did not comment on the specific allegations to NBC Bay Area.
- Whether the robotaxi stopped because of the bumper grab or because it was at a stoplight is not settled in the sources. The Chronicle writes that the grab caused it to stop, and also that it pulled up to a stoplight.
- The Chronicle takes 3:46 a.m. as the time officers arrived from the police report, and the rider told NBC Bay Area that police arrived about 35 minutes after the 911 call. The two accounts are not reconciled.
- NBC Bay Area reports that the San Francisco Police Department said it generally does not release video and is not the custodian of the recording, and that according to the narrative in the police report an officer requested the footage the night of the incident. The Chronicle quotes a police captain saying the department cannot issue a search warrant on behalf of Waymo. The two accounts are not reconciled.
- Whether the rider was injured is unsettled: the rider told officers of no injury and later described pain behind an ear and a possible small cut. No medical record was inspected.
- The two attackers are not identified and no arrest is reported in the inspected sources.
- The police report was not inspected and is described only by the Chronicle and NBC Bay Area. The Chronicle body was read from a Wayback capture (26 September 2026) because the direct page returned a client-challenge stub. The capture is a revised version: an earlier syndicated copy (Yahoo, 17 July 2026) lacks the police officials' statement about the rider's injury and captions the photo 'refused to move', whereas the capture says 'remained stationary'. The record uses the revised text.
What the evidence supports
AI involvement: reported. The rider says the autonomous vehicle stopped when a man grabbed its bumper and stayed stationary for the rest of the attack, and that Waymo support staff declined to move it. The Chronicle states the vehicle stopped and remained stationary in its own voice, while the account of the attack and of the support replies comes from the rider. The vehicle was carrying the rider on a ride. No Waymo vehicle data or footage was inspected. The support responders are described as staff members and no source says software generated their replies.
6 claims: 6 reported. What the statuses mean
Reported At about 3:30 a.m. on 9 May 2026 a Waymo robotaxi with a rider in the front passenger seat was at a stoplight at Pierce and Lombard streets in San Francisco when a man grabbed its front bumper and the vehicle stopped. The rider says two men then struck the windshield and windows and climbed onto the car.
Causal attribution. The account is the rider's, told to the Chronicle and to NBC Bay Area, and the police report as described by both outlets records the rider's account. The attackers are the direct cause of the vandalism. No vehicle data or footage was inspected.
- sfchronicle.com(opens in new tab) supports · English
It was nearing 3:30 a.m. on May 9
- sfchronicle.com(opens in new tab) supports · English
In a flash the man grabbed the Waymo’s front bumper, causing the autonomous vehicle to stop.
- sfchronicle.com(opens in new tab) supports · English
the two took turns bashing the front windshield with an object that had the shape of a stick
- nbcbayarea.com(opens in new tab) supports · English
the Waymo vehicle stopped at the intersection of Pierce and Lombard Street
- nbcbayarea.com(opens in new tab) supports · English
two suspects threw items at the vehicle, jumped on it and broke a window
- sfchronicle.com(opens in new tab) supports · English
one of the men climbed on top of the vehicle’s hood and roof
- sfchronicle.com(opens in new tab) supports · English
He was riding shotgun
- sfchronicle.com(opens in new tab) supports · English
Waymo pulled up to a stoplight
Reported The rider says the robotaxi stayed stationary during an attack that the rider remembers as about 10 minutes, and that a Waymo rider cannot honk the horn or flash the lights to get help.
Causal attribution. Single-source account (the rider). The Chronicle states the stationary vehicle in its own voice and a photo caption. No vehicle logs were inspected and Waymo has not described what the driving system did.
- sfchronicle.com(opens in new tab) supports · English
He was trapped inside as the robotaxi remained stationary.
- sfchronicle.com(opens in new tab) supports · English
10 minutes of terror
- sfchronicle.com(opens in new tab) supports · English
You can’t honk the horn,
- sfist.com(opens in new tab) supports · English
for approximately 10 minutes, he was unable to honk a horn or get customer service to move the vehicle
- sfchronicle.com(opens in new tab) supports · English
You can’t flash the lights. You can’t do anything to get out of there.
Reported Waymo support staff who spoke to the rider through the car intercom declined the rider's request to move the car, saying it was obstructed. The rider says nothing was blocking the car. The Chronicle reports that the car's remote assistant had noticed the car was not moving and decided to call police.
Causal attribution. Both outlets take this from the rider. The sources call the responders "support team members" and a "remote assistant" and do not say whether any reply was generated by software. Waymo has not responded to the specific account in the inspected sources.
- sfchronicle.com(opens in new tab) supports · English
He asked whether they could move the car, and they declined, saying it was obstructed.
- nbcbayarea.com(opens in new tab) supports · English
Their response was no the car is obstructed and I said I'm literally looking in front of me on the street.
- nbcbayarea.com(opens in new tab) supports · English
There's nothing blocking me.
- sfchronicle.com(opens in new tab) context · English
Spokespeople for Waymo were not immediately available to comment.
- nbcbayarea.com(opens in new tab) context · English
Waymo did not provide further comment regarding
- sfchronicle.com(opens in new tab) context · English
The car’s remote assistant had noticed the car was not moving and decided to call police.
Reported The rider says the rider feared being killed, sought therapy afterward, and later noticed pain behind an ear that the rider believes came from glass. Police officials say the rider told officers at the scene that the rider was not injured. Waymo customer support later referred the rider to an insurance carrier for medical and mental health care.
Causal attribution. The rider's own account. The Chronicle describes the injury as something the rider believed to be a small laceration, and the rider told officers of no injury. No medical or therapy record was inspected. The attackers struck the windshield and windows, and NBC Bay Area's description of the police report says a window was broken.
- sfchronicle.com(opens in new tab) supports · English
“Please, please, get me out of here,” he said. “They’re going to kill me.”
- sfchronicle.com(opens in new tab) supports · English
woke up to feel pain behind his ear. He thought a piece of glass had burst from the window and pierced his skin.
- sfchronicle.com(opens in new tab) supports · English
He sought therapy to help process the attack
- sfchronicle.com(opens in new tab) supports · English
he noticed what he believed was a small laceration later that morning
- sfchronicle.com(opens in new tab) context · English
he told them he was not injured
- sfchronicle.com(opens in new tab) supports · English
A Waymo customer support representative called and referred him to an insurance carrier for medical and mental health care.
Reported The San Francisco Police Department report, as described by the Chronicle and NBC Bay Area, identifies Waymo as the victim of malicious mischief and the rider as a witness. Officers reached the intersection at 3:46 a.m., found the damaged robotaxi and interviewed the rider.
Causal attribution. Both outlets describe the report and neither publishes it. The report was not inspected. The rider recalls police arriving about 35 minutes after the rider called 911 (NBC Bay Area), which differs from the 3:46 a.m. time the Chronicle takes from the report.
- sfchronicle.com(opens in new tab) supports · English
Two officers pulled up to the intersection at 3:46 a.m., found the damaged Waymo
- sfchronicle.com(opens in new tab) supports · English
as victims of malicious mischief.
- nbcbayarea.com(opens in new tab) supports · English
According to the report, the incident was classified as malicious mischief.
- nbcbayarea.com(opens in new tab) supports · English
It also notes damage to the windshield and states the vehicle was towed from the scene by Waymo staff.
- sfchronicle.com(opens in new tab) supports · English
is merely a witness to the crime.
Reported The rider asked Waymo and the police for the vehicle's video and had not received it as of mid-July 2026. Waymo told the rider it could not access footage without legal justification, and police said they could not seek a warrant on Waymo's behalf.
Causal attribution. Company and police statements as quoted from emails to the rider. Whether footage exists in usable form was not established.
- sfchronicle.com(opens in new tab) supports · English
we’re unable to access any footage without proper legal justification.
- sfchronicle.com(opens in new tab) supports · English
we can’t issue a search warrant on behalf of Waymo.
- nbcbayarea.com(opens in new tab) supports · English
has not received it.
- nbcbayarea.com(opens in new tab) supports · English
It remains unclear whether San Francisco police ever obtained the vehicle's surveillance footage.
- nbcbayarea.com(opens in new tab) context · English
However, according to the narrative in the police report, an officer requested the footage the night of the incident.
Sources
3 sources inspected, from 2 underlying accounts. Sources that repeat one account do not corroborate each other.
- San Francisco Chronicle (16 Jul 2026)(opens in new tab)
s1 · sfchronicle.com · News report · English · Inspected · Shares an underlying account with another listed source · Primary
- NBC Bay Area (16 Jul 2026), separate interview with the rider and description of the police report(opens in new tab)
s2 · nbcbayarea.com · News report · English · Inspected · 16 July 2026
- SFist (17 Jul 2026), rewrites the Chronicle report(opens in new tab)
s3 · sfist.com · News report · English · Inspected · 17 July 2026 · Shares an underlying account with another listed source
How the sources were read, and where the events happened
Event countries: United States. Affected-person countries: United States. Court countries: Unknown.
The Chronicle and NBC Bay Area place the event at Pierce and Lombard streets in San Francisco, and SFist describes the rider as a San Francisco resident. No court proceeding is reported.
Reviewed for publication 2026-09-29: The San Francisco Chronicle article (full text read from a Wayback capture) and NBC Bay Area (independent interview and its own description of the police report) report the rider's account, and SFist rewrites the Chronicle. Every claim is the rider's statement, a description of a police report that was not inspected, or a company or police statement quoted by the outlets, so all claims stay at reported status. The direct harm is from the attackers, and the case is published for the reported behaviour of the stopped autonomous vehicle and of Waymo support toward the rider. The rider spoke to both outlets and is not named here.
People reported harmed in this case
At least 1 person
1 AI participant · 0 other people harmed
One rider reports fear, pain behind an ear and therapy. The sources do not say whether anyone else was in the vehicle, and no other person is reported harmed. The two men who attacked the vehicle are not counted as harmed.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). San Francisco: rider says a Waymo robotaxi stayed stopped and support declined to move it while two men attacked the car with the rider inside (9 May 2026). AI incidents. https://nope.net/incidents/2026-san-francisco-waymo-robotaxi-stopped-during-attack-with-rider-inside
BibTeX
@misc{2026_san_francisco_waymo_robotaxi_stopped_during_attack_with_rider_inside,
title = {San Francisco: rider says a Waymo robotaxi stayed stopped and support declined to move it while two men attacked the car with the rider inside (9 May 2026)},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2026-san-francisco-waymo-robotaxi-stopped-during-attack-with-rider-inside}
} Related cases
San Francisco: cyclist alleges Waymo robotaxi passenger door and a second Waymo injured her in a bike lane, sues Waymo over Safe Exit warning system
A 26-year-old cyclist alleges in a June 2025 lawsuit that on 16 February 2025 a driverless Waymo carrying four passengers pulled over to the right-side curb beside a no-stopping sign next to a marked bike lane on Seventh Street in San Francisco, that a passenger opened a door into the bike lane, and that she was thrown into a second Waymo that was also pulling into the lane. The complaint states she sustained serious bodily injuries and was taken by ambulance for emergency treatment. The Chronicle reports her saying she suffered a brain injury and spine and soft tissue damage that has kept her out of work and off bicycles. The suit, filed in San Francisco County Superior Court against Waymo and Alphabet, alleges battery, emotional distress, negligence and strict products liability and alleges that Waymo's Safe Exit passenger-warning system failed. Waymo did not comment on the suit and pointed to its own safety data. These are allegations reported by the San Francisco Chronicle.
Portland, Oregon: an anonymous social-media account posted 17 racist and anti-immigrant images targeting David Douglas High School football players and their coach, some digitally altered including with AI, from 22 September 2026; the school reported content to Portland police
David Douglas High School in Portland warned families in a statement reported on 28 September 2026 about social-media posts targeting its students, athletes, coaches and staff, saying some images and videos had been digitally altered, including with AI, and did not accurately represent those depicted; it reported some of the content to the Portland Police Bureau. KATU, which reviewed the account, reports 17 posts using racist, anti-immigrant and religious stereotypes against football players: one image shows a Latino player in a sombrero being detained by people labelled as ICE agents, another shows a player in a head covering with what appears to be a fake explosive vest, and a Black player is depicted beneath a caption referring to George Floyd. The head coach said students were hurt, and that one student texted him over the weekend after seeing one of the posts: 'Coach, this is terrible. What do I do?' The account references Rex Putnam High School, whose team David Douglas played on the Friday before the report; which along with its district says it has no connection to it. Who runs the account and which images were AI-generated are not reported.
New York: the Manhattan District Attorney seized 12 websites selling AI-generated sexual deepfakes of about 1,200 real people
On 14 September 2026 Manhattan District Attorney Alvin Bragg announced the seizure of 12 domain names used to disseminate, publish and sell non-consensual AI-generated sexual 'deepfake' videos. His office said individuals under investigation had used AI image- and video-creation tools to turn photos and videos of approximately 1,200 real people, overwhelmingly women, into hyper-realistic sexual imagery without consent. The victims included actors, politicians, athletes, musicians, activists and social-media influencers. WIRED and outside researchers reported that many videos reposted content from the defunct MrDeepFakes platform and that dozens of politicians appeared on the sites; investigations into who ran them are ongoing.
Saginaw, Michigan: a credit union CEO used ChatGPT to put herself and family members in 'Lake America' sweatshirts in a photo taken before a trip to Halifax; after her sister reposted it publicly without its AI label she says she received death threats and the family came home early, and on 23 September 2026 the credit union said she was no longer employed
The chief executive of Family First Credit Union in Saginaw, Michigan, told WJRT (ABC12) that before boarding a flight to Halifax, Nova Scotia, on 11 September 2026 she and family members took a photo and put it through ChatGPT to show them wearing 'Lake America' sweatshirts, a joke about the US president's order renaming Lake Ontario. She posted it to her private Facebook page with a marker saying it contained AI content; her sister reposted it publicly without the marker while they were in Halifax, and it spread in Canada as if the family had worn the shirts. The backlash concerned the image's political message; she said she would understand the anger of anyone in Halifax who thought the family had walked in wearing those sweatshirts. She said she was getting death threats and the family returned early; by 16 September she was back in the US. She called the post poor judgment, said she would not use AI again and that AI 'can make people think something's real that's not'. On 23 September the credit union said she was no longer an employee, effective immediately; it has not said whether she resigned or was dismissed, or why.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.