Campus Alert Archive
MSU

Live 'ACTIVE VIOLENCE INCIDENT' alert sent during a system test; corrected in two minutes

AI-generated · every claim is source-linked
MIpolice activitytesthigh confidence
Compare →
UnfoundedNo evidence of an actual threat was found. The institutional response is documented because the alert communication is identical to what would occur during a real incident.

A Security Operations Center employee running a routine, monthly scenario-based test of MSU's emergency notification system accidentally sent a live 'ACTIVE VIOLENCE INCIDENT' alert to the entire campus at 10:51 a.m. EST on Tuesday, February 10, 2026, three days before the anniversary of the 2023 MSU shooting. MSU Police Chief Mike Yankowski said the employee believed they were working in a designated test environment but were actually operating the live alert system, and a correction went out two minutes later.

Alerts
2
Response
—
Killed
—
Injured
—
Institution
Michigan State University
Public R1 · MI
All MSU cases →
~50,000 studentsMSU Alert
Official alert policy
Read when and how MSU says it will use MSU Alert: summarized, quoted, and analyzed.
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 ALERTMulti-channel
Verified verbatim274 chars
[DRILL] EMERGENCY! EAST LANSING ACTIVE VIOLENCE INCIDENT! [DRILL] EMERGENCY! ACTIVE VIOLENCE INCIDENT at the Michigan State University East Lansing campus. Avoid the area. If on campus RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT! Monitor alert.msu.edu for more information.
Verify this quote
MSU Alert official archive (verbatim full drill message including RUN/HIDE/FIGHT)alert.msu.edufind archived copies
Official archive preserves the dual [DRILL] tags and full RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT template
Transmitted through live campus-wide channel during monthly scenario training three days before 2023 shooting anniversary
CORRECTIONMulti-channel+2 min
Verified verbatim347 chars
ERROR - EAST LANSING! MSU East Lansing: The recent Active Violence Incident message was sent in error. Please disregard that alert. We regret any undue stress or inconvenience caused, and steps are being taken to prevent such errors from occurring in the future. Visit alert.msu.edu to learn more about emergency notifications and timely warnings.
Verify this quote
MSU Alert official archive (verbatim error/correction message)alert.msu.edufind archived copies
ERROR prefix and fuller apology/remediation language preserved from official archive
Sent ~2 minutes after the false drill message
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.

