Skip to content
Campus Alert Archive
UMD

Early-morning false report of a rifle near the main library; no evidence of gunfire found

AI-generated · every claim is source-linked
MDswattingemergency notificationmedium 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.

At 4:17 AM EDT on September 2, 2025, a false report of a person with an AR-style weapon was called in to Prince George's County Public Safety Communications, claiming an active shooter near McKeldin Library on UMD's campus. A UMPD officer already patrolling McKeldin Mall at that time saw and heard nothing suspicious, and the university's gunshot detection system confirmed no shots fired. UMD was one of approximately 20 universities targeted by swatting hoaxes that week.

Alerts
1
Response
—
Killed
0
Injured
0
Institution
University of Maryland, College Park
Public R1 · MD
All UMD cases →
~41,000 studentsUMD Alerts
Official alert policy
Read when and how UMD says it will use UMD Alerts: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

1 message in sequence · 1 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.

FOLLOW-UPEmail
Verified verbatim2488 chars
In recent weeks, there has been an increase of false active shooter reports, targeting institutions of higher education across the country. Approximately 20 colleges and universities have been impacted. We take these matters very seriously. Whenever we get a call that impacts our campus community, we take into account the totality of the circumstances and respond accordingly. At 4:17 a.m. today, UMPD was notified by the Prince George's County Public Safety Communications of a similar report in the McKeldin Library area. A UMPD officer was already patrolling McKeldin Mall. That officer had not heard or seen anything suspicious, and UMPD did not receive a notification from our gun-shot detection technology system. UMPD did not receive any other calls from our community reporting gunfire. With the assistance from our allied agencies and our Security Operations Center, it was determined that this call was a false report and there was no threat to our community. We understand how this can be distressing to members of our community. Below are resources that are available to you should you need to reach out. As always, we encourage our community to report suspicious activity and/or behavior to UMPD immediately by calling 301-405-3333 or through the UMD Guardian app. University of Maryland Police Department Emergency Number - 301-405-3333 / #3333 from a mobile phone (AT&T and Verizon Wireless) / 911 Non-Emergency Number - 301-405-3555 Prince George's County Police Department Emergency Number - 911 Non-Emergency Number - 301-352-1200 Office of Emergency Management and Business Continuity https://prepare.umd.edu/ for quick access to phone numbers and emergency guide UMD Guardian (Mobile Campus Safety App) https://umpdnews.umd.edu/download-umd-guardian-app-today UMD Police Walking Escort 301-405-3555 NITE Ride 301-314-3687 https://transportation.umd.edu/shuttle-um/nite-ride ADA/504 Coordinator 301-405-2841 https://accessibility.umd.edu/ Faculty Staff Assistance Program (FSAP) 301-314-8170 FSAPadmin@umd.edu https://health.umd.edu/fsap Bias Incident Support Services 301-405-0980 https://biassupport.umd.edu/ BiasSupport@umd.edu Help Center (Peer Counseling & Crisis Intervention) 301-314-4357 https://helpcenterumd.org/ Counseling Center 301-314-7651 https://counseling.umd.edu/ CARE Office (Free & Confidential resource for those impacted by Sexual & Relationship Violence) 301-741-3442 https://health.umd.edu/CARE Health Center
Verbatim text from the official UMD Advisory: False Report of Campus Incident posted to alert.umd.edu on September 2, 2025
Notably, UMPD did not send a real-time emergency alert during the incident; the advisory was issued after the call had already been determined a hoax
The 4:17 AM EDT timing minimized disruption, as few students were on campus at that hour
2026-09-21 second deep audit b50 P4 a1-noledger-single-alert-public-case. Recapture official product at product boundary. Dual html.parser walk+regex. Cap-exempt R1.
Message elements

How the first alert is built

