The University of Copenhagen says attackers accessed a test environment containing information on approximately 525,000 people. Its incident notices describe personal-data exposure, replacement of campus-card PINs and precautionary shutdowns of administrative systems.

Evidence status: university-confirmed unauthorized access and compromised PINs. The reviewed notices provide no technical entry point, attacker attribution or independently verified account of subsequent misuse.

Update — October 27, 2026 at 21:49 EDT

The university’s October 27, 21:30 local update adds a recovery plan and a more explicit scope assessment. It says the closed administrative systems “have not been compromised” and were shut down as a precaution. The confirmed test-environment breach and PIN exposure remain separate from that assessment.

External access remains blocked for several systems. The university plans a controlled reopening over the coming days, following an individual security assessment for each system. It expects staff access to most systems through its VPN, an authenticated campus-network connection, on Wednesday, October 28. That is a plan, not a completed restoration.

For current access, the notice directs users to campus connections or the staff-only VPN. It gives building-specific exceptions for the Eduroam campus network. Follow those official instructions rather than treating an inaccessible service as evidence of another attack.

The university also says it has sent breach letters through Digital Post. Some affected people could not be contacted because its records contained only their names. The notice therefore links a public copy of the letter. Check the official page directly rather than trusting an unsolicited copy.

The original publication date and earlier correction are retained below. This update adds access guidance and the university’s latest assessment; it supplies no new attacker attribution or confirmed misuse.

A test environment still held real personal information

The university’s original October 23 notice says it detected the attack on Tuesday and blocked access. The affected database contained full names, national identity numbers, work and home telephone numbers, and personal email addresses.

On October 25 at 20:00, the university disclosed that approximately 20,000 staff and students’ ID-card PINs had been compromised and replaced. It says it delayed that disclosure until new PINs were issued.

The PIN exposure belongs to the same incident. Do not add 20,000 to 525,000 as a new total of distinct victims. The notices do not establish that those populations are separate.

The university had restricted physical access to selected critical locations on October 23. Its October 25 update says those locations reopened after the affected PINs were replaced. The notice does not report unauthorized physical entry.

Correction regarding a new attack

On October 26 at 17:50, the university reported preventive shutdowns affecting administrative systems, including Workzone and Nimbus. That notice initially attributed them to a new attack.

Its October 27, 11:00 correction retracts that assessment:

However, later in the evening it was determined that this was not a new attack, but rather activity within the system that initially appeared to indicate a new attack.

The correction says the controlled shutdown remains necessary in connection with the original attack, and some systems still face disruptions.

The original October 23 statement reported no indication of access to day-to-day operational systems or operational impact. That was the assessment then. The later precautionary shutdowns are a real service impact, without establishing that attackers breached those administrative systems.

Bill Toulas’s October 26 BleepingComputer report covers the personal-data and PIN exposure. The university’s newer correction supplies the current assessment of the supposed second attack.

Treat test data and physical-access secrets as separate recovery tasks

For affected staff and students, follow the university’s current card and service notices through known university channels. The university says affected PINs have already been replaced. Its reviewed notices contain no blanket password-reset order.

Accurate personal details can make an impostor credible. Verify unexpected requests through an independently opened university site or known contact, particularly requests for credentials or additional identity information.

For teams operating test systems, this incident raises a concrete review question: does a lower-trust environment contain production identities or access secrets?

  • Inventory copied data. Include national identifiers, private contact details and credentials for physical systems.
  • Minimize test datasets. Use synthetic or appropriately de-identified records where practical, with defined retention and deletion rules.
  • Review access independently of the production perimeter. A test label does not reduce the sensitivity of the records it contains.
  • Separate containment from credential replacement. Blocking network access cannot invalidate a stolen card PIN; the relevant access system must replace it.

Those are defensive implications of the disclosed exposure. The university has not published enough technical detail to identify a specific control failure or affected software version.

Caveat: The university is still establishing the breach’s full extent. Its public notices confirm access and PIN exposure but do not establish a complete stolen-record inventory or subsequent identity fraud.