Skip to content

Western New Mexico University cyberattack

Summary

Western New Mexico University logo

Unauthorized access to WNMU systems April 9–13, 2025, led to extensive service disruption detected April 13. Recovery remained incomplete in June. The university later confirmed file theft and a 24-hour payroll delay. Qilin-signed ransom messages identify a claimed actor; attribution remains unverified.

Key facts

Timeline

  • Incident start:
    ? Earliest known or assessed start of malicious activity or incident activity.
  • First public signal:
    ? Earliest public indication of an outage, disruption, closure or other observable incident impact. The signal does not need to mention cybersecurity.
  • First public cyber evidence:
    ? Earliest credible public information connecting the incident or disruption to malicious cyber activity.
  • Official cyber disclosure:
    ? First official acknowledgment by the affected organization or an authoritative public body that the incident was cyber-related.
  • Last impact seen:
    ? Latest public indication that disruption, degraded operations, recovery work or unresolved impact was still ongoing.

Primary victim organization

Organization types

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

    Malware that encrypts systems or data, typically accompanied by a ransom demand.

  • Data extortion

    Threats to publish or sell stolen data without evidence of encryption.

  • Unauthorized access

    Unauthorized access to systems, accounts, networks, or data.

Data impacts

  • Unauthorized data access

    An unauthorized party accessed or viewed data without evidence that the data was copied, removed, altered, or publicly disclosed.

  • Data theft or exfiltration

    Data was copied, transferred, downloaded, or otherwise removed from the affected environment by an unauthorized party.

  • Data unavailable

    Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.

Operational impacts

  • Partial service outage

    A service, system, platform, or operational capability remained available only in part or with significant limitations.

  • Network outage

    Internal or external network connectivity was unavailable or materially impaired.

  • Internet access disruption

    The organization lost or materially restricted internet connectivity.

  • Email disruption

    Email sending, receiving, access, or related messaging functions were unavailable or materially impaired.

  • Phone service disruption

    Telephone, voice-over-IP, call-center, or related voice communication services were unavailable or materially impaired.

  • Website unavailable

    A public-facing website was unavailable, disabled, or inaccessible.

  • Online portal unavailable

    A public, customer, employee, student, patient, vendor, or partner portal was unavailable or materially impaired.

  • Internal systems unavailable

    Internal business, administrative, operational, or staff-facing systems were unavailable.

  • Application unavailable

    A specific application or software platform became unavailable or unusable.

  • Remote access disruption

    VPN, remote desktop, telework, remote administration, or other remote-access capabilities were unavailable or restricted.

  • Payment processing disruption

    The organization could not process, receive, issue, reconcile, or record payments normally.

  • Records access disruption

    Staff, customers, patients, students, residents, or other users could not access records or case information normally.

  • Educational operations disrupted

    Instruction, student services, school administration, learning platforms, transportation, or other educational operations were materially affected.

  • Service delay

    Services continued but with longer processing, response, delivery, or completion times.

  • Manual workaround required

    Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.

  • Alternate service channel required

    The organization redirected users to a different website, office, telephone number, email address, provider, or service channel.

  • Staff unable to work normally

    Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.

  • Downstream organization impact

    The incident caused operational effects at customers, affiliates, subsidiaries, partners, tenants, or other dependent organizations.

Extortion indicators

  • Ransom demand

    The victim received a demand for payment in exchange for restoring access, decrypting systems, preventing disclosure, or stopping another threatened action.

  • Encryption-based extortion

    The extortion activity involved unauthorized encryption of systems or data, with restoration or decryption conditioned on payment.

  • Data-theft extortion

    The actor threatened to disclose, sell, distribute, or otherwise misuse stolen data unless the victim paid or complied with demands.

  • Public leak threat

    The actor explicitly threatened to publish or publicly release victim data or incident details.

  • Direct victim contact

    The actor directly contacted the victim through a ransom note, email, chat portal, telephone call, messaging platform, or other communication channel.

  • Negotiation portal or ransom chat

    A dedicated portal, chat system, or communication channel was used for ransom negotiation or victim instructions.

Incident narrative

Analyst assessment

Western New Mexico University detected unusual activity April 13, 2025, and isolated systems, interrupting academic and administrative services. Its later breach notice established unauthorized access from April 9–13 and acquisition of certain files. The incident is confirmed with high confidence; April 13 is the detection and disruption date, rather than the beginning of the known intrusion window.

Operational significance

The university’s recovery FAQ describes unavailable web services, restrictions on desktops and remote access, and alternatives for registration, payments and records requests. April 24 local reporting documented phone and academic-access problems despite some third-party learning services remaining available. Hotspots and alternate login routes helped keep classes operating.

