Skip to content
Campus Alert Archive
Wake Forest

Swatting call during finals week confirmed false within about 24 minutes

AI-generated · every claim is source-linked
NCswattingemergency 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 the morning of May 5, 2026, Wake Forest University Police and Winston-Salem Police responded to a swatting call on the Reynolda Campus during the final week of the spring semester. The initial Wake Alert was issued at 11:50 a.m. EDT, with a follow-up alert at 12:14 p.m. EDT confirming the call was a false report consistent with swatting. It marked Wake Forest's second high-profile swatting since 2023.

Alerts
2
Response
Killed
Injured
Institution
Wake Forest University
Private R1 · NC
All Wake Forest cases →
~9,100 studentsWake Alert
Documented Timeline

Alert Sequence

2 messages in sequence · 2 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 ALERTWebsite
Verified verbatim121 chars
Wake Alert Emergency: Heavy police presence on campus. There is no active threat to campus. Updates at wakealert.wfu.edu.
Corrected to full text from https://wakealert.wfu.edu/2026/05/heavy-police-presence/ (byline May 5, 2026 11:50 a.m.).
Explicitly states no active threat while explaining heavy police presence during swatting assessment.
UPDATEWebsite+24 min
Verified verbatim492 chars
University Police, in coordination with the Winston-Salem Police Department, responded to a report of a swatting attempt on the Reynolda campus this morning. The report has been determined to be false and consistent with a swatting call. There is no threat to the campus community. Out of an abundance of caution, officers responded with a visible law enforcement presence while the report was being assessed. Updates will be shared at wakealert.wfu.edu if more information becomes available.
Sent at approximately 12:14 p.m. EDT on May 5, 2026, about 24 minutes after the initial alert, with an update at 12:16 p.m. EDT; the exact wording was confirmed from the Wake Alert archive and reproduced in WFMY News 2 reporting
The update explicitly named 'swatting' rather than 'hoax', a vocabulary shift increasingly common among universities responding to the fall 2025 Purgatory wave
Wake Forest did not enter formal lockdown; officers swept buildings while classes continued elsewhere on the Reynolda Campus
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.

