Campus Alert Archive
Stanford

A driver strikes a pedestrian and flees while shouting a slur in a suspected hate crime

AI-generated · every claim is source-linked
CAaggravated assaulttimely warninghigh confidence
Compare →
Under Investigation

On the afternoon of November 3, 2023, a Stanford University student of Arab Muslim heritage was struck by a black Toyota 4Runner at Campus Drive and Ayrshire Farm Lane. The driver made eye contact, accelerated, and shouted 'F*** you and your people' before fleeing. Stanford's Department of Public Safety issued an AlertSU community alert that evening, and the Santa Clara County Sheriff later took over the hate-crime investigation.

Alerts
3
Response
—
Killed
0
Injured
1
Institution
Stanford University
Private R1 · CA
All Stanford cases →
~17,249 studentsAtHocAlertSU
Official alert policy
Read when and how Stanford says it will use AlertSU: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

3 messages in sequence · 3 verified verbatim

Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.

INITIAL ALERTEmail
Verified verbatim1533 chars
Community Advisory-Hit and Run Hate Crime Just before 2 p.m. today, a hit-and-run traffic incident at Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane, was reported to police. The incident resulted in injuries to a pedestrian. Fortunately, the injuries to the victim are not life-threatening. This incident is being investigated by the California Highway Patrol, as all injury traffic incidents on campus are. Based on the circumstances reported by the victim, the CHP is investigating the incident as a potential hate crime. The victim reported that the driver made eye contact with the victim, accelerated and struck the victim, and then drove away while shouting “f*** you people.” The victim is an Arab Muslim student at Stanford. The suspect vehicle is described as a black SUV with a tire mounted on the back. Additional information about the suspect will be shared as it is available. We encourage any witnesses to this incident to come forward and share with law enforcement any information they have. Please contact the CHP at 650-779-2700 or the Department of Public Safety at 650-329-2413. Stanford is continuing to work to provide a safe and secure campus environment in the context of heightened tensions related to the events in Israel and Gaza. This includes additional security that has been deployed at key locations on campus. If you ever have a concern for your personal safety, please call 911 or 9-911 from a campus telephone. This alert is being sent to you in compliance with the Jeanne Clery Act.
Verify this quote
Stanford Department of Public Safety AlertSU archive (alertid=1401), Community Advisory-Hit and Run Hate Crime; body also mirrored at emergency-failover.stanford.edu Community Crime Alert pagepolice.stanford.edufind archived copies
Verbatim recovered 2026-07-17 from official SUDPS AlertSU archive alertid=1401 (ajax content); Posted Friday, November 3rd, 2023, 10:29 pm PDT
Official title is 'Community Advisory-Hit and Run Hate Crime' (not a later multi-source reconstruction)
CHP is named as lead because the injury collision occurred on Campus Drive (public roadway jurisdiction at Stanford)
Quote is sanitized with asterisks as f*** in the official AlertSU; Nov 4 update (alertid=1402) expands the shouted phrase to 'f*** you and your people'
Initial vehicle description is only 'black SUV with a tire mounted on the back'; full 4Runner/plate detail arrives in the Nov 4 update
UPDATEEmail+10h 55m
Verified verbatim1287 chars
Additional information - Hit and Run, Hate Crime Investigation Additional information is available about the suspect in the hit-and-run incident, being investigated as a hate crime, that was the subject of an AlertSU message Friday evening. The victim, an Arab Muslim student, describes the driver of the vehicle as a white male in his mid 20s, with short dirty-blond hair and a short beard, wearing a gray shirt and round framed eyeglasses at the time of the incident. The driver is reported to have made eye contact with the victim, accelerated and struck the victim, and then driven away while shouting “f*** you and your people” out the lowered window of the vehicle. The vehicle involved in the incident is described by the victim as a black Toyota 4Runner, model year 2015 or newer, with an exposed tire mounted to the rear center and a Toyota logo in the center of the wheel. The vehicle was described by the victim as having a white California license plate with the letters M and J, with M possibly being the first letter and J in the middle. The California Highway Patrol is continuing to investigate this incident. Any witnesses are encouraged to come forward to share information. Please contact the CHP at 650-779-2700 or the Department of Public Safety at 650-329-2413.
Verify this quote
Stanford Department of Public Safety AlertSU archive (alertid=1402), Additional information - Hit and Run, Hate Crime Investigationpolice.stanford.edufind archived copies
Verbatim recovered 2026-07-17 from official SUDPS AlertSU archive alertid=1402; Posted Saturday, November 4th, 2023, 9:24 am PDT
Adds suspect physical description (white male mid-20s, dirty-blond hair, short beard, gray shirt, round eyeglasses) and detailed vehicle description (black Toyota 4Runner 2015 or newer, M and J plate letters)
Expands the shouted phrase from Friday's 'f*** you people' to 'f*** you and your people' out the lowered window
Still names CHP as continuing lead investigator
UPDATEEmail+5d
Verified verbatim580 chars
Sheriff’s Office further information – Hit and Run The Santa Clara County Sheriff’s Office has issued an update, including a suspect sketch, on the November 3 hit and run that occurred on the Stanford campus. The Sheriff’s Office is investigating the incident as a hate crime. The update is available at: https://countysheriff.sccgov.org/sites/g/files/exjcpb406/files/news-releases/Stanford%20University%20-Hate%20Crime.pdf Further updates and ongoing press releases from the Sheriff’s Office can be found here: https://countysheriff.sccgov.org/about-us/newsroom-press-releases
Verify this quote
Stanford Department of Public Safety AlertSU archive (alertid=1404), Sheriff's Office further information – Hit and Run; content also mirrored on Stanford Emergency Informationpolice.stanford.edufind archived copies
Verbatim recovered 2026-07-17 from official SUDPS AlertSU archive alertid=1404; Posted Thursday, November 9th, 2023, 6:51 pm PST
Hands the hate-crime investigation narrative to the Santa Clara County Sheriff's Office and links the official suspect-sketch PDF
Does not restate vehicle/suspect physical descriptors; points community to the Sheriff's news release
Message elements

How the first alert is built

To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.

Community Advisory-Hit and Run Hate Crime Just before 2 p.m. today, a hit-and-run traffic incident at Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane, was reported to police. The incident resulted in injuries to a pedestrian. Fortunately, the injuries to the victim are not life-threatening. This incident is being investigated by the California Highway Patrol, as all injury traffic incidents on campus are. Based on the circumstances reported by the victim, the CHP is investigating the incident as a potential hate crime. The victim reported that the driver made eye contact with the victim, accelerated and struck the victim, and then drove away while shouting “f*** you people.” The victim is an Arab Muslim student at Stanford. The suspect vehicle is described as a black SUV with a tire mounted on the back. Additional information about the suspect will be shared as it is available. We encourage any witnesses to this incident to come forward and share with law enforcement any information they have. Please contact the CHP at 650-779-2700 or the Department of Public Safety at 650-329-2413. Stanford is continuing to work to provide a safe and secure campus environment in the context of heightened tensions related to the events in Israel and Gaza. This includes additional security that has been deployed at key locations on campus. If you ever have a concern for your personal safety, please call 911 or 9-911 from a campus telephone. This alert is being sent to you in compliance with the Jeanne Clery Act.

  • Sourcepresent14/25

    Final assessment

    A majority credited the California Highway Patrol and Department of Public Safety as identified investigating/issuing authorities, while a substantial minority felt these were named only as investigators, not as a clear issuing signature for the advisory itself. Majority rules present.

    Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.

    See all 25 individual reads
    1. present: Signed as issued by the "Department of Public Safety" and references CHP investigation.
    2. present: Names the CHP and the Department of Public Safety as investigating authorities.
    3. absent: No specific authority names itself as issuer of this advisory
    4. absent: no clear issuing authority or branded sender identified in the notice itself
    5. absent: No specific agency name given, only references CHP and Department of Public Safety generically, no branded signature.
    6. present: References CHP, Department of Public Safety, and Stanford compliance
    7. absent: No issuing authority named, though CHP and DPS are referenced as investigators not senders
    8. present: Names the California Highway Patrol and Department of Public Safety at Stanford.
    9. present: Names 'Department of Public Safety' and CHP as investigating agencies.
    10. absent: No named issuing authority signature, references CHP and DPS but not as sender.
    11. present: References CHP and Department of Public Safety as investigating agencies.
    12. present: References the Stanford Department of Public Safety and CHP as investigators.
    13. present: California Highway Patrol and Department of Public Safety named as investigating agencies.
    14. absent: No specific sender identified, generic 'Community Advisory' label without agency name in text given.
    15. present: References CHP and Department of Public Safety as investigating authorities, sent per Clery Act.
    16. absent: No specific issuing agency named for this advisory itself, though CHP/DPS are referenced as investigators.
    17. present: Department of Public Safety and CHP named.
    18. absent: No specific authority named as issuer, generic 'we'
    19. absent: no specific sender named, though CHP and DPS are mentioned as investigators not issuers
    20. absent: Labeled 'Community Advisory' but no specific issuing department named for this message.
    21. present: References CHP investigation and Department of Public Safety
    22. present: references CHP and 'Department of Public Safety'
    23. present: California Highway Patrol and Department of Public Safety named.
    24. absent: No specific issuing office named in the excerpt beyond 'Department of Public Safety' phone contact, but no clear signature/authority header.
    25. present: Names the California Highway Patrol and Department of Public Safety as investigators.
  • Hazardpresent25/25

    Final assessment

    Unanimous agreement that a hit-and-run traffic incident investigated as a potential hate crime is specifically named.

    What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.

    See all 25 individual reads
    1. present: Describes a "hit-and-run traffic incident" investigated as a potential hate crime.
    2. present: Describes a 'hit-and-run traffic incident', naming the specific hazard.
    3. present: Names hit-and-run traffic incident/hate crime
    4. present: names hit-and-run and potential hate crime specifically
    5. present: Names hit-and-run traffic incident treated as potential hate crime.
    6. present: 'hit-and-run traffic incident' and hate crime described
    7. present: 'hit-and-run traffic incident' described as a hate crime
    8. present: Describes a 'hit-and-run traffic incident' investigated as a hate crime.
    9. present: Names 'hit-and-run traffic incident' as a potential hate crime.
    10. present: Names hit-and-run and hate crime.
    11. present: Names hit-and-run traffic incident/hate crime.
    12. present: Describes a hit-and-run vehicle attack, a hate crime.
    13. present: 'hit-and-run traffic incident' and potential hate crime named.
    14. present: 'hit-and-run traffic incident' resulting in injury names the hazard.
    15. present: 'hit-and-run traffic incident' and potential hate crime described.
    16. present: 'hit-and-run traffic incident' names the hazard as a potential hate crime.
    17. present: Hit-and-run hate crime named specifically.
    18. present: 'hit-and-run traffic incident' and 'hate crime' named
    19. present: 'hit-and-run traffic incident' described as a potential hate crime
    20. present: Describes a hit-and-run traffic incident being investigated as a hate crime.
    21. present: 'hit-and-run traffic incident' and potential hate crime described
    22. present: 'hit-and-run traffic incident' and potential hate crime
    23. present: Hit-and-run hate crime specified.
    24. present: 'hit-and-run traffic incident' and 'potential hate crime' name the hazard.
    25. present: Describes a hit-and-run traffic incident/hate crime.
  • Locationpresent25/25

    Final assessment

    Unanimous agreement that Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane, is specifically named.

    Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.

    See all 25 individual reads
    1. present: Names "Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane."
    2. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane.
    3. present: Campus Drive and Ayrshire Farm Lane given
    4. present: names Campus Drive and Ayrshire Farm Lane near Bowdoin Lane
    5. present: Names Campus Drive and Ayrshire Farm Lane.
    6. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane'
    7. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane'
    8. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane.
    9. present: Names 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane'.
    10. present: 'Campus Drive and Ayrshire Farm Lane' given.
    11. present: Names Campus Drive and Ayrshire Farm Lane.
    12. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane.
    13. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane' given.
    14. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane'.
    15. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane.
    16. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane' given.
    17. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane'.
    18. present: 'Campus Drive and Ayrshire Farm Lane' given
    19. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane'
    20. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane.
    21. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane
    22. present: 'Campus Drive and Ayrshire Farm Lane'
    23. present: Campus Drive and Ayrshire Farm Lane named.
    24. present: 'Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane' given.
    25. present: Names Campus Drive and Ayrshire Farm Lane, near Bowdoin Lane.
  • Guidanceabsent11/25

    Final assessment

    A modest majority found the message only asks witnesses to come forward and report, without direct protective action for personal safety, while a sizable minority credited the call-911-if-concerned line as protective guidance. Majority rules absent.

    The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.

    See all 25 individual reads
    1. present: Tells readers to contact CHP or Public Safety with information, and call 911 for safety concerns.
    2. present: Encourages witnesses to come forward and call 911 or the listed numbers.
    3. present: Encourages witnesses to come forward and contact CHP or Public Safety
    4. absent: only asks witnesses to come forward, not a protective action instruction
    5. present: Encourages witnesses to come forward and contact CHP or DPS.
    6. present: 'encourage any witnesses...come forward' and call 911/DPS if concerned
    7. present: 'we encourage any witnesses... come forward', call CHP or DPS
    8. absent: Only asks witnesses to come forward, no protective action for recipients.
    9. absent: Only requests witnesses come forward, no protective action instruction.
    10. present: Encourages witnesses to contact CHP or DPS.
    11. present: Encourages witnesses to contact CHP or Public Safety.
    12. present: Asks witnesses to contact CHP or call 911 if concerned for safety.
    13. present: 'encourage any witnesses...come forward' is an instruction to recipients.
    14. absent: Asks witnesses to come forward but gives no protective action.
    15. absent: Only asks witnesses to come forward, no protective instruction.
    16. absent: Only asks witnesses to come forward, no protective action for recipients.
    17. absent: Only asks witnesses to come forward, not protective action.
    18. absent: No protective action, only asks witnesses to come forward
    19. absent: asks for witnesses to come forward, not protective action
    20. absent: Only asks witnesses to come forward, no protective action for recipients.
    21. absent: Only asks witnesses to come forward, no protective action for recipients
    22. absent: only asks witnesses to come forward, no protective action for recipients
    23. present: 'call 911 or 9-911' instructed if concerned.
    24. absent: Only asks witnesses to come forward, not protective action for personal safety.
    25. absent: Only asks witnesses to come forward; no protective action instructed.
  • Timepresent25/25

    Final assessment

    Unanimous agreement that 'Just before 2 p.m. today' gives a specific time and date.

    When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.

    See all 25 individual reads
    1. present: States "Just before 2 p.m. today."
    2. present: 'Just before 2 p.m. today' gives a specific time.
    3. present: 'Just before 2 p.m. today' given
    4. present: 'Just before 2 p.m. today' gives time and recency
    5. present: States 'Just before 2 p.m. today'.
    6. present: 'Just before 2 p.m. today'
    7. present: 'Just before 2 p.m. today'
    8. present: States 'Just before 2 p.m. today'.
    9. present: 'Just before 2 p.m. today' gives time.
    10. present: 'Just before 2 p.m. today' given.
    11. present: 'Just before 2 p.m. today' gives time and recency.
    12. present: States 'Just before 2 p.m. today.'
    13. present: 'Just before 2 p.m. today' given.
    14. present: 'Just before 2 p.m. today' gives time and recency.
    15. present: 'Just before 2 p.m. today' given.
    16. present: 'Just before 2 p.m. today' given.
    17. present: 'Just before 2 p.m. today'.
    18. present: 'Just before 2 p.m. today' given
    19. present: 'Just before 2 p.m. today'
    20. present: 'Just before 2 p.m. today'.
    21. present: 'Just before 2 p.m. today'
    22. present: 'Just before 2 p.m. today'
    23. present: 'Just before 2 p.m. today' given.
    24. present: 'Just before 2 p.m. today' given.
    25. present: States 'Just before 2 p.m. today'.
  • Impactpresent24/25

    Final assessment

    Nearly unanimous agreement that stating the incident 'resulted in injuries to a pedestrian' conveys real harm, even though the injuries are noted as not life-threatening; one dissent felt the not-life-threatening framing negated any forward-looking impact statement.

    What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.

    See all 25 individual reads
    1. present: States injuries to the victim "are not life-threatening," conveying the severity.
    2. present: States the incident 'resulted in injuries to a pedestrian', though 'not life-threatening'.
    3. present: States injuries to victim, though 'not life-threatening'
    4. present: states injuries to the victim, though noted not life-threatening, conveying harm occurred
    5. absent: States injuries not life-threatening, no forward-looking harm warning.
    6. present: 'resulted in injuries to a pedestrian'
    7. present: 'resulted in injuries to a pedestrian'
    8. present: States 'resulted in injuries to a pedestrian', a concrete consequence.
    9. present: States injuries to the pedestrian, though 'not life-threatening'.
    10. present: States injuries to pedestrian, though 'not life-threatening'.
    11. present: States injuries to pedestrian, though not life-threatening.
    12. present: States the pedestrian suffered injuries, though 'not life-threatening.'
    13. present: 'resulted in injuries to a pedestrian' states actual harm caused.
    14. present: States injuries occurred, though 'not life-threatening'.
    15. present: States 'resulted in injuries to a pedestrian'.
    16. present: States injuries occurred though 'not life-threatening'.
    17. present: 'resulted in injuries to a pedestrian'.
    18. present: 'injuries to a pedestrian' stated, though noted not life-threatening
    19. present: 'resulted in injuries to a pedestrian'
    20. present: Notes injuries to the victim, though says not life-threatening, still conveys harm.
    21. present: States injuries to pedestrian, though 'not life-threatening'
    22. present: 'resulted in injuries to a pedestrian'
    23. present: 'resulted in injuries to a pedestrian'.
    24. present: States 'resulted in injuries to a pedestrian'.
    25. present: States injuries occurred though 'not life-threatening'.

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

Stanford University, a private R1 research university with approximately 17,000 students, sits on a 8,180-acre campus in Santa Clara County, California, making jurisdictional questions over campus crimes particularly complex (Stanford has its own SUDPS, but California Highway Patrol patrols campus roads, and the Santa Clara County Sheriff has primary jurisdiction over the broader county). On November 3, 2023, less than a month after the October 7 Hamas attacks and amid heightened campus tensions over the Israel-Hamas war, Stanford co-term student Abdulwahab Omira was struck by a black Toyota 4Runner at the corner of Campus Drive and Ayrshire Farm Lane on Stanford's campus. The driver made eye contact, accelerated, struck Omira, and shouted 'F*** you and your people' before fleeing. Stanford issued an AlertSU community alert that evening. From a hospital bed, Omira issued a public statement calling for 'love, compassion, and unity'. Six days later, the Santa Clara County Sheriff took over the hate-crime investigation from CHP. The case is significant because Stanford was simultaneously investigating multiple bias incidents (anti-Muslim, antisemitic, and anti-Israeli), and the AlertSU language was praised for naming the victim's Arab Muslim heritage explicitly rather than using neutral language.
Analysis

Key Findings

AlertSU explicitly named the victim's 'Arab Muslim heritage', unusually direct identity language for an initial alert, often hedged or omitted at peer institutions
Jurisdictional complexity is striking: CHP was lead initially (Campus Drive is a public road), Santa Clara County Sheriff took over for the hate-crime investigation 6 days later
The detailed vehicle description (black Toyota 4Runner, M and J plate letters) arrived in the Nov 4 morning AlertSU update (alertid=1402), not the Nov 3 initial Community Advisory
Stanford issued at least three AlertSU messages: Nov 3 Community Advisory (1401), Nov 4 suspect/vehicle update (1402), and Nov 9 Sheriff's Office handoff (1404)
The case was part of a documented surge in anti-Muslim and anti-Arab incidents on US campuses following October 7, 2023
Despite a composite sketch and detailed vehicle information, the suspect remained at large as of 2025
Outcome
The victim, identified as Stanford co-term student Abdulwahab Omira, sustained non-life-threatening injuries — bruising and abrasions — and was treated and released. The Santa Clara County Sheriff's Office took over the investigation from California Highway Patrol on November 9, 2023, classifying it as a hate crime. A composite sketch of the suspect was released; the suspect remained at large as of 2025.
Provenance