The same report quoted Aldo Leopold Charter School’s director describing lost connectivity on the university campus, phone workarounds, relocated testing and students using the public library. The charter school was a downstream affected organization; Silver Consolidated Schools and WNM Communications provided assistance and are not identified as additional victims.

WNMU restored registration access May 1. A May 29 post announced that Mustang Express and email would return the following day, with password resets and multifactor authentication. That was a planned milestone, not a universal restoration confirmation. At the June 25 regents meeting, the chief information officer still reported desktops being rebuilt and voicemail not yet available.

The university later confirmed that the April incident delayed one payroll by 24 hours. It committed to cover resulting fees and distinguished the processing delay from a lack of funds.

Confidence and uncertainty

Searchlight New Mexico reproduced a Qilin-signed ransom message demanding negotiations and threatening data publication. The message referred to decryption software and claimed personal, financial and network information. Ransomware involvement is assessed with medium confidence, while attribution to Qilin remains low confidence. A self-identifying message is not independent verification of the operator.

The official breach investigation subsequently confirmed that copied files contained names with Social Security numbers, driver’s license or other identification numbers, and/or financial account numbers. The university identified those contents Sept. 23, 2025; that review date does not extend the intrusion into September. The notice does not validate every category in the ransom message or establish public release of the data.

Analytic gaps

University leaders reported an enrollment-related annual revenue decline of about $3.3 million in September, largely attributing it to the spring incident. A January 2026 report estimated about $3 million over two semesters. These are separate leadership estimates with different periods, not amounts to add or audited incident-response costs.

No verified universal restoration date, entry route, ransom amount or payment outcome is established. The historical status is presumed resolved, with the end date unset and June 25 retained as the latest unambiguous technical-impact observation. Later enrollment consequences do not establish a continuing technical outage. The undated recovery FAQ does not establish one either.

Threat actor and claim

Listed as: Western New Mexico UniversitySource: other

Claim details

Searchlight New Mexico’s April 25, 2025, report reproduces a Qilin-signed ransom note on a university laptop. The note claims files and personal/financial information were stolen, threatens leak-site publication and offers a decryption tool and negotiation contact. This records the incident-specific claimant, not an independently verified Qilin intrusion or original public leak listing. Original claim publication/discovery times and original leak post URL are unknown. The later university breach notice independently confirms unauthorized access April 9–13 and copied files, but does not establish Qilin responsibility, all note categories, actual public data release or encryption of every affected system. Actor confidence remains low; no separate downstream-school claim is established.

Organizations involved

Impacted locations

  • Luna County, New Mexico

    University Smith center is a documented hotspot access workaround during the disrupted university network. This county-level physical anchor follows the exact 1360 W. Florida St. Census match and Deming polygon exclusion, without asserting a countywide outage or separate facility record.

  • Silver City, New Mexico

    The main university campus and Aldo Leopold Charter School’s affected 2025 Ritch Hall campus were in Silver City. Census exact university and 410 W. 10th St. addresses fall within Silver City 3573260 / Grant County 35017. The charter school moved in 2026; the event-time site is retained. No claim that every local institution was disrupted.

Sources

Cyberattack snarls WNMU systems

Named university and charter-school sources described unavailable web, phone and academic resources, hotspots and testing workarounds.

WNMU restores summer and fall registration after cyber incident

The university explicitly identified a cyber incident and announced registration availability with advising and request-form assistance.

WNMU announces planned return of Mustang Express and email

The university said Mustang Express and email would return the following day, with password resets and multifactor authentication.

WNMU Regents Meet, Take Steps Toward Appointing an Interim President

At the June25meeting, CIO MichaelAcosta said desktops were being rebuilt and voicemail would be available soon.

WNMU Regents Meet, Hear Updates on Presidential Search

The interim president reported about365 fewer students, a roughly10%decline, and approximately$3.3million lower annual revenue, largely attributing the decline to the spring cyber incident.

Board of Regents Discusses Presidential Search and Campus Growth for WNMU

At the January29meeting, the university estimated approximately$3million in losses over two semesters from cyber-related enrollment fluctuations.

Notice of Data Breach

WNMU confirmed unauthorized access April9–13,2025 and acquisition of certain files containing names and sensitive identifiers.

WNMU cybersecurity incident message and recovery FAQ

The university confirmed April13 unusual activity, protective isolation and unavailable web services, with staged workarounds and restoration.

See something that needs correction?

Signed-in members can report an error, update, or missing source.