Wake Alert Emergency: Heavy police presence on campus. There is no active threat to campus. Updates at wakealert.wfu.edu.

  • Sourcepresent25/25

    Final assessment

    Unanimous agreement the branded 'Wake Alert Emergency' signature identifies the issuing system.

    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: 'Wake Alert' branded signature.
    2. present: 'Wake Alert Emergency' branded signature.
    3. present: 'Wake Alert Emergency' branded signature.
    4. present: Branded "Wake Alert Emergency" signature.
    5. present: 'Wake Alert Emergency' branded signature.
    6. present: 'Wake Alert Emergency' branded signature.
    7. present: 'Wake Alert Emergency' branded signature.
    8. present: 'Wake Alert Emergency' identifies sender.
    9. present: 'Wake Alert Emergency' branded signature identifies the system.
    10. present: Labeled "Wake Alert Emergency"
    11. present: Wake Alert identifies the sender.
    12. present: Wake Alert Emergency branding identifies issuer.
    13. present: Branded 'Wake Alert Emergency' signature.
    14. present: Labeled 'Wake Alert Emergency'.
    15. present: Wake Alert Emergency names the issuing system.
    16. present: Branded "Wake Alert Emergency."
    17. present: 'Wake Alert Emergency' branded signature.
    18. present: 'Wake Alert Emergency' signature identifies sender.
    19. present: 'Wake Alert Emergency' branded signature.
    20. present: "Wake Alert Emergency" branded signature
    21. present: Branded 'Wake Alert Emergency' signature identifies the issuer.
    22. present: Labeled Wake Alert Emergency with wakealert.wfu.edu reference.
    23. present: 'Wake Alert Emergency' branded signature identifies the sender.
    24. present: Branded 'Wake Alert Emergency' signature.
    25. present: 'Wake Alert Emergency' branded signature.
  • Hazardabsent0/25

    Final assessment

    Unanimous agreement that 'heavy police presence' is too generic to count as a specific named hazard, especially with the message stating no active threat.

    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. absent: 'Heavy police presence' is vague, no specific hazard type named.
    2. absent: 'police presence' is generic, no specific threat named.
    3. absent: Only 'heavy police presence' generically named, no specific threat.
    4. absent: "Heavy police presence" is not a specific hazard type.
    5. absent: 'Heavy police presence' is vague, no specific hazard named.
    6. absent: 'police presence' is generic, no specific hazard named.
    7. absent: 'Heavy police presence' is generic, no specific threat named.
    8. absent: 'police presence' is generic, no specific hazard named.
    9. absent: Only 'heavy police presence', not a specific hazard named.
    10. absent: Only "heavy police presence" stated, no specific hazard named
    11. absent: Heavy police presence does not name a specific hazard.
    12. absent: 'Heavy police presence' generic, no specific hazard named.
    13. absent: Only 'Heavy police presence', no specific hazard named.
    14. absent: Only 'Heavy police presence', no specific hazard named; states 'no active threat'.
    15. absent: Only 'heavy police presence' named, no specific threat type.
    16. absent: Only "heavy police presence," too vague to name a specific hazard.
    17. absent: 'Heavy police presence' is generic, not a specific hazard type.
    18. absent: 'Heavy police presence' is generic, no specific hazard named.
    19. absent: 'police presence' is generic, no specific hazard named.
    20. absent: "police presence" is generic, no specific hazard named
    21. absent: Only describes 'Heavy police presence', explicitly stating 'no active threat.'
    22. absent: Only 'heavy police presence' named, no specific threat type given.
    23. absent: Only 'Heavy police presence' generic term, no specific hazard type named.
    24. absent: 'Heavy police presence' is generic, no specific threat named, and text states 'no active threat'.
    25. absent: 'police presence' is generic, no specific hazard type named.
  • Locationpresent18/25

    Final assessment

    Reads split roughly 17 to 7, but the clear majority accepted the generic 'on campus' reference as meeting the location bar, so location is marked present.

    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: Only 'on campus' generally, no specific building or area.
    2. present: 'on campus' referenced generally.
    3. present: 'on campus' referenced.
    4. present: "On campus" referenced.
    5. present: 'on campus' referenced.
    6. present: 'on campus' referenced.
    7. present: 'on campus'.
    8. present: 'on campus.'
    9. present: References campus generically.
    10. absent: No specific location beyond "campus" generically
    11. present: States on campus.
    12. absent: No specific location given beyond 'on campus'.
    13. present: States 'on campus'.
    14. present: References 'campus'.
    15. absent: Only 'campus' referenced generically, no specific area.
    16. absent: Only says "on campus," too generic to count as a specific location.
    17. present: 'on campus'.
    18. present: 'on campus' referenced.
    19. absent: Only 'on campus' generic reference, no specific place.
    20. present: "on campus" referenced
    21. absent: Only vaguely references 'campus', no specific building or area.
    22. present: On campus specified generally.
    23. present: 'campus' generically referenced.
    24. present: Refers to 'campus'.
    25. present: 'on campus' given.
  • Guidanceabsent0/25

    Final assessment

    Unanimous agreement no protective action is instructed; the message only gives a status update.

    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. absent: No protective action instructed, only status update given.
    2. absent: No protective action instructed, just states no active threat.
    3. absent: No protective action instructed, states there is no active threat.
    4. absent: No protective action instructed.
    5. absent: No protective action instructed.
    6. absent: No protective action given, only status update.
    7. absent: No protective action instructed.
    8. absent: No protective action instructed.
    9. absent: No protective action instructed.
    10. absent: No protective action instructed
    11. absent: No protective instruction is given.
    12. absent: No protective action instructed.
    13. absent: No protective instruction given, only status update.
    14. absent: No protective action instructed.
    15. absent: No protective action instructed.
    16. absent: No protective action instructed.
    17. absent: No protective instruction given.
    18. absent: No protective action instructed to recipients.
    19. absent: No protective action instructed, only 'no active threat'.
    20. absent: No protective action instructed
    21. absent: No protective action instructed.
    22. absent: No protective action instructed, states no active threat.
    23. absent: No protective action instructed, states no active threat to campus.
    24. absent: No protective action instructed.
    25. absent: No protective action instructed; states no active threat.
  • Timeabsent0/25

    Final assessment

    Unanimous agreement no clock time, date, or recency marker 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. absent: No clock time or date given.
    2. absent: No clock time or recency marker given.
    3. absent: No clock time or recency marker given.
    4. absent: No clock time or date given.
    5. absent: No clock time or date given.
    6. absent: No clock time given.
    7. absent: No clock time or date given.
    8. absent: No time reference given.
    9. absent: No clock time or date given.
    10. absent: No clock time or date given
    11. absent: No time or recency reference given.
    12. absent: No clock time or date given.
    13. absent: No clock time or date given.
    14. absent: No clock time or date given.
    15. absent: No specific time given.
    16. absent: No clock time or date given.
    17. absent: No time given.
    18. absent: No clock time or recency term given.
    19. absent: No clock time or date given.
    20. absent: No clock time or date given
    21. absent: No clock time or date given.
    22. absent: No clock time or date given.
    23. absent: No clock time or recency marker present.
    24. absent: No clock time or date given.
    25. absent: No clock time or date given.
  • Impactabsent0/25

    Final assessment

    Unanimous agreement the explicit 'no active threat to campus' statement negates any stated consequence or severity.

    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: 'no active threat to campus' states no impact.
    2. absent: No stated consequence, explicitly 'no active threat'.
    3. absent: States 'no active threat to campus', no stated consequence.
    4. absent: States no active threat, no severity conveyed.
    5. absent: 'no active threat to campus' negates stated harm.
    6. absent: Explicitly states 'no active threat to campus'.
    7. absent: States 'no active threat to campus', no stated harm.
    8. absent: 'no active threat to campus' explicitly negates harm.
    9. absent: States no active threat, no stated consequence or severity.
    10. absent: States no active threat to campus, no consequence conveyed
    11. absent: States there is no active threat, no consequence conveyed.
    12. absent: States no active threat, no consequence stated.
    13. absent: States no active threat, no stated harm severity.
    14. absent: No stated consequence or severity.
    15. absent: States no active threat, no stated harm.
    16. absent: No stated consequence or severity.
    17. absent: States 'no active threat to campus', no consequence.
    18. absent: States 'no active threat to campus,' no stated potential harm.
    19. absent: 'no active threat to campus' states no danger.
    20. absent: States "no active threat," no stated danger
    21. absent: No stated consequence; explicitly says no active threat.
    22. absent: States no active threat, no consequence conveyed.
    23. absent: No stated consequence, message states 'no active threat'.
    24. absent: No stated consequence or severity.
    25. absent: States 'no active threat,' no severity conveyed.

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

