Skip to main content

The call from “IT” that gets past your MFA: what the Cyber Centre’s alert means for Canadian firms

The Cyber Centre has warned of an ongoing help desk voice phishing campaign against Canadian organizations, concentrated on legal and financial firms. Ordinary MFA does not stop it. What it is, what to do, and the question for the board.

Checked on 17 November 2026. On 28 October 2026 the Canadian Centre for Cyber Security issued alert AL26-028 about a voice phishing campaign against Canadian organizations. It is ongoing, it has concentrated on law firms and financial firms, and it gets past the kind of multi-factor authentication most businesses rely on. The alert is here, and it is worth ten minutes of whoever runs your IT.

What is happening

Someone telephones a member of staff, or messages them on Microsoft Teams, claiming to be your own IT help desk. The story is urgent and plausible: a passkey migration, a new MFA enrolment, a password that must be changed today. The caller may know colleagues’ names, may appear to be calling from your real help desk number, and according to the Cyber Centre may simply hang up if the employee tries to check.

The employee is sent to a sign-in page carrying your organization’s branding. It is not yours. It passes the password and the MFA code straight through to the real sign-in service, and the attacker walks away with a signed-in session. From there the Cyber Centre describes a consistent pattern: the attacker registers their own MFA device so they can come back, deletes the security notification emails that would have warned the user, pulls files out of Microsoft 365 including SharePoint and OneDrive, and then sends an extortion demand.

Why this reaches organizations that think they are covered

Most organizations that have “turned on MFA” use codes, text messages or approval prompts. This campaign defeats all three, because the employee completes the MFA step themselves on the attacker’s page. The Cyber Centre says activity has moved between sectors during 2026, has leaned towards finance and legal since July, and was concentrated on the legal sector in October. Nothing in the method is specific to those sectors. It works on any organization whose staff will act on a confident call from “IT”.

What the Cyber Centre says to do

  • Move to phishing-resistant MFA — security keys, device-bound passkeys or platform authenticators — starting with administrators and anyone handling money or client files.
  • Require managed devices for sign-in, and restrict sign-ins from commercial VPNs, hosting providers and residential proxies.
  • Tighten the checks before anyone resets MFA, recovers an account or enrols a new device.
  • Tell staff, in plain words, that an unexpected call from IT asking for an MFA, passkey or password change is to be verified through a number they already hold — whatever the caller ID says and however urgent it sounds — and give them one obvious place to report it.
  • Watch for new MFA registrations, bulk or scripted file access, deleted security emails, and newly registered domains carrying your name.
  • Limit who outside the organization can contact staff on Teams, Webex or Slack.
  • If you suspect it has happened: revoke sessions and tokens, reset credentials, remove MFA methods you do not recognize, and keep the identity and Microsoft 365 audit logs.

What it means under Canadian privacy law

If client or employee personal information leaves through a compromised account, PIPEDA’s breach rules apply in the ordinary way: a record of the breach kept for two years, and a report to the Privacy Commissioner and notice to the people affected where there is a real risk of significant harm. An extortion demand after data theft will usually put you in that territory. Organizations in Quebec have the parallel duties under Law 25.

The board question

If someone who sounded exactly like our IT help desk rang a partner, a finance lead or an executive assistant this afternoon, what would stop them — and when did we last test it rather than assume it?

We date our briefings because a governance claim without a date is not a governance claim. If the Cyber Centre updates AL26-028, we will update this page and say what changed.

Leave a Reply

Your email address will not be published. Required fields are marked *

Standards we assess against

ISO/IEC 27001:2022 · ISO/IEC 27701:2025 · ISO 9001:2015 · ISO/IEC 42001:2023 · ISO/IEC 23894:2023 (guidance) · ISO/IEC 42005:2025 (guidance)

Français : La première heure — rédigé en français, pas une traduction automatique.

Canada Cyber-Safe is an independent assessment practice. We are not a certification body and we do not issue certificates.