[DRILL] EMERGENCY! EAST LANSING ACTIVE VIOLENCE INCIDENT! [DRILL] EMERGENCY! ACTIVE VIOLENCE INCIDENT at the Michigan State University East Lansing campus. Avoid the area. If on campus RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT! Monitor alert.msu.edu for more information.

  • Sourcepresent25/25

    Final assessment

    Unanimous: the message references "Michigan State University East Lansing campus" and points to alert.msu.edu, identifying the issuing system despite being a drill.

    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: 'Michigan State University' named, plus drill framing implies institutional alert
    2. present: Implied East Lansing/MSU system via alert.msu.edu reference.
    3. present: References Michigan State University
    4. present: 'MSU' Michigan State University identified as the affected system, framed as a drill.
    5. present: 'Michigan State University' campus named as sender context, monitor msu.edu
    6. present: Labeled '[DRILL]' notice from East Lansing/MSU system, links alert.msu.edu.
    7. present: Names 'Michigan State University East Lansing campus' and references alert.msu.edu.
    8. present: Mentions 'alert.msu.edu' and describes an MSU incident, identifying the system.
    9. present: 'Monitor alert.msu.edu' implies MSU as issuing source
    10. present: Michigan State University East Lansing campus named as issuer context.
    11. present: EAST LANSING, Michigan State University, alert.msu.edu
    12. present: 'Michigan State University' and 'alert.msu.edu' identify the sender.
    13. present: 'MSU' Michigan State University named, though flagged as a DRILL.
    14. present: Points to "alert.msu.edu" and is an MSU-branded alert (though a drill).
    15. present: 'EAST LANSING' and monitor 'alert.msu.edu' implies MSU
    16. present: 'Michigan State University East Lansing campus' identifies sender context via alert.msu.edu.
    17. present: Labeled 'EMERGENCY!' drill referencing 'Michigan State University' campus
    18. present: Mentions Michigan State University; 'alert.msu.edu' identifies sender system.
    19. present: References Michigan State University East Lansing campus and directs to alert.msu.edu.
    20. present: References "Michigan State University" and "alert.msu.edu".
    21. present: References 'East Lansing' MSU campus and is a system alert (labeled DRILL).
    22. present: References 'Michigan State University East Lansing campus' and alert.msu.edu.
    23. present: 'MSU' 'Michigan State University' identified via 'alert.msu.edu' and message context.
    24. present: Michigan State University East Lansing campus named
    25. present: References Michigan State University and monitor 'alert.msu.edu'.
  • Hazardpresent25/25

    Final assessment

    Unanimous: "ACTIVE VIOLENCE INCIDENT" names the hazard, though the message is labeled a drill.

    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: 'ACTIVE VIOLENCE INCIDENT'
    2. present: Active violence incident named, though marked drill.
    3. present: 'ACTIVE VIOLENCE INCIDENT' names the hazard
    4. present: States 'ACTIVE VIOLENCE INCIDENT'.
    5. present: 'ACTIVE VIOLENCE INCIDENT' names hazard, though tagged [DRILL]
    6. present: 'ACTIVE VIOLENCE INCIDENT' named.
    7. present: Names 'ACTIVE VIOLENCE INCIDENT'.
    8. present: 'ACTIVE VIOLENCE INCIDENT' names the specific hazard.
    9. present: 'ACTIVE VIOLENCE INCIDENT'
    10. present: 'Active violence incident' named, though flagged as drill.
    11. present: ACTIVE VIOLENCE INCIDENT
    12. present: 'ACTIVE VIOLENCE INCIDENT' names the specific hazard, though this is a drill.
    13. present: 'ACTIVE VIOLENCE INCIDENT' names hazard.
    14. present: "ACTIVE VIOLENCE INCIDENT" names the hazard.
    15. present: 'ACTIVE VIOLENCE INCIDENT'
    16. present: 'ACTIVE VIOLENCE INCIDENT' names the hazard, marked as drill.
    17. present: Names 'ACTIVE VIOLENCE INCIDENT'
    18. present: 'ACTIVE VIOLENCE INCIDENT' names the hazard.
    19. present: 'ACTIVE VIOLENCE INCIDENT' named, though flagged as drill.
    20. present: States "ACTIVE VIOLENCE INCIDENT".
    21. present: 'ACTIVE VIOLENCE INCIDENT' names the hazard.
    22. present: 'ACTIVE VIOLENCE INCIDENT' names the hazard, though marked DRILL.
    23. present: 'ACTIVE VIOLENCE INCIDENT' names hazard.
    24. present: Active violence incident
    25. present: 'ACTIVE VIOLENCE INCIDENT' names hazard (labeled DRILL).
  • Locationpresent25/25

    Final assessment

    Unanimous: "East Lansing campus" gives 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. present: 'East Lansing campus'
    2. present: Michigan State University East Lansing campus given.
    3. present: 'East Lansing campus'
    4. present: Names 'East Lansing campus'.
    5. present: 'East Lansing campus'
    6. present: 'Michigan State University East Lansing campus'.
    7. present: References 'East Lansing campus'.
    8. present: 'East Lansing campus' names the location.
    9. present: 'Michigan State University East Lansing campus'
    10. present: East Lansing campus named.
    11. present: Michigan State University East Lansing campus
    12. present: 'East Lansing campus' gives the location.
    13. present: 'East Lansing campus' given.
    14. present: "East Lansing campus".
    15. present: 'Michigan State University East Lansing campus'
    16. present: 'East Lansing campus'.
    17. present: 'East Lansing campus'
    18. present: 'East Lansing campus'.
    19. present: 'East Lansing campus'.
    20. present: Specifies "East Lansing campus".
    21. present: 'Michigan State University East Lansing campus' names location.
    22. present: 'East Lansing campus'.
    23. present: 'East Lansing campus' given.
    24. present: East Lansing campus
    25. present: 'East Lansing campus' specified.
  • Guidancepresent25/25

    Final assessment

    Unanimous: "RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT" is explicit, detailed 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: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'
    2. present: Run/avoid, hide/barricade, fight/confront instructed.
    3. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'
    4. present: Instructs 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    5. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'
    6. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    7. present: Instructs 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    8. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT' gives clear guidance.
    9. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'
    10. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    11. present: RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT
    12. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT' instructs recipients.
    13. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    14. present: "RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT".
    15. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'
    16. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    17. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'
    18. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    19. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    20. present: Instructs "RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT".
    21. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT' is explicit guidance.
    22. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    23. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT'.
    24. present: Avoid area, RUN/HIDE/FIGHT
    25. present: 'RUN/AVOID, HIDE/BARRICADE, or FIGHT/CONFRONT!'
  • Timeabsent0/25

    Final assessment

    Unanimous: no clock time, date, or recency marker is given beyond the drill label.

    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 explicit recency term given.
    3. absent: No clock time or recency marker given
    4. absent: No clock time or date given.
    5. absent: No clock time or recency marker
    6. absent: No clock time, date, or recency word given.
    7. absent: No clock time or recency marker beyond it being a drill.
    8. absent: No specific time or recency marker beyond present tense.
    9. absent: No clock time or explicit recency marker beyond present tense
    10. absent: No clock time or recency marker given.
    11. absent: No specific time given, only DRILL label
    12. absent: No clock time or specific recency marker given.
    13. absent: No clock time or date given.
    14. absent: No clock time, date, or recency term given.
    15. absent: No clock time or recency word given
    16. absent: No clock time or date given.
    17. absent: No clock time or date given
    18. absent: No clock time, date, or recency word beyond it being a drill.
    19. absent: No specific clock time or date given.
    20. absent: No clock time or date given.
    21. absent: No clock time, date, or recency term given.
    22. absent: No clock time, date, or recency term given.
    23. absent: No clock time, date, or recency term given.
    24. absent: No clock time or date given, marked as drill
    25. absent: No clock time or specific recency marker beyond 'incident'.
  • Impactabsent0/25

    Final assessment

    Unanimous: no stated consequence or severity beyond naming the incident, which is also marked as a drill.

    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 stated consequence beyond naming the incident
    2. absent: No stated consequence beyond hazard name.
    3. absent: No stated harm or severity
    4. absent: No stated consequence beyond naming the incident.
    5. absent: No stated harm or severity beyond naming the hazard
    6. absent: No stated consequence or severity described.
    7. absent: No stated consequence or severity given.
    8. absent: No stated consequence beyond naming the incident, marked as a drill.
    9. absent: No stated harm or severity beyond hazard name, also a drill
    10. absent: No explicit statement of potential harm.
    11. absent: No stated consequence beyond naming the incident
    12. absent: No stated consequence beyond the hazard name.
    13. absent: No stated consequence or severity described.
    14. absent: No stated harm or severity conveyed.
    15. absent: No stated consequence beyond hazard name, tagged [DRILL]
    16. absent: No stated consequence beyond naming the hazard.
    17. absent: No stated consequence beyond the hazard name
    18. absent: No stated harm or severity described.
    19. absent: No stated consequence or severity.
    20. absent: No stated consequence beyond hazard label, and it's marked a DRILL.
    21. absent: No stated consequence or severity described.
    22. absent: No stated harm or severity, it's a drill.
    23. absent: No stated consequence beyond hazard name; also marked [DRILL].
    24. absent: No stated consequence beyond hazard name
    25. absent: No stated harm or severity conveyed.

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

