Skip to content
Campus Alert Archive
MSU

A Wrong Button, Two Minutes, and a Terrifying Echo of February 13

AI-generated · every claim is source-linked
MIpolice activitytesthigh confidence
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
~50,000 studentsMSU Alert
Official alert policy
Read when and how MSU says it will use MSU Alert — summarized, quoted, and analyzed.
Confirmed Timeline

Alert Sequence

2 messages in sequence · 2 verified verbatim

INITIAL ALERTSMS
MSU: EMERGENCY! ACTIVE VIOLENCE INCIDENT at the Michigan State University East Lansing campus. Avoid the area. Monitor alert.msu.edu for info.
This message was generated during a monthly scenario-based training exercise but was transmitted through MSU's live, campus-wide alert channel rather than a sandboxed test environment
The 'ACTIVE VIOLENCE INCIDENT' language and 'avoid the area' directive are indistinguishable from MSU's real emergency-notification template, which is precisely why the false alert caused genuine panic
Sent three days before the third anniversary of the February 13, 2023 MSU shooting, a timing coincidence that intensified the emotional impact on students, staff, and parents who received it
Some recipients reported receiving a version of the message that additionally referenced 'run/avoid, hide/barricade, or fight/confront,' echoing the run-hide-fight guidance MSU adopted after the 2023 shooting
CORRECTIONSMS+2 min
The recent MSU Alert was sent in error. Please disregard the message. We regret any undue stress caused. Visit alert.msu.edu to learn more.
Sent just two minutes after the false alert, an unusually fast correction that MSU credited to staff 'quickly' realizing the mistake
Uses the passive 'was sent in error' rather than explaining the test-environment mix-up, with the fuller human-error explanation reserved for the university's later public statement and police chief interview
The brief apology, 'we regret any undue stress caused,' understates what students described as genuine panic, given the proximity to the 2023 shooting anniversary
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.

MSU: EMERGENCY! ACTIVE VIOLENCE INCIDENT at the Michigan State University East Lansing campus. Avoid the area. Monitor alert.msu.edu for info.

  • Sourceabsent0/0

    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

    Open to load the 25 reads.

  • Hazardabsent0/0

    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

    Open to load the 25 reads.

  • Locationabsent0/0

    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

    Open to load the 25 reads.

  • Guidanceabsent0/0

    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

    Open to load the 25 reads.

  • Timeabsent0/0

    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

    Open to load the 25 reads.

  • Impactabsent0/0

    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

    Open to load the 25 reads.

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

  1. Official
  2. Student Paper
  3. Student Paper
  4. News
Cite this case

Campus Alert Archive. "Michigan State University: A Wrong Button, Two Minutes, and a Terrifying Echo of February 13." 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