About this analysis
Context

Background

On the morning of May 5, 2026, Wake Forest University Police and the Winston-Salem Police Department responded to a swatting attempt on the Reynolda Campus, the main residential campus in northwest Winston-Salem. The first Wake Alert went out at 11:50 a.m. EDT with the standard 'Heavy police presence on campus' template; that same message was revised at 12:01 p.m., and a second, follow-up alert at 12:14 p.m. EDT confirmed the report was false and consistent with swatting. Officers responded out of an abundance of caution; no buildings were locked down and no suspect was identified. The 24-minute interval between the initial alert and the confirming update was far faster than the 82-minute delay that triggered scandal at the University of Pittsburgh under a similar swatting attack two years earlier; public sources do not document a comparable minute-by-minute interval for Wake Forest's own April 2023 hoax at Reynolda, so no direct before/after comparison can be drawn for Wake Forest specifically. This incident came amid a year of false active-shooter calls that had hit dozens of US colleges since the Purgatory group's August 2025 spree.
Analysis

Key Findings

The confirming update arrived about 24 minutes after the initial alert, far faster than Pittsburgh's notorious 82-minute delay in a comparable swatting incident, though public sources do not document a comparable interval for Wake Forest's own April 2023 response, so no improvement claim can be substantiated from the record alone
Wake Forest used the deliberately vague 'Heavy police presence on campus' template rather than naming the threat, a hedging strategy increasingly common in 2025-2026 swatting responses
May 5 fell during finals week; the timing maximized disruption to students preparing for exams, a pattern noted in several 2025-2026 swatting cases
Outcome
Officers responded with a visible law enforcement presence while the report was assessed. The report was determined to be false within roughly 24 minutes of the first alert. No injuries, no weapon recovered, and no suspect identified at the time of all-clear.
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. News
  2. national media
  3. Official
  4. News
  5. Official
  6. Official
Cite this case

Campus Alert Archive. "Wake Forest University: Swatting call during finals week confirmed false within about 24 minutes." Incident of May 5, 2026. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/wake-forest-university-swatting-reynolda-2026-05-05/

Download case JSON

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

Tags
swattingwake-alertreynoldanorth-carolinafinals-weekprivate-r1accHoax
Added May 2026Updated July 2026Via ingestion