About this analysis
Context

Background

Every month, MSU's Security Operations Center runs a scenario-based training exercise designed to test the university's emergency notification system without alerting the public. On the morning of Tuesday, February 10, 2026, an SOC employee running that exercise clicked the wrong button, sending a live, campus-wide 'ACTIVE VIOLENCE INCIDENT' alert instead of a contained test message. According to MSU Police Chief Mike Yankowski, the employee believed they were operating inside a designated test environment throughout the exercise. The false alert landed just three days before the anniversary of the February 13, 2023 shooting that killed three MSU students, amplifying fear among a campus community for whom the language of an active-violence alert carried lived, recent trauma. MSU President Kevin Guskiewicz and Chief Yankowski apologized publicly that afternoon and outlined planned fixes: stronger technical separation between test and live systems, additional confirmation steps before any campus-wide alert goes out, and a full review of system permissions and vendor workflows.
Analysis

Key Findings

A monthly test exercise, meant to run in a sandboxed environment, instead transmitted through MSU's live campus-wide alert system because an employee misjudged which environment they were operating in
The correction went out two minutes after the false alert, one of the fastest self-corrections documented among accidental-alert cases in this archive
The false alert's timing, three days before the anniversary of MSU's own 2023 shooting, illustrates how test-system failures can compound trauma at institutions with a documented history of real violence
MSU's response, adding confirmation steps and separating test from live environments, mirrors fixes other universities have adopted after similar accidental broadcasts
Outcome
MSU President Kevin Guskiewicz and Chief Yankowski publicly apologized, and the department began strengthening safeguards between its test and live alert environments, adding confirmation steps, and reviewing system permissions.
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
    Statement on emergency alert system message sent in error - MSUToday
    msutoday.msu.edu
    archived copy
  2. Student Paper
    MSU Police Chief: Employee clicking wrong button to blame for false alert incident - The State News
    statenews.com
    archived copy
  3. Student Paper
    False MSU active violence alert sent out to campus and parents - The State News
    statenews.com
    archived copy
  4. News
    Michigan State mistakenly sends out 'active violence' alert on Tuesday - ClickOnDetroit
    clickondetroit.com
    archived copy
  5. Official
    MSU Alert archive — false drill active violence message
    alert.msu.edu
    archived copy
  6. Official
    MSU Alert archive — error correction
    alert.msu.edu
    archived copy
Cite this case

Campus Alert Archive. "Michigan State University: Live 'ACTIVE VIOLENCE INCIDENT' alert sent during a system test; corrected in two minutes." Incident of February 10, 2026. Added July 2026. https://campusalertarchive.com/case/michigan-state-university-false-active-violence-alert-2026-02-10/

Download case JSON

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

Tags
system-testaccidental-alerthuman-errormichiganclery-testrun-hide-fight2026Unfounded
Added July 2026Updated July 2026Via ingestion