To check this alert, Claude Opus 5.5 (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.

In recent weeks, there has been an increase of false active shooter reports, targeting institutions of higher education across the country. Approximately 20 colleges and universities have been impacted. We take these matters very seriously. Whenever we get a call that impacts our campus community, we take into account the totality of the circumstances and respond accordingly. At 4:17 a.m. today, UMPD was notified by the Prince George's County Public Safety Communications of a similar report in the McKeldin Library area. A UMPD officer was already patrolling McKeldin Mall. That officer had not heard or seen anything suspicious, and UMPD did not receive a notification from our gun-shot detection technology system. UMPD did not receive any other calls from our community reporting gunfire. With the assistance from our allied agencies and our Security Operations Center, it was determined that this call was a false report and there was no threat to our community. We understand how this can be distressing to members of our community. Below are resources that are available to you should you need to reach out. As always, we encourage our community to report suspicious activity and/or behavior to UMPD immediately by calling 301-405-3333 or through the UMD Guardian app. University of Maryland Police Department Emergency Number - 301-405-3333 / #3333 from a mobile phone (AT&T and Verizon Wireless) / 911 Non-Emergency Number - 301-405-3555 Prince George's County Police Department Emergency Number - 911 Non-Emergency Number - 301-352-1200 Office of Emergency Management and Business Continuity https://prepare.umd.edu/ for quick access to phone numbers and emergency guide UMD Guardian (Mobile Campus Safety App) https://umpdnews.umd.edu/download-umd-guardian-app-today UMD Police Walking Escort 301-405-3555 NITE Ride 301-314-3687 https://transportation.umd.edu/shuttle-um/nite-ride ADA/504 Coordinator 301-405-2841 https://accessibility.umd.edu/ Faculty Staff Assistance Program (FSAP) 301-314-8170 FSAPadmin@umd.edu https://health.umd.edu/fsap Bias Incident Support Services 301-405-0980 https://biassupport.umd.edu/ BiasSupport@umd.edu Help Center (Peer Counseling & Crisis Intervention) 301-314-4357 https://helpcenterumd.org/ Counseling Center 301-314-7651 https://counseling.umd.edu/ CARE Office (Free & Confidential resource for those impacted by Sexual & Relationship Violence) 301-741-3442 https://health.umd.edu/CARE Health Center

  • Sourcepresent25/25

    Final assessment

    All 25 reads agree the sender is identified: the message names UMPD and signs off as the University of Maryland Police Department.

    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: It names UMPD and the University of Maryland Police Department.
    2. present: University of Maryland Police Department (UMPD) is named.
    3. present: It names UMPD and is signed by the University of Maryland Police Department.
    4. present: UMPD, University of Maryland Police Department.
    5. present: It is signed by the 'University of Maryland Police Department' (UMPD).
    6. present: UMPD, the University of Maryland Police Department, is named.
    7. present: Signed by the University of Maryland Police Department.
    8. present: UMPD and the University of Maryland Police Department are named.
    9. present: The University of Maryland Police Department (UMPD) is named.
    10. present: It is signed by the University of Maryland Police Department (UMPD).
    11. present: The University of Maryland Police Department is named and signs the message.
    12. present: The University of Maryland Police Department signs the message.
    13. present: UMPD is named as the responding agency.
    14. present: The University of Maryland Police Department (UMPD) is named.
    15. present: Signed by the University of Maryland Police Department.
    16. present: UMPD and the University of Maryland Police Department are named.
    17. present: The University of Maryland Police Department is named.
    18. present: The University of Maryland Police Department (UMPD) is named.
    19. present: Signed by the University of Maryland Police Department (UMPD).
    20. present: University of Maryland Police Department.
    21. present: UMPD is named as issuer.
    22. present: It is signed by the 'University of Maryland Police Department' (UMPD).
    23. present: It is signed by the University of Maryland Police Department (UMPD).
    24. present: It is signed by the University of Maryland Police Department, UMPD.
    25. present: It names 'UMPD' repeatedly and signs with the University of Maryland Police Department contact block.
  • Hazardpresent25/25

    Final assessment

    Unanimous: the hazard is named as a false active shooter report, a swatting call, even though it was found to be no 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. present: It names a false 'active shooter' report, a swatting call.
    2. present: It names a false active shooter report.
    3. present: It names a false active shooter report.
    4. present: False active shooter report.
    5. present: It names a false 'active shooter' report, a swatting incident.
    6. present: It names a false active shooter report.
    7. present: Names a false active shooter report.
    8. present: It names a false active shooter report, a swatting call.
    9. present: It names a false active shooter report.
    10. present: It names 'false active shooter reports' and a report near McKeldin Library.
    11. present: It names a false active shooter report.
    12. present: It names a false active shooter report.
    13. present: It names a false active shooter report.
    14. present: It names a false active shooter report.
    15. present: Names false active shooter reports.
    16. present: It names a false active shooter report.
    17. present: It names a false active shooter report.
    18. present: It names a false active shooter report.
    19. present: Names a false active shooter report.
    20. present: False active shooter report.
    21. present: It names a false active shooter report.
    22. present: It names a false active shooter report.
    23. present: It names a false active shooter report.
    24. present: It names a false active shooter report.
    25. present: It describes 'false active shooter reports' and a similar report in the McKeldin Library area.
  • Locationpresent25/25

    Final assessment

    All 25 reads agree a specific place is given, the McKeldin Library area, with McKeldin Mall also mentioned.

    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: It gives 'the McKeldin Library area'.
    2. present: It gives the McKeldin Library area.
    3. present: It names the McKeldin Library area.
    4. present: McKeldin Library area.
    5. present: It gives 'the McKeldin Library area'.
    6. present: It specifies "the McKeldin Library area".
    7. present: Gives the McKeldin Library area.
    8. present: It specifies the McKeldin Library area.
    9. present: It gives the McKeldin Library area.
    10. present: It says 'the McKeldin Library area'.
    11. present: It gives "the McKeldin Library area".
    12. present: It gives the McKeldin Library area.
    13. present: It names the McKeldin Library area.
    14. present: It names the McKeldin Library area.
    15. present: 'McKeldin Library area'.
    16. present: It gives "the McKeldin Library area".
    17. present: It gives the McKeldin Library area.
    18. present: It gives the McKeldin Library area.
    19. present: McKeldin Library area.
    20. present: McKeldin Library area.
    21. present: It names the McKeldin Library area.
    22. present: It gives 'the McKeldin Library area'.
    23. present: It names 'the McKeldin Library area'.
    24. present: It gives the McKeldin Library area.
    25. present: It names 'the McKeldin Library area' and 'McKeldin Mall'.
  • Guidancepresent15/25

    Final assessment

    Present by a split 15 to 10 majority: most reads count the request to report suspicious activity to UMPD immediately by calling 301-405-3333, while a sizable minority saw only a tip request after no threat was declared.

    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: It encourages the community 'to report suspicious activity and/or behavior to UMPD immediately'.
    2. absent: It only encourages reporting suspicious activity, not a protective action.
    3. absent: It only asks for reports of suspicious activity, with no protective action, since there is no threat.
    4. present: Encourages reporting suspicious activity to UMPD.
    5. absent: It only encourages reporting suspicious activity after declaring no threat; no protective action is given.
    6. present: It encourages reporting suspicious activity to UMPD immediately or calling 911.
    7. absent: Only asks people to report suspicious activity; no protective action.
    8. absent: It only encourages reporting suspicious activity; no protective action is needed as there was no threat.
    9. absent: It only encourages reporting suspicious activity, with no protective action as the report was false.
    10. present: It encourages the community to 'report suspicious activity' to UMPD immediately.
    11. present: It encourages reporting suspicious activity to UMPD immediately.
    12. present: It encourages reporting suspicious activity to UMPD immediately.
    13. present: It tells the community to report suspicious activity immediately to UMPD.
    14. absent: It only encourages reporting suspicious activity, with no protective action since there was no threat.
    15. absent: Only encourages reporting suspicious activity; no protective action.
    16. absent: It only encourages reporting suspicious activity; no protective action.
    17. present: It urges reporting suspicious activity immediately to UMPD.
    18. present: It encourages reporting suspicious activity to UMPD.
    19. absent: Only encourages reporting suspicious activity; no protective action.
    20. present: Encourages reporting suspicious activity immediately.
    21. present: It asks people to report suspicious activity to UMPD immediately.
    22. present: It encourages reporting suspicious activity to UMPD immediately.
    23. present: It encourages reporting suspicious activity to UMPD immediately.
    24. present: It asks the community to report suspicious activity to UMPD immediately.
    25. present: It encourages the community 'to report suspicious activity and/or behavior to UMPD immediately' and lists emergency numbers.
  • Timepresent25/25

    Final assessment

    Unanimous: the message gives a clock time and recency cue, At 4:17 a.m. today.

    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: It gives 'At 4:17 a.m. today'.
    2. present: It gives 4:17 a.m. today.
    3. present: It gives '4:17 a.m. today'.
    4. present: 'At 4:17 a.m. today'.
    5. present: It gives 'At 4:17 a.m. today'.
    6. present: It gives "4:17 a.m. today".
    7. present: Gives 4:17 a.m. today.
    8. present: It gives 4:17 a.m. today.
    9. present: It gives 4:17 a.m. today.
    10. present: It gives 'At 4:17 a.m. today'.
    11. present: It gives "4:17 a.m. today".
    12. present: It gives 4:17 a.m. today.
    13. present: It gives 4:17 a.m. today.
    14. present: It gives 4:17 a.m. today.
    15. present: 'At 4:17 a.m. today'.
    16. present: It gives "4:17 a.m. today".
    17. present: It gives 4:17 a.m. today.
    18. present: It gives 'At 4:17 a.m. today'.
    19. present: 'At 4:17 a.m. today'.
    20. present: 4:17 a.m. today.
    21. present: It gives '4:17 a.m. today'.
    22. present: It gives 'At 4:17 a.m. today'.
    23. present: It gives '4:17 a.m. today'.
    24. present: It gives 4:17 a.m. today.
    25. present: It says 'At 4:17 a.m. today, UMPD was notified', giving a clock time.
  • Impactabsent0/25

    Final assessment

    All 25 reads agree impact is absent; the message says there was no threat to our community, so no harm or severity is conveyed.

    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: It states 'there was no threat to our community', conveying no harm.
    2. absent: It states there was no threat.
    3. absent: It says there was no threat, and no consequence is stated.
    4. absent: Says there was no threat; no severity.
    5. absent: It says there was 'no threat to our community', so no consequence is conveyed.
    6. absent: It says there was "no threat to our community".
    7. absent: States there was no threat to the community.
    8. absent: It says there was no threat to the community.
    9. absent: It states there was "no threat to our community".
    10. absent: It concludes there was 'no threat to our community', conveying no consequence.
    11. absent: It says there "was no threat to our community".
    12. absent: It says there was no threat and states no consequence.
    13. absent: It says there was no threat to the community.
    14. absent: It says there was no threat and states no consequence.
    15. absent: States 'no threat to our community'.
    16. absent: It says "there was no threat"; no harm is conveyed.
    17. absent: It says there was no threat; no consequence is conveyed.
    18. absent: It says there was no threat and states no consequence.
    19. absent: States there was 'no threat to our community'.
    20. absent: States there was no threat.
    21. absent: It says there was no threat and states no consequence.
    22. absent: It states there was 'no threat to our community'.
    23. absent: It concludes there was 'no threat to our community'.
    24. absent: It says there was no threat, so no harm or severity is conveyed.
    25. absent: It concludes 'there was no threat to our community', so no consequence of a hazard is conveyed.

Coded by Claude Opus 5.5

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

About this analysis
Context

Background

At 4:17 AM EDT on September 2, 2025, the University of Maryland Police Department was alerted to a report of an active shooter near McKeldin Library via Prince George's County Public Safety Communications. The caller reported a person with an AR-style weapon. However, a UMPD officer was already patrolling McKeldin Mall at that exact time and reported not seeing or hearing anything suspicious. The university's gunshot detection technology system also had not triggered, providing a second layer of counter-evidence. With assistance from allied agencies and the Security Operations Center, the call was quickly determined to be a false report. UMD was among the victims of an escalating wave of swatting targeting college campuses, with approximately 20 universities hit by similar hoaxes that week alone. By mid-September 2025, at least 45 colleges and universities had been victimized during the fall semester. The 4:17 AM EDT timing of the call minimized disruption, as few students were on campus.
Analysis

Key Findings

UMD's gunshot detection system and a patrolling officer provided immediate counter-evidence, enabling rapid confirmation of the false alarm
The 4:17 AM EDT timing minimized disruption but also meant fewer potential witnesses to corroborate or refute the report
UMD was one of approximately 20 universities targeted by swatting hoaxes in a single week during fall 2025
Outcome
The report was quickly determined to be a false alarm with help from allied agencies and the Security Operations Center. No evidence of gunfire, no weapon, no injuries. The incident was part of a nationwide wave of swatting targeting approximately 20 universities.
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. Student Paper
  2. News
  3. News
  4. News
  5. Source
  6. Official
Cite this case

Campus Alert Archive. "University of Maryland, College Park: Early-morning false report of a rifle near the main library; no evidence of gunfire found." Incident of September 2, 2025. Added May 2026; last updated September 2026. https://campusalertarchive.com/case/university-of-maryland-swatting-2025-09-02/

Download case JSON

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

Tags
swattingmarylandhoaxgunshot-detectionwave-of-threatspublic-universityovernight-incidentHoax
Added May 2026Updated September 2026Via ingestion