{"id":26581,"date":"2026-11-10T14:00:05","date_gmt":"2026-11-10T14:00:05","guid":{"rendered":"https:\/\/www.securitytoday.de\/?p=26581"},"modified":"2026-11-16T16:40:10","modified_gmt":"2026-11-16T16:40:10","slug":"legacy-portal-attack-tum-pulled-tumonline-offline","status":"publish","type":"post","link":"https:\/\/www.securitytoday.de\/en\/2026\/11\/10\/legacy-portal-attack-tum-pulled-tumonline-offline\/","title":{"rendered":"Attack via legacy system: TUM took TUMonline offline"},"content":{"rendered":"<p><strong>At the Technical University of Munich, attackers used the legacy portal myTUM to steal the central login passwords of everyone registered there, including a system administrator&#8217;s password for TUMonline. They used that access to attack TUMonline. The university took the system offline. It has been running again since 9 November.<\/strong><\/p>\n<div style=\"background:#003340;color:#fff;padding:32px 36px;margin:32px 0;border-radius:8px;\">\n<p style=\"color:#69d8ed;text-transform:uppercase;letter-spacing:0.08em;font-size:0.82em;font-weight:700;margin:0 0 16px;\">Key takeaways<\/p>\n<ul style=\"margin:0;padding-left:20px;line-height:1.7;\">\n<li style=\"margin-bottom:10px;\"><strong style=\"color:#69d8ed;\">The legacy system myTUM served as the entry point into TUMonline.<\/strong> Through the old portal, attackers obtained the central login passwords of everyone registered there, including a system&nbsp;administrator&#8217;s login credentials.<\/li>\n<li style=\"margin-bottom:10px;\"><strong style=\"color:#69d8ed;\">TUMonline went offline after the attack and has been running again since 9 November.<\/strong> According to the university, the myTUM portal remains permanently&nbsp;offline.<\/li>\n<li style=\"margin-bottom:0;\"><strong style=\"color:#69d8ed;\">Accounts with MFA (multi-factor authentication) remained protected, according to TUM.<\/strong> The university asks everyone affected to change their password and then enable multi-factor&nbsp;authentication.<\/li>\n<\/ul>\n<\/div>\n<p style=\"border-bottom:1px solid rgba(230,227,218,0.14);padding:14px 0;margin:28px 0;font-size:0.92em;color:#b8c5ce;\"><strong style=\"color:#69d8ed;\">Related:<\/strong> <a href=\"https:\/\/www.securitytoday.de\/en\/2026\/10\/22\/black-october-many-attacks-had-been-running-for-months\/\" target=\"_blank\" rel=\"noopener\">Black October: Many attacks ran for&nbsp;months<\/a><\/p>\n<h2>The path from myTUM to&nbsp;TUMonline<\/h2>\n<p>According to a TUM spokesperson speaking to Bayerischer Rundfunk, the attackers most likely wanted to gain access to TUMonline by attacking the old portal. It was their gateway into the current campus management&nbsp;system.<\/p>\n<p>Through myTUM, the unknown attackers obtained the passwords for the central login to TUM systems, including login.tum.de and TUMonline. Everyone who had registered with myTUM is affected. The stolen passwords included that of a TUMonline system administrator. In this campus management system, the university manages central student records, including grades and applications for university&nbsp;places.<\/p>\n<p>The attackers used the system administrator&#8217;s access to attack TUMonline. The university then took the system offline. According to the university, the myTUM portal remains permanently offline. On the morning of 9 November, TUM re-enabled password changes, and at 17:25 it reported TUMonline back in operation. Before using it, users must change their password and set up two-factor authentication.<\/p>\n<div data-element=\"definition_box\" style=\"background:#23261f;border:1px solid rgba(105,216,237,0.22);border-radius:10px;padding:20px 24px;margin:32px 0;box-shadow:0 2px 10px rgba(0,0,0,0.22);\">\n<p style=\"margin:0;color:#e6e3da;line-height:1.6;\"><strong>What is a legacy system?<\/strong> A legacy system is an application that an operator keeps running even though newer systems have taken over its tasks, or are meant to. For security, what matters is which central services such a system is still connected to. At TUM, users logged in to the myTUM portal with the same central passwords used for login.tum.de and&nbsp;TUMonline.<\/p>\n<\/div>\n<h2>What the logs&nbsp;show<\/h2>\n<p>A TUM spokesperson told Bayerischer Rundfunk that the attack on myTUM was probably intended to gain access to TUMonline. That succeeded. The passwords were not the goal. <a href=\"https:\/\/www.br.de\/nachrichten\/bayern\/erneut-hackerangriff-auf-bayerische-uni-tum-betroffen,VaCjyBT\" target=\"_blank\" rel=\"noopener\">&#8220;We currently believe that virtually no data was exfiltrated, although this would have been&nbsp;possible.&#8221;<\/a><\/p>\n<p>The university has largely logged the attackers&#8217; activity within TUMonline. After evaluating these logs, it assumes that no further data from TUMonline is affected, for example grades or applications for university places. The review is still&nbsp;ongoing.<\/p>\n<h2>The potentially affected data identified by&nbsp;TUM<\/h2>\n<p>As early as 6 November, the university broke down which data may have been affected. Alongside the stolen passwords, names, private addresses and dates of birth may have been accessible for everyone affected. For employees, the business address and work phone number may also have been accessible. For students, the matriculation number, degree programme and number of semesters in their degree programme may also have been&nbsp;accessible.<\/p>\n<p>TUM warns of a secondary risk. With a name, degree programme and address, fraudsters could compose phishing messages that look credible.<\/p>\n<h2>Accounts with MFA stayed&nbsp;protected<\/h2>\n<p>&#8220;User accounts with MFA were protected in this attack,&#8221; writes <a href=\"https:\/\/www.tum.de\/aktuelles\/alle-meldungen\/pressemitteilungen\/details\/it-sicherheitsvorfall-an-der-tum\" target=\"_blank\" rel=\"noopener\">TUM in its statement<\/a>. Multi-factor authentication requires a second form of verification in addition to the password. The university asks everyone affected to change their password and then enable&nbsp;MFA.<\/p>\n<p>The attackers gained entry through a portal that was still in use, stealing a system administrator&#8217;s credentials for the central management system. For security teams, this highlights two areas to check: legacy systems still connected to central authentication and the protection of privileged accounts.<\/p>\n<h2>What TUM leaves&nbsp;open<\/h2>\n<p>TUM has <a href=\"https:\/\/www.theregister.com\/cyber-crime\/2026\/11\/09\/portal-breach-at-germanys-top-university-exposes-every-registered-users-password\/5308380\" target=\"_blank\" rel=\"noopener\">not disclosed<\/a> how the attackers initially got into myTUM. It also remains unclear how the stolen passwords were stored. The question of whether the system administrator had enabled MFA went&nbsp;unanswered.<\/p>\n<p>TUM is not the only university in Munich with a security incident. Since <a href=\"https:\/\/www.lmu.de\/de\/newsroom\/newsuebersicht\/news\/update-zum-datenschutzvorfall-71c6c19a.html\" target=\"_blank\" rel=\"noopener\">16 September<\/a>, Ludwig-Maximilians-Universit\u00e4t (LMU) has been defending against and investigating a cyber attack on one of its IT systems. According to Bayerischer Rundfunk, it affected around 600,000 records of current and former students spanning about 50 years. There, the attackers gained access to the admissions system. Passwords were not affected at&nbsp;LMU.<\/p>\n<p>Further answers at TUM will depend on continued analysis of the TUMonline logs.<\/p>\n<h2 style=\"padding-top:64px;margin-bottom:20px;\">Frequently asked questions<\/h2>\n<p class=\"st-faq-hint\">Answers are initially hidden. Tap a question to reveal its&nbsp;answer.<\/p>\n<details>\n<summary><strong>Can affected users change their password in TUMonline&nbsp;again?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Yes. Password changes have been available again since 9 November, and TUMonline is running again as well. TUM requires changing the password first and then setting up multi-factor authentication.<\/p>\n<\/details>\n<details>\n<summary><strong>How can you spot fake requests in TUM&#8217;s name?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">TUM says it never asks for passwords by email, phone or letter. A message that demands a password therefore does not come from the university, even if it states a name, degree programme or address&nbsp;correctly.<\/p>\n<\/details>\n<details>\n<summary><strong>Which authorities has TUM involved?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">The university has filed a criminal complaint and reported the incident to the Bavarian State Commissioner for Data Protection. Responsibility for the statement lies with Dr.-Ing. Alexander Braun, Executive Vice President for IT Systems and Services and Chief Information Officer of&nbsp;TUM.<\/p>\n<\/details>\n<p><!--ST-LOWER-CARDS lang=en--><!--\/ST-LOWER-CARDS--><\/p>\n<p style=\"font-style:italic;text-align:right;font-size:0.85em;margin-top:8px;\">Image source: AI-generated (November 2026)<\/p>\n","protected":false},"excerpt":{"rendered":"Attackers stole a system administrator&#8217;s password through the legacy portal myTUM. They used it to attack TUMonline, the central campus management system.","protected":false},"author":10,"featured_media":26560,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_focuskw":"Technical University of Munich","_yoast_wpseo_title":"Legacy system attack: TUM took TUMonline offline","_yoast_wpseo_metadesc":"Attackers stole a system administrator's password via the legacy portal myTUM and attacked TUMonline. It has been running again since 9 November.","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_yoast_wpseo_twitter-image-id":0,"evm_kih_original":false,"_evm_slot_owner":"","evm_cvss":0,"evm_risk":0,"evm_casefile":"","evm_primary_cve":"","evm_pin_until":0,"evm_external_preview_token":"","evm_external_preview_expires":"","_evm_translation_lang":"","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[251],"tags":[],"class_list":["post-26581","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"evm_reading_time_minutes":5,"wpml_language":"en","wpml_translation_of":26553,"_links":{"self":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/26581","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/comments?post=26581"}],"version-history":[{"count":17,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/26581\/revisions"}],"predecessor-version":[{"id":27353,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/26581\/revisions\/27353"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media\/26560"}],"wp:attachment":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media?parent=26581"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/categories?post=26581"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/tags?post=26581"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}