Key takeaways

  • Osaka Metropolitan University (大阪公立大学), run by Osaka Prefecture and Osaka City, says it was hit by a ransomware attack early on October 2, 2026.
  • Attackers got into the university's virtualization platform, and about 500 servers stopped. Most backups were encrypted too. Email, the student portal and academic systems are down, and there is no recovery date.
  • Data on at least 130,000 people, including students and graduates going back to 1995, was stored on the affected systems. Whether it was taken is under investigation.
  • On October 21, the university said the attackers got in with a legitimate account belonging to a subcontractor of NEC, which maintains and operates its systems. NEC says the subcontractor was hacked in late September, that several NEC customers were hit the same way, and that files in a cloud storage NEC used to share information with customers, including the university's personal data and system information, also leaked.
  • Classes were cancelled until October 8. In-person classes resumed on October 9, using temporary systems the university built for teaching. The university hospital and veterinary center are unaffected.

Update, November 17: In its sixth report, on November 13, the university said that the data leaked from NEC's cloud storage included personal data on about 170,000 students and staff, and admin information for its own systems. For about 1,400 people it included sensitive data such as bank account numbers, health information and passport images and numbers, most of it left over from a 2021 system migration NEC carried out. Its own investigation found that the attacker used admin accounts of NEC and the subcontractor, taken from the subcontractor's computer and NEC's storage, to get in. See What NEC's storage held.

Update, October 21: The cause is now known. NEC, which runs the university's systems, says a subcontractor it uses was hacked in late September, and its legitimate account was used to get into the university's systems. Data in a cloud storage NEC used for the project also leaked. See The way in: an NEC subcontractor.

Update, October 7: The university has published its own account of the October 5 press conference, with a detailed timeline and a list of affected systems, including finance, HR and payroll, and the admissions database. See The university's timeline.

Update, October 9: In-person classes resumed on October 9. The university has built temporary learning, student portal and help desk systems to make this possible, but its main systems are still down. See Classes resume on temporary systems.

What happened#

Date (2026) Event
Oct 2, early morning Large-scale failure of the university's information systems across all campuses. The university learns of it from its IT vendor
Oct 2, 14:00 First report: cause unknown, no recovery date. Classes cancelled for the day
Oct 2, 18:00 Second report: classes cancelled until Oct 8. In-person classes to resume from Oct 9
Oct 5 Press conference: the university says the cause is a ransomware attack
Oct 6 The university publishes an account of the press conference and the handout
Oct 8 Fourth report: in-person classes to resume as planned, using temporary systems
Oct 9 In-person classes resume at all campuses

According to reports of the press conference, the attackers got into the virtualization platform that runs many of the university's systems, and about 500 servers stopped. Most of the backups were also encrypted and cannot be used. The university has no date for recovery.

President Hiroyuki Sakuragi apologized. The university says it has reported the attack to the Ministry of Education, its founding bodies Osaka Prefecture and Osaka City, the police, JPCERT/CC and the Personal Information Protection Commission. It has not said whether a ransom has been demanded or who is behind the attack.

The university's timeline#

The handout from the October 5 press conference gives this account of October 2:

Time (Oct 2) Event
About 00:20 The maintenance vendor sees the information system's servers stopping one after another and starts investigating
About 01:40 The vendor alerts the university's IT department
About 02:00–03:00 Remote response is not possible. University IT staff go on site and find the systems unreachable from the campus network
From about 04:00 The vendor's engineers find the virtual servers stopped and "traces of some data having been altered"
About 07:00 Class cancellation posted for students
About 08:00 Reported to Osaka Prefecture and Osaka City. Crisis headquarters set up at 08:15
About 11:00 Reported to the Ministry of Education, information security bodies and the police
12:00 and 18:30 First and second public reports

A temporary notice site opened at about 07:30 on October 3. The university contacted the Personal Information Protection Commission at about 10:00 on October 5. The handout does not explain what the "altered" data was, or whether this refers to the encryption itself.

What is down#

The university's handout lists the main affected systems as:

  • Campus network and OMU email
  • The organization's websites, including www.omu.ac.jp, and the staff portal
  • Office PCs, which staff cannot log in to
  • Financial accounting, HR and payroll, academic affairs and education support systems
  • The admissions information database
  • The library system

The list is described as a partial excerpt. The university is posting updates on its entrance page and a temporary notice site.

Not affected:

  • The university hospital and the veterinary clinical center, which are operating normally
  • Online application and enrollment sites for prospective students, which run on external servers. The application deadline has been extended to October 22

