Email Bombing Fuels Microsoft Teams Helpdesk Scams

Attackers are flooding employees’ inboxes with thousands of unsolicited messages before posing as internal IT staff on Microsoft Teams, turning an email nuisance into a social-engineering pathway to account or device compromise. The campaign is being tracked by Fortra’s Intelligence and Research Experts, which says the Teams contact arrives while the mail flood is still underway. Fortra’s November 19 report describes the activity as targeted, large-scale “mail bombing” followed by Teams vishing. [16]

The bombing itself does not require access to the victim’s mailbox. Instead, attackers submit a target’s address to newsletter, registration and other online signup forms, causing legitimate services to generate a deluge of confirmation and subscription messages. Fortra said observed campaigns peaked at about 10,000 messages, with roughly 1,000 arriving per day during active operations. The volume can obscure security alerts and make a user more receptive to anyone offering an immediate solution.

Once the flood begins, an unsolicited Teams contact claims to represent internal IT and offers verbal or emailed instructions to stop it. Those instructions may seek credentials, remote access, security-setting changes or execution of software. Fortra said the observed actors’ exact objective can differ and warned that a support call alone does not prove compromise; defenders must investigate what the user was asked to do and what actions followed.

There is no CVE associated with the technique, and the report does not identify a software flaw or confirm a named threat actor. Fortra also said it could not verify whether the operators responsible for the email bombing sent the observed phishing messages or were connected to the Teams activity, even though the events occurred concurrently. The campaign therefore represents an abuse of trust and workflow rather than a vulnerability that can be fixed with a single vendor patch.

Organizations should treat an unexpected Teams support approach during an inbox flood as a potential incident. Employees should end the contact and reach the helpdesk through a known, independently verified channel rather than using a phone number, link or address supplied by the caller. Security teams should preserve representative email headers, Teams account and call identifiers, chat history and a user timeline before cleaning up the mailbox, then review identity, endpoint and remote-access logs for follow-on activity.

Fortra also recommends reviewing Microsoft Teams external-access settings and restricting external domains where business requirements permit, while recognizing that domain blocking cannot address every compromised partner account. Administrators should pair those controls with clear guidance that legitimate support staff will not demand passwords or unexpected remote access, and should monitor for unauthorized remote-support tools and unusual data movement after any suspicious interaction. The vendor’s incident-response guidance emphasizes independent verification and evidence preservation rather than assuming that restoring inbox usability resolves the threat. [16]

References

  1. Mail Bombing as a Pretext: Teams Vishing as the Attack

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply