Skip to content
Campus Alert Archive
OSU

Bomb threat against food delivery robots; fleet isolated and a student arrested

AI-generated · every claim is source-linked
ORbomb threatemergency notificationhigh confidence
Confirmed HoaxDetermined to be a hoax. The institutional response is documented because it reveals how the alert system performed under a perceived real threat.

On October 24, 2023, Oregon State University issued an urgent alert warning students to avoid all food delivery robots after receiving a bomb threat targeting the Starship Technologies fleet on the Corvallis campus. The threat proved to be a prank posted on social media by a student who was subsequently arrested.

Alerts
2
Response
29 min
Killed
Injured
Institution
Oregon State University
Public R1 · OR
All OSU cases →
~34,000 studentsOSU Alert
Official alert policy
Read when and how OSU says it will use OSU Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

2 messages in sequence · 2 verified verbatim

INITIAL ALERTPush
Urgent OSU Alert: Bomb Threat in Starship food delivery robots. Do not open robots. Avoid all robots until further notice. Public Safety is responding.
Verbatim text from Oregon State University's official X post at 12:20 PM PDT on October 24, 2023
The alert was issued approximately 30 minutes after the Department of Public Safety received the threat report at 11:51 AM PDT
The phrase 'Avoid all robots' became a widely shared headline across national media
ALL CLEARPush+1h 25m
Emergency is over. You may now resume normal activities.
Verbatim 'Emergency is over. You may now resume normal activities.' quoted by NBC News from the 1:45 PM PDT OSU Alert push notification
Issued at approximately 1:45 PM PDT, roughly 85 minutes after the 12:20 PM PDT initial 'Avoid all robots' alert
By 1:52 PM PDT on October 24, 2023, all robots had been inspected by a bomb-detection K-9 and no explosive devices were found
A student, Ted Daniel Stock, was arrested in connection with the threat, which authorities said was posted on social media
The terse 56-character all-clear contrasts with the 151-character initial alert, characteristic of return-to-normal messages that minimize alarm
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.

Urgent OSU Alert: Bomb Threat in Starship food delivery robots. Do not open robots. Avoid all robots until further notice. Public Safety is responding.

  • Sourcepresent25/25

    Final assessment

    Unanimous: it opens with the branded Urgent OSU Alert tag and names Public Safety, identifying the sender.

    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: Branded "Urgent OSU Alert" and names "Public Safety".
    2. present: It opens "Urgent OSU Alert" and names "Public Safety", the branded sender.
    3. present: Branded "OSU Alert" and "Public Safety" identify the sender and authority.
    4. present: The branded tag "OSU Alert" and "Public Safety" identify sender and authority.
    5. present: Opens with "Urgent OSU Alert" branding and names "Public Safety".
    6. present: It opens with "Urgent OSU Alert" and names "Public Safety", identifying the sender.
    7. present: The branded "OSU Alert" tag and "Public Safety" identify the sender and responder.
    8. present: Opens "Urgent OSU Alert" and names "Public Safety", identifying the sender.
    9. present: Branded "Urgent OSU Alert" and names "Public Safety".
    10. present: It opens with the branded "OSU Alert" signature and names "Public Safety".
    11. present: The branded "OSU Alert" and "Public Safety" identify the sender.
    12. present: Branded "Urgent OSU Alert" and "Public Safety" identify the sender.
    13. present: Opens with "Urgent OSU Alert" and names "Public Safety", identifying the sender.
    14. present: The branded "OSU Alert" and "Public Safety" identify the sender and authority.
    15. present: The branded "Urgent OSU Alert" plus "Public Safety" identifies the sender.
    16. present: Opens with branded "Urgent OSU Alert" and names "Public Safety".
    17. present: The "OSU Alert" signature identifies Oregon State University and "Public Safety" responding.
    18. present: It opens with "Urgent OSU Alert" and names "Public Safety".
    19. present: It opens with "Urgent OSU Alert" and references "Public Safety".
    20. present: It opens with "Urgent OSU Alert" and names "Public Safety", identifying the sender.
    21. present: Opens with branded "OSU Alert" and names "Public Safety".
    22. present: Opens with "Urgent OSU Alert" and names "Public Safety".
    23. present: The branded "OSU Alert" tag and "Public Safety" identify the sender.
    24. present: The branded "OSU Alert" tag and "Public Safety" identify the sender.
    25. present: The branded "OSU Alert" signature and "Public Safety" identify the sender.
  • Hazardpresent25/25

    Final assessment

    Unanimous: it names a bomb threat in Starship food delivery robots, a specific hazard.

    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: Names a "Bomb Threat in Starship food delivery robots", a specific hazard.
    2. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    3. present: Names "Bomb Threat in Starship food delivery robots", a specific threat.
    4. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    5. present: States a "Bomb Threat in Starship food delivery robots", a specific threat.
    6. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    7. present: It cites a "Bomb Threat in Starship food delivery robots", a specific threat.
    8. present: States a "Bomb Threat in Starship food delivery robots", a specific threat.
    9. present: States "Bomb Threat in Starship food delivery robots", a specific threat.
    10. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    11. present: It states "Bomb Threat in Starship food delivery robots", a specific threat.
    12. present: Names a "Bomb Threat in Starship food delivery robots", a specific threat.
    13. present: States "Bomb Threat in Starship food delivery robots", a specific threat.
    14. present: It names a "Bomb Threat in Starship food delivery robots", a specific hazard.
    15. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    16. present: Names "Bomb Threat in Starship food delivery robots", a specific threat.
    17. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    18. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    19. present: It reports a "Bomb Threat in Starship food delivery robots", a specific threat.
    20. present: It states "Bomb Threat in Starship food delivery robots", a specific named threat.
    21. present: States a "Bomb Threat in Starship food delivery robots", a specific threat.
    22. present: Names "Bomb Threat in Starship food delivery robots", a specific threat.
    23. present: It names a "Bomb Threat in Starship food delivery robots", a specific threat.
    24. present: It names "Bomb Threat in Starship food delivery robots", a specific threat.
    25. present: It names a "Bomb Threat in Starship food delivery robots".
  • Locationabsent12/25

    Final assessment

    Nearly even split: a slim majority found no building, street, or campus area named beyond the mobile robots, so location is coded absent; many reads treated the robots themselves as the location.

    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. absent: Names only the robots, no building, street, or campus area location.
    2. present: It refers to "all robots" on campus, a location/object reference.
    3. absent: No building, street, named campus place is given, only the mobile robots.
    4. present: It references the "robots" as the location of concern, a specific object/place.
    5. present: Says the threat is in "Starship food delivery robots", a specific (mobile) object location on campus.
    6. absent: It references robots but names no building, area, or campus location.
    7. present: It refers to the "robots" as the location, a specific object location on campus.
    8. present: Says the threat is "in Starship food delivery robots", identifying the objects/places to avoid.
    9. present: Locates the threat in the "robots" on campus.
    10. present: It refers to the robots and "all robots" on campus as the location focus.
    11. absent: No building, hall, street, or campus area is named beyond the robots themselves.
    12. present: Locates it in the "Starship food delivery robots" on campus.
    13. absent: No building, street, or campus area is named; it refers only to robots.
    14. absent: It references the robots but gives no building, street, or campus area location.
    15. absent: No building, street, area, or "campus" location is named, only the robots themselves.
    16. absent: No building, street, or campus area is named, only the robots themselves.
    17. absent: It names robots but no building, street, area, or campus location.
    18. absent: It locates it only in "Starship food delivery robots" generally, not a building or area.
    19. absent: No building, street, or campus area is named; only the robots are referenced.
    20. present: It locates the threat in "Starship food delivery robots", a specific object location on campus.
    21. absent: Names only the robots, not a building, street, area, or campus location.
    22. present: References "all robots" on campus as the location of concern.
    23. present: It locates the threat in the "robots" across campus.
    24. absent: It names the robots but no building, area, or campus location.
    25. present: It locates the threat in the "Starship food delivery robots" on campus.
  • Guidancepresent25/25

    Final assessment

    Unanimous: it instructs people not to open robots and to avoid all robots until further notice, clear protective guidance.

    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: Instructs "Do not open robots. Avoid all robots until further notice".
    2. present: It instructs recipients to "Do not open robots. Avoid all robots until further notice".
    3. present: Instructs recipients "Do not open robots. Avoid all robots until further notice".
    4. present: It instructs "Do not open robots. Avoid all robots until further notice", protective actions.
    5. present: Instructs "Do not open robots. Avoid all robots until further notice".
    6. present: It instructs "Do not open robots. Avoid all robots until further notice".
    7. present: It instructs "Do not open robots. Avoid all robots until further notice", protective actions.
    8. present: Instructs "Do not open robots. Avoid all robots until further notice", protective actions.
    9. present: Instructs "Do not open robots. Avoid all robots until further notice".
    10. present: It instructs to "Do not open robots. Avoid all robots until further notice".
    11. present: It instructs recipients "Do not open robots. Avoid all robots until further notice".
    12. present: Instructs recipients: "Do not open robots. Avoid all robots until further notice".
    13. present: Instructs "Do not open robots. Avoid all robots until further notice", protective actions.
    14. present: It instructs recipients to "Do not open robots. Avoid all robots until further notice".
    15. present: It instructs "Do not open robots. Avoid all robots until further notice", protective actions.
    16. present: Instructs "Do not open robots. Avoid all robots until further notice".
    17. present: It instructs "Do not open robots. Avoid all robots until further notice".
    18. present: It instructs recipients to "Do not open robots. Avoid all robots until further notice".
    19. present: It instructs recipients to "Do not open robots. Avoid all robots until further notice".
    20. present: It instructs "Do not open robots. Avoid all robots until further notice", protective actions.
    21. present: Instructs "Do not open robots. Avoid all robots until further notice".
    22. present: Instructs "Do not open robots. Avoid all robots until further notice."
    23. present: It instructs "Do not open robots. Avoid all robots until further notice".
    24. present: It instructs "Do not open robots. Avoid all robots until further notice".
    25. present: It instructs recipients "Do not open robots. Avoid all robots until further notice".
  • Timepresent25/25

    Final assessment

    Unanimous: it says until further notice, a duration and recency cue, so timing is present.

    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: Says "until further notice", a recency cue.
    2. present: It says "until further notice", a duration/recency cue.
    3. present: Says "until further notice", a duration/recency cue.
    4. present: The phrase "until further notice" conveys timing duration.
    5. present: Uses "until further notice", a recency/duration cue.
    6. present: It uses "until further notice", a duration or recency cue.
    7. present: "until further notice" conveys a recency/duration cue.
    8. present: Says "until further notice", a recency and duration cue.
    9. present: Uses "until further notice", a duration cue.
    10. present: It says "until further notice", a recency cue.
    11. present: It says "until further notice", a recency cue.
    12. present: Says "until further notice", a duration/recency cue.
    13. present: Uses "until further notice", a recency/duration cue.
    14. present: It uses "until further notice", a recency and duration cue.
    15. present: It uses "until further notice", a recency and duration cue.
    16. present: Includes "until further notice", a temporal cue.
    17. present: It says "until further notice", a recency/duration cue.
    18. present: It uses "until further notice", a recency/duration cue.
    19. present: It says "until further notice", a recency cue.
    20. present: It says "until further notice", a recency or duration cue.
    21. present: Uses "until further notice", a recency/duration cue.
    22. present: Uses recency cue "until further notice".
    23. present: The phrase "until further notice" conveys a time frame.
    24. present: It says "until further notice", a recency cue.
    25. present: It says "until further notice", a duration/recency cue.
  • Impactpresent20/25

    Final assessment

    Present, with strong agreement (20 of 25). A bomb threat in delivery robots with do-not-open instructions implies explosive detonation danger; dissenters held the text only names the threat without stating harm.

    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. absent: A bomb threat in delivery robots with do-not-open instructions is named but states no consequence or harm.
    2. present: Reports a bomb threat in delivery robots and warns not to open them, implying explosive danger and potential harm.
    3. present: Warns of a bomb threat in delivery robots and to not open them, implying explosive danger to people.
    4. present: A bomb threat in delivery robots with do-not-open instruction implies explosive danger.
    5. absent: It reports a bomb threat in robots and to not open them but states no consequence or potential harm.
    6. present: A bomb threat warning not to open delivery robots implies the risk of an explosion harming people.
    7. present: Warns of a bomb threat in delivery robots and says do not open them, implying explosive danger to people.
    8. present: Bomb threat in delivery robots with do not open them, implying danger from a possible explosive.
    9. present: Warns of a bomb threat in delivery robots and to not open or approach robots, implying an explosive device danger.
    10. present: A bomb threat with do-not-open and avoid-all-robots instructions implies the danger of an explosive device.
    11. present: It warns of a bomb threat in delivery robots and to not open them, implying explosive danger.
    12. present: Names a bomb threat in delivery robots and warns do not open robots, implying explosive danger to people.
    13. present: A bomb threat in delivery robots with do-not-open instructions implies an explosive danger to people.
    14. absent: Reports a bomb threat in delivery robots and to not open them but states no potential harm or severity.
    15. present: It warns of a bomb threat in delivery robots and not to open them, implying an explosive danger.
    16. present: A bomb threat in delivery robots with do-not-open warnings implies danger of an explosive device.
    17. present: Reports a bomb threat and warns not to open robots, implying potential explosive harm.
    18. present: It reports a bomb threat inside delivery robots and warns not to open them, implying an explosive danger.
    19. present: A bomb threat in delivery robots with do-not-open implies the danger of an explosive device.
    20. present: Warns of a bomb threat in robots and not to open them, implying explosive danger.
    21. absent: It reports a bomb threat in delivery robots and tells people not to open them but states no danger or potential harm.
    22. present: A bomb threat in delivery robots with explicit instructions not to open them implies an explosive detonation danger.
    23. present: Names a bomb threat in delivery robots and warns not to open them, implying explosive danger to people; however no explicit harm stated, the warning not to open robots implies danger, code present.
    24. absent: Names a bomb threat in delivery robots and says not to open them but states no potential harm or severity.
    25. present: Names a bomb threat and warns not to open robots, implying detonation danger requiring precautions.

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

About this analysis
Context

Background

At 11:51 AM PDT on October 24, 2023, the OSU Department of Public Safety received a report indicating an improvised explosive device would be placed in a Starship Technologies food delivery robot on the Corvallis campus. The university issued an alert at 12:20 PM PDT telling students to avoid all robots and not open them. Out of an abundance of caution, Public Safety began remotely isolating robots in a safe location for inspection by a law enforcement dog trained in bomb detection. By 1:52 PM PDT, all robots had been inspected and no explosive devices were found. The threat was determined to be a prank posted on social media by a student. The suspect, identified as Ted Daniel Stock, was taken into police custody. Starship Technologies suspended its campus delivery service following the incident. The unusual nature of the threat, targeting autonomous delivery robots rather than a building, generated widespread national media coverage.
Analysis

Key Findings

The threat targeted autonomous food delivery robots rather than buildings, representing a novel category of campus bomb threat
All robots were remotely isolated and cleared by a K-9 unit within approximately two hours of the initial report
The incident generated national media attention due to the unusual 'avoid all robots' advisory
Outcome
All robots were remotely isolated and inspected by a bomb-detection K-9 unit; no explosives were found. A student, Ted Daniel Stock, was arrested in connection with the threat. Starship suspended campus service following the incident.
Provenance

Sources

  1. Social
  2. News
  3. News
  4. News
Cite this case

Campus Alert Archive. "Oregon State University: Bomb threat against food delivery robots; fleet isolated and a student arrested." Incident of October 24, 2023. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/oregon-state-university-bomb-threat-2023-10-24/

Download case JSON

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

Tags
bomb-threathoaxdelivery-robotsstarshiporegonnovel-threatsocial-mediaprankverbatim-confirmedHoax
Added May 2026Updated July 2026Via ingestion