{"id":683,"date":"2026-04-30T12:27:22","date_gmt":"2026-04-30T17:27:22","guid":{"rendered":"https:\/\/www.wisconsin.edu\/information-security\/?p=683"},"modified":"2026-04-30T13:20:58","modified_gmt":"2026-04-30T18:20:58","slug":"threat-spotlight-phishing-attacks-that-get-past-multi-factor-authentication","status":"publish","type":"post","link":"https:\/\/www.wisconsin.edu\/information-security\/2026\/04\/30\/threat-spotlight-phishing-attacks-that-get-past-multi-factor-authentication\/","title":{"rendered":"Threat Spotlight: Phishing Attacks That Get Past Multi-Factor Authentication"},"content":{"rendered":"\n

A walkthrough of a phishing scam currently hitting colleges and universities, what it looks like, why it’s sneaky, and what to do if one lands in your inbox.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Source: REN-ISAC AiTM Advisory<\/a>. REN-ISAC is the cybersecurity threat-sharing organization for higher education, with about 800 member colleges and universities. When they put out an advisory, it means real campuses are already seeing the attack.<\/p>\n\n\n\n

Threat at a Glance<\/h3>\n\n\n\n
<\/th><\/th><\/tr><\/thead>
Threat type<\/strong><\/td>Adversary-in-the-Middle (AiTM) phishing<\/td><\/tr>
Targets<\/strong><\/td>Faculty, staff, and researchers at colleges and universities<\/td><\/tr>
What it steals<\/strong><\/td>Your password AND your active login session, meaning MFA gets bypassed<\/td><\/tr>
Common disguises<\/strong><\/td>Shared file notices, mailbox-full warnings, HR or payroll messages, DocuSign requests<\/td><\/tr>
Why it’s dangerous<\/strong><\/td>The fake page passes you through to the real one, so everything feels normal<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

How It Works<\/h3>\n\n\n\n

Imagine someone sets up a fake bank lobby that looks exactly like your real bank. You walk in, hand the teller your ID and your PIN, and they pass it through a window to a real teller at the real bank next door. The real bank does its normal verification, including texting you a code, and you read the code out loud. Everything feels normal. You finish your “transaction” and walk out. Meanwhile, the person in the middle now has a copy of your bank’s “you’re logged in” pass and can walk into the real bank as you for the rest of the day.<\/p>\n\n\n\n

That’s what’s happening online. The attacker sends you to a fake login page that secretly forwards everything to the real one. You type your password, they get it. You approve the Duo prompt, they get the access. The page sends you somewhere normal-looking afterward, so nothing seems off. But your account is now wide open to them.<\/p>\n\n\n\n

The Red Flags<\/h3>\n\n\n\n

The web address doesn’t match.<\/strong> The fake page looks perfect, but the URL in your browser’s address bar won’t quite match the real one. Universities of Wisconsin and Microsoft logins end in addresses like wisconsin.edu or microsoftonline.com. Fakes use lookalikes such as wisconsin-login.com, login-microsoftonline.net, or office365-secure.com.<\/p>\n\n\n\n

You arrived by clicking an email link.<\/strong> AiTM attacks almost always start with an unexpected email containing a link to “review a file,” “verify your account,” or “listen to a voicemail.”<\/p>\n\n\n\n

An MFA prompt you didn’t trigger.<\/strong> If your phone buzzes with an MFA approval request and you weren’t actively logging in, that prompt is someone else trying to log in as you.<\/p>\n\n\n\n

Other Warning Signs<\/h3>\n\n\n\n

Unexpected file shares.<\/strong> Always verify with the sender through a separate channel like a phone call or in-person before clicking.<\/p>\n\n\n\n

Urgency.<\/strong> Phrases like “action required” or “your account will be locked” are designed to make you click before thinking.<\/p>\n\n\n\n

Generic greetings or slightly-off branding.<\/strong> Look for “Dear User” instead of your name, or logos that look a little stretched or pixelated.<\/p>\n\n\n\n

Lookalike sender addresses.<\/strong> The display name might say “Microsoft 365” but the actual email address ends in something unrelated.<\/p>\n\n\n\n

What to Do if You Get a Real One<\/h3>\n\n\n\n

Check the address bar before typing anything.<\/strong> The URL is the giveaway. If it looks even slightly off, close the tab.<\/p>\n\n\n\n

Don’t log in from email links.<\/strong> Open a new tab and go to the site yourself, or use a saved bookmark.<\/p>\n\n\n\n

Deny unexpected MFA prompts.<\/strong> Don’t approve a push just to make it stop.<\/p>\n\n\n\n

Pay attention to number-matching codes.<\/strong> Actually look at the number, don’t tap on autopilot.<\/p>\n\n\n\n

Report it.<\/strong> Use the Report Phishing button in Outlook or forward the email to the help desk.<\/p>\n\n\n\n

If you entered your password or approved a prompt, change your password immediately and contact the help desk right away. They can kick the attacker out of your active session, but only if they know quickly.<\/p>\n\n\n\n

You can find contact information for your campus help desk here: Universities of Wisconsin (UW System) – IT Help Desks Contact Information<\/a>.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

A walkthrough of a phishing scam currently hitting colleges and universities, what it looks like, why it’s sneaky, and what to do if one lands in your inbox. Source: REN-ISAC […]<\/p>\n","protected":false},"author":6587,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[34,33,23,21,39,28,38],"tags":[],"class_list":["post-683","post","type-post","status-publish","format-standard","hentry","category-account-security","category-faculty-staff-awareness","category-mfa","category-phishing","category-ren-isac","category-student-safety","category-threat-spotlight"],"publishpress_future_action":{"enabled":false,"date":"2026-06-23 00:31:37","action":"change-status","newStatus":"draft","terms":[],"taxonomy":"category","extraData":[]},"publishpress_future_workflow_manual_trigger":{"enabledWorkflows":[]},"_links":{"self":[{"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/posts\/683","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/users\/6587"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/comments?post=683"}],"version-history":[{"count":5,"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/posts\/683\/revisions"}],"predecessor-version":[{"id":698,"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/posts\/683\/revisions\/698"}],"wp:attachment":[{"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/media?parent=683"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/categories?post=683"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wisconsin.edu\/information-security\/wp-json\/wp\/v2\/tags?post=683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}