UConn Response to Email Breach of July 5, 2023

ITS and UConn Police are investigating every aspect of the incident, including the identity of who may have been responsible

The official University of Connecticut seal, in painted gold on an oak panel.

(Peter Morenus/UConn Photo)

UConn Information Technology Services (ITS) and UConn Police are investigating an incident that occurred early on the morning of Wednesday, July 5, in which its email system was breached and a fictitious message was sent to a listserv.

One or more unauthorized users gained access to the system and sent two emails, including one that created alarm and concern by falsely reporting that President Maric had died.

ITS quickly removed the messages from inboxes, determined the avenue used to gain access, and took corrective action to prevent it from occurring again. ITS and UConn Police are investigating every aspect of the incident, including the identity of who may have been responsible and any potential affiliations.

"We recognize and share the distress that this message created for President Maric, her family, and the University community," says Michael Mundrane, UConn's vice president for information technology and chief information officer.

"Cybersecurity breaches are a very real threat worldwide, and they are continuously evolving as institutions adopt new safeguards and would-be hackers attempt to circumvent those measures," he adds. "However, in this case, we made a mistake that was then exploited. It spotlights the challenges and risks that can exist as we strive to provide reliable, secure technological systems."

No personal or financial information about students, employees, alumni, or other supporters of the University was exposed, nor did the unauthorized user(s) gain access to institutional fiscal data.

/Public Release. This material from the originating organization/author(s) might be of the point-in-time nature, and edited for clarity, style and length. Mirage.News does not take institutional positions or sides, and all views, positions, and conclusions expressed herein are solely those of the author(s).View in full here.