Sign in Book demo

The request MFA can’t stop: BYOD, campuses and the help desk

A new extortion group called BYOD has started claiming attacks on university systems, and the way in may be a person who already has access. Attackers are calling help desks and staff to get MFA reset or approved, not trying to break it. This post explains why state, local and education organizations are easy targets and the six steps to take now.

A new extortion group is turning its attention to higher education. BYOD first surfaced in late September 2026 with claims against telecom, IT services and manufacturing companies. Since late October, it has claimed attacks on two university systems and says it holds large volumes of student and employee records.

Most of those claims have not been confirmed, and analysts have not tied BYOD to a consistent way in. In one case, the group says it started with credentials stolen from a third party’s employee. That fits a broader pattern: the easiest way into a well-defended network is often a person who already has access.

We turned the BYOD campaign into a short briefing for students, faculty and staff with Fable’s Briefing Agent. Watch it below, or, if you’re a Fable customer, deploy it from the Catalog.

For campuses and agencies, the practical question is how that access gets handed over. Increasingly, it starts with an unexpected request for a password or an authentication approval, and more and more often that request arrives by phone.

The call

Eighty-nine percent of states have deployed MFA, according to NASCIO’s 2024 survey, so attackers have started asking for it instead of trying to break it. The Center for Internet Security, which supports state and local governments through MS-ISAC, observed vishing incidents against those organizations through the first eight months of 2026, often over Microsoft Teams. CIS describes two versions of the play. A third is newer, and all of them aim at the moment of verification, the one step MFA cannot protect on its own:

  1. The caller is “an employee.” The attacker contacts the help desk, claims to be a locked-out staff member, and asks for a password reset or for MFA to be moved to a new device. The new device belongs to the attacker.
  2. The caller is “the help desk.” The attacker contacts an employee, often over Teams, and asks them to read back a one-time passcode or approve an MFA push to “finish a fix.”
  3. The newer twist: passkeys. In July 2026, Okta documented attackers using vishing to talk users into registering an attacker-controlled passkey in Microsoft Entra. That makes enrollment the new weak point.
  4. The payoff. Once the attacker holds a valid session, every downstream control sees a legitimate, authenticated user.

Mandiant’s M-Trends 2026 report found that vishing accounted for 11% of initial access, making it the second most common way in. Email phishing fell to 6%, down from 14% the year before.

Why state, local and education

Public-sector organizations publish a great deal by design. Staff directories, org charts, board minutes and department phone numbers are often a click away. That transparency serves citizens and students, and it hands a caller every name and title needed to sound credible.

The help desk itself is often stretched thin. One service desk may support dozens of agencies, a whole county, or a campus with thousands of students and staff who turn over every semester. Agents are measured on how fast they resolve tickets, and a polite, slightly frantic caller who “just needs to get back into email before the council meeting” is a ticket like any other.

Comparitech counted 77 ransomware attacks on education in the third quarter of 2026, up 54% from the quarter before, with higher education up 88%. Nobody knows how many began with a phone call. Each one began with someone getting access they should not have had.

What to do now

CIS’s own recommendations start with the help desk, and that is the right place to begin. A few practical steps:

  • Raise the bar for help desk verification. Resets, MFA changes and new device enrollments should require more than a name and an employee ID. A callback to the number on file, or a manager’s confirmation, slows an attacker far more than it slows a real employee.
  • Treat passkey enrollment like a password reset. Any request to register a new authenticator deserves the same scrutiny, no matter how routine it sounds.
  • Tell staff what the help desk will never ask. If IT will never request a one-time code or ask you to approve a push you did not start, put it in writing and make sure every employee has seen it.
  • Lock down Teams external access. Limit which outside tenants can message your users, and flag first-contact chats from accounts claiming to be IT.
  • Watch for what happens after the call. CIS points to new device enrollments, unusual MFA push activity and impossible travel as signs that a call succeeded.
  • Find out what your help desk would do. The 2026 Verizon DBIR logged 35 voice simulation campaigns against thousands for email. Very few organizations have measured how their agents respond to a confident caller asking for a reset.

The real question

State agencies, counties, school systems and universities did the hard work of rolling out MFA. The real question is whether the people who reset it would recognize a convincing request from someone who should not have it. In most organizations, nobody has checked.

Want to know how your help desk handles a call from “a locked-out employee”? Book a vishing demo and we will run a live, authorized AI voice call against your service desk lines, so you see exactly what your agents said and where verification broke down.

Want to see it happen? Watch how a single phone call talks a university help desk past MFA, in under four minutes.