Sources

Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.

  1. Official
    Community Crime Alert – Hit and Run, Potential Hate Crime — Stanford Emergency Information (failover mirror)
    emergency-failover.stanford.edu
    archived copy
  2. Official
    Sheriff's Office further information – Hit and Run (AlertSU alertid=1404) — Stanford DPS
    police.stanford.edu
    archived copy
  3. Official
    Additional information - Hit and Run, Hate Crime Investigation (AlertSU alertid=1402) — Stanford DPS
    police.stanford.edu
    archived copy
  4. Official
    Community Advisory-Hit and Run Hate Crime (AlertSU alertid=1401) — Stanford DPS
    police.stanford.edu
    archived copy
  5. Student Paper
    Hit-and-run injures Arab Muslim student, incident under investigation as hate crime — Stanford Daily
    stanforddaily.com
    archived copy
  6. News
    Arab Muslim student struck in hit-and-run as Stanford University investigates spate of hate crime incidents — CNN
    cnn.com
    archived copy
  7. Official
    Sheriff's Office update on hit and run — Stanford Emergency Information
    emergency.stanford.edu
    archived copy
  8. News
    Arab Muslim student at Stanford injured in hit-and-run, allegedly by pro-Israel student — Palo Alto Online
    paloaltoonline.com
    archived copy
  9. News
    Stanford University: Arab Muslim student struck in hit-and-run calls for love, compassion — CNN
    cnn.com
    archived copy
Cite this case

Campus Alert Archive. "Stanford University: A driver strikes a pedestrian and flees while shouting a slur in a suspected hate crime." Incident of November 3, 2023. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/stanford-university-arab-muslim-hit-and-run-2023-11-03/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
hate-crimeislamophobiaanti-arabanti-muslimhit-and-runstanford-universitycaliforniapost-october-7alertsutimely-warningsanta-clara-countymarkaz-resource-centerUnder Investigation
Added May 2026Updated July 2026Via ingestion