KnowBe4 has flagged new research from CrowdStrike showing that vishing and device code phishing attacks are surging, with voice phishing intrusions doubling in the first half of 2026 compared with the second half of 2025, and device code phishing attacks rising fifteenfold over the same six-month window. Voice phishing, known as vishing, involves a caller posing as IT support and talking an employee through granting remote access or resetting a password, sometimes moving from that first call to stolen data in under five minutes.

The findings come from CrowdStrike’s threat hunting arm, OverWatch, and were reported on the KnowBe4 blog. CrowdStrike names two groups it tracks, CORDIAL SPIDER and SNARKY SPIDER, as using vishing calls to compromise single sign-on accounts and pull data straight out of cloud applications, without ever needing to move around inside a network.

The appeal for attackers is simple: a phone call leaves almost no forensic trail, and a real person on the other end of the line is far more convincing than an email. CrowdStrike’s researchers note that attackers routinely pose as IT staff citing a “trivial support issue” as the pretext, which is exactly the kind of low-stakes request a busy employee is unlikely to question.

Device code phishing works differently but with the same effect. It abuses a legitimate Microsoft sign-in process called the OAuth device authorisation flow, tricking a user into entering an attacker’s code on a real login page. Because the victim is genuinely authenticating, the attack sails past multi-factor authentication (MFA) entirely, the attacker simply takes the access token that comes out the other end.

What this means for small businesses

Neither attack needs malware, and neither needs the target to click a dodgy link, which is why standard email filtering will not catch them. That makes this a training and process problem as much as a technical one, similar to the gap highlighted in our guide on writing an AI usage policy for your small business: rules only work if staff know when and how to apply them.

Firms already dealing with breaches through other routes, such as the ones flagged in our coverage of vibe coding security risks, should treat this as another reason to tighten identity checks rather than assume MFA alone covers them. It is also worth reviewing what your outsourced IT support actually does day to day: businesses using a managed provider, of the sort discussed in our piece on Redsquid’s acquisition of ARK ICT, should ask directly whether vishing and device code phishing are covered in their client’s security awareness training.

None of this needs an enterprise security budget. It needs a written policy that no one grants remote access or enters a device code on a call they did not initiate, and a simple habit of hanging up and calling the IT helpdesk back on a known number. Businesses that have already had to rebuild after an attack, such as the ones affected by the Gentlemen ransomware gang, tend to say the same thing afterwards: the weak point was a person being helpful, not a piece of software failing.

What to do today: tell your team that IT support will never ask them to read out a code or approve a login over the phone, and agree a callback process for any unexpected “urgent” request. It costs nothing and closes the exact gap these attacks are built to exploit.