Classes resume on temporary systems#

Added October 9, 2026.

In its fourth report, on October 8, the university said the investigation and recovery are still under way, but that in-person classes would resume at all campuses on October 9, as first announced. To make that possible, it has built temporary versions of the systems teaching depends on:

Temporary system What it does
Temporary Moodle (learning management system) Course materials, timetables and rooms, messages from teachers, assignment submission and questions
Temporary student portal Notices on student life and class registration
Academic affairs system Course search and grades
Temporary course catalog Syllabuses and textbook information
Temporary digital help desk Questions and consultations from students to staff
QR code attendance Attendance registration through the university app

Separate notices on October 8 say OMU email has resumed for students, and for staff for use within the university only. The university has still given no date for restoring its main systems.

The way in: an NEC subcontractor#

Added October 21, 2026.

In its fifth report, on October 21, the university said it had been told the cause the day before by NEC, the company it contracts to maintain and operate its core systems:

  • A company that NEC uses for system development and maintenance, a subcontractor from the university's point of view, was hit by a cyberattack in late September.
  • The attackers then got into the university's systems using that subcontractor's legitimate account.
  • Separately, files in a cloud storage service that NEC used were leaked, and they included personal data and system information related to the university. What and how much is still being confirmed with NEC.

NEC published its own notice on October 20. It says the stolen credentials were used to access customers' systems from the contractor's terminals, that server files were encrypted and systems stopped working, and that the leaked cloud storage was one NEC set up to share information between customers, NEC and its contractors. Several NEC customers were affected; NEC has contacted them but has not named them. It now lends NEC-managed computers to the contractor, and says it will tighten its management of contractors and personal data. We cover NEC's disclosure in a separate article.

The university stresses that the roughly 130,000 records it mentioned on October 5 were on its own virtualization platform, not in NEC's cloud storage, and that whether those were taken is still under investigation.

What NEC's storage held#

Added November 17, 2026.

The university's sixth report, published on November 13, gives the results of its investigation so far.

How the attacker got in. The university found traces of large amounts of data, including university information, leaking from the subcontractor's computer and from the cloud storage NEC manages. Right after the times those leaks were recorded, someone logged in to the university's systems with legitimate accounts and passwords used by NEC and the subcontractor for the contract, including system administrator accounts. The outside investigator found several traces showing that the same attacker was behind both. The university concludes that the attacker used account details stolen through the subcontractor's computer and from NEC's storage to get in.

What leaked from NEC's storage. NEC reported to the university on November 12 that the leaked data included important management information, including admin information for the university's systems, and personal data on about 170,000 students and staff: IDs, names, email addresses and birth dates. About 1,400 people's records were more sensitive:

Data People Whose
Bank account numbers about 20 Not stated
Health-related information about 200 Staff and students enrolled from 2018 to 2021
Passport images about 200 International students who came from 2018 to 2021
Passport numbers about 1,000 Students enrolled from 2018 to 2021 registered for overseas travel (JCSOS)

Most of the sensitive data was migration data from a system migration NEC carried out for the university in fiscal 2021, which stayed on NEC's cloud storage after the work was finished. The university says NEC's keeping the data for years without deleting it, in a storage used by many people at NEC and its subcontractor, was a serious problem. NEC is still working out exactly who is affected, and the university will contact each person once they are identified.

In our view, the lesson for any organization that hires a vendor for a system migration is to require that migration copies are deleted when the work ends, and to get that confirmed in writing. The most sensitive data in this case was not in the live systems but in a copy nobody needed any more.

The university's own systems. It has found no clear evidence that personal data was taken from its own systems, but because the attacker got in and encrypted many systems, it cannot rule it out, and it will explain the case to the people concerned as a possible leak. The report says nothing new about when the main systems will be restored.

What may have been exposed#

According to reports of the press conference, personal data on at least 130,000 people was stored on the affected systems. That figure does not appear in the university's own documents. According to the press reports, the data includes:

Data Source of report
Names, addresses, email addresses Nikkei, Jiji
Mobile phone numbers MBS
Student ID photos Nikkei

The people covered include current students, graduates, and faculty and staff. The data goes back to students of Osaka City University from 1995 and Osaka Prefecture University from 2005, the two universities that merged to form Osaka Metropolitan University in 2022. With an undergraduate intake of about 2,850, the merged university was the third-largest national or public university in Japan, after Osaka University and the University of Tokyo, when it opened, according to Nikkei.

Whether any of it was taken is still under investigation.

Update, October 21: A second set of data has now leaked: files in the cloud storage NEC used to share project information, which included personal data and system information related to the university. Neither the university nor NEC has said what personal data, or how much.

What we don't know yet#

The university has not said:

  • How the subcontractor was hacked, which company it is, and why its account could reach the university's systems directly
  • Exactly who is in the data on NEC's cloud storage. The university gave the counts on November 13, but NEC is still identifying the people
  • Which other NEC customers were hit
  • Whether data was stolen from the university's own systems as well as encrypted, and whether a ransom has been demanded
  • Which ransomware group is responsible. As of October 9, we found no listing on ransomware leak site trackers
  • When the main systems will be restored, and how long the temporary systems will be used
  • Whether it will notify each of the 130,000 people individually

The university's own documents now confirm the ransomware attack, the timeline and the affected systems. The figure of 130,000 people, the types of data and the encryption of most backups come from press reports of the October 5 press conference and do not appear in those documents.

Our analysis#

One platform, 500 servers, and the backups#

The most important detail is where the attackers landed: the virtualization platform. When many systems run as virtual machines on shared infrastructure, control of that layer is control of all of them, and of any backups stored or managed within reach. That is how one intrusion becomes 500 stopped servers and backups that cannot be used.

This is a common pattern in ransomware attacks: many major ransomware groups have encryptors built specifically for hypervisors, so that a single foothold in the virtualization layer can stop hundreds of servers at once.

It is the pattern the police figures keep showing. In the NPA's ransomware statistics, most victims had backups, but most of those who tried could not restore from them, usually because the attackers had encrypted or deleted the backups too. Backups only help if the attacker cannot reach them: offline, immutable, or managed with separate credentials. The university has not said how its backups were set up.

Thirty years of data#

Data on students going back to 1995 was on the affected systems. That is not unusual for a university: alumni records, certificates and contact lists build up over decades. But it means the people at risk include graduates who left the university, or its predecessors, long ago and may not expect to be affected.

We have seen the same issue in other breaches this month: Dai-ichi Life held records on former office staff going back to 1967, and Times Car held data on former members and on people who never completed sign-up. Data that is no longer needed day to day still has to be protected, or deleted.

Found by the vendor#

According to the university's timeline, its maintenance vendor saw servers stopping at about 00:20 and alerted the university about 80 minutes later, and the investigation is being carried out with the outsourced operator of its systems. Many Japanese organizations, universities included, rely on outside companies to run their infrastructure. That means that how quickly an attack is spotted, and how the systems were configured, may depend as much on the operator as on the university.

Update, October 21: It turns out the operator's supply chain was also the way in. The attackers used a legitimate account of a company NEC subcontracts, working from that company's computers. In our view, this is the risk that remote maintenance access carries for every organization that outsources its infrastructure: the vendor's accounts, and its vendors' accounts, are as much a part of the attack surface as the organization's own VPN. Questions worth asking any operator are which of its subcontractors can reach your systems, from which devices, with what authentication, and whether that access is limited to when it is needed.

Keeping students informed#

With its main website down, the university has kept communicating through a separate entrance page and a temporary notice site, both apparently hosted outside the affected systems. That is the right approach. One caution: the temporary site uses a domain outside omu.ac.jp. Students and others should reach it through the university's entrance page, e.omu.ac.jp, rather than through links in emails or messages, since scammers often imitate emergency notices.

What this means for readers#

  • If you studied or worked at Osaka Metropolitan University, Osaka City University (since 1995) or Osaka Prefecture University (since 2005), your name, address, email, phone number and possibly your student ID photo may have been on the affected systems.
  • Be suspicious of messages about the incident, especially ones asking you to log in, pay, or "check" whether you are affected. Get updates from e.omu.ac.jp.
  • For organizations running virtualized infrastructure, treat the virtualization management layer as one of your most critical systems, and keep at least one copy of backups that it cannot reach.

Japanese terms at a glance#

Japanese Reading Meaning
大阪公立大学 Ōsaka Kōritsu Daigaku Osaka Metropolitan University
情報基盤システム jōhō kiban shisutemu Information infrastructure systems
仮想化基盤 kasōka kiban Virtualization platform
休講 kyūkō Class cancellation
運用委託事業者 un'yō itaku jigyōsha Outsourced IT operator
臨時お知らせサイト rinji oshirase saito Temporary notice site

We will update this article when the university publishes the results of its investigation or a recovery date.