Subscription Bombing Floods Inboxes Before Fake IT Helpdesk Calls on Microsoft Teams
Attackers are signing victims up to thousands of newsletters through ordinary signup forms, then calling on Microsoft Teams as the IT helpdesk. Fortra says Mailchimp, Mandrill, Amazon SES and SendGrid mail dominates the floods.

Attackers are flooding employees' inboxes with thousands of newsletter confirmations and welcome emails, then calling the same people on Microsoft Teams while pretending to be the IT helpdesk that can "make it stop". The warning comes from Fortra Intelligence and Research Experts (FIRE), which describes campaigns peaking at around 10,000 messages per target and averaging about 1,000 emails a day.
The flood does not require any access to the victim's mailbox. The attackers submit the target's address to signup, demo and prospecting forms on unrelated websites, and those websites' own email platforms do the rest. FIRE says Mailchimp and its transactional service Mandrill were the most frequently observed sources, followed by Amazon SES and SendGrid, and that the form filling is likely run by an AI agent told to crawl the web for newsletter forms.
That makes it a sender problem as much as a security one: every business with an open signup form can be turned into one of the thousands of voices in someone else's flood.
Key facts
- Who reported it: Fortra Intelligence and Research Experts (FIRE), in a November 2026 research update
- Technique: subscription bombing, where a target's address is entered into signup forms on many unrelated websites, followed by a Microsoft Teams call from a fake internal IT contact
- Volume: peaks of about 10,000 messages per active campaign, around 1,000 emails per day on average
- Delivery services seen most: Mailchimp and Mandrill, then Amazon SES and SendGrid, plus self-managed newsletter infrastructure
- Automation: FIRE says the form filling is likely an AI agent set up to crawl pages for newsletter, demo and prospecting forms
- Attribution: none; FIRE names no threat actor
How the attack works
Mail bombing deliberately buries an inbox under unwanted messages. Its most common form today is subscription bombing: the attacker never touches the target's account, but signs the address up to as many lists as possible. Each website then sends what it always sends to a new subscriber: a confirmation request, a welcome message, a first newsletter.
Once the inbox is unusable, the second stage starts. A caller reaches the target over Microsoft Teams, introduces themselves as internal IT, and offers verbal and written instructions that supposedly stop the flood. According to FIRE, the real goal is to compromise the user's account, their computer, or both. The pretext works because the caller already knows about the problem the victim is living through.
FIRE also saw phishing emails mixed into the waves, using fake validation steps and loading screens. It could not confirm that the same operator sent them or that they were tied to the Teams calls, only that both happened at the same time.
Why filters struggle with it
Each message in the flood is, taken alone, legitimate mail. FIRE notes that subscription emails can pass SPF, DKIM and DMARC and often carry no malicious link or attachment, because they come from real businesses using real email platforms. The tell is the pattern: unusual volume from many unrelated senders, repeated signup wording, and mailing-list headers such as List-Unsubscribe, which ordinary newsletters also carry.
Allowlists make containment harder. Organisations that allowlist large delivery platforms so that their own vendors' mail always arrives may find that the same exception lets the flood through. FIRE advises against broad blocks on shared delivery platforms and recommends temporary, recipient-scoped controls with a review and an expiry date instead.
The damage goes beyond annoyance. A buried inbox hides account alerts, payment notices and customer requests, and for teams that turn incoming email into support cases, it can swamp the queue.
What the email platforms offer
FIRE reports that, during its investigation, Mailchimp said senders could request temporary subscription blocking for a specified recipient, with the scope and duration to be confirmed with Mailchimp. Mailchimp also documents an automatic control: on its fake signups help page, it says that when one address is added to several audiences in a short time, it blocks that address from joining any other audience for 24 hours. The same page says reCAPTCHA is added automatically to Mailchimp hosted forms and can be switched on for embedded and pop-up forms.
FIRE points out that the 24-hour restriction applies to Mailchimp audience signups only. Whether a similar protection covers messages sent through Mandrill by many different senders has to be checked separately.
What it means for senders
What changes
Open newsletter and demo forms are being used as weapons to flood victims' inboxes before a fake IT support call on Microsoft Teams. Any business with a signup form can end up sending part of someone else's flood.
Who is affected
Employees targeted by the campaigns and their IT and security teams, and every sender whose signup, demo or lead form accepts an address without confirming it, including customers of Mailchimp, Mandrill, Amazon SES and SendGrid.
When
Now. FIRE describes active campaigns in a November 2026 update and names no threat actor.
Action checklist
- Switch your signup forms to confirmed opt-in so a typed address receives one confirmation request and nothing else until it is confirmed; see double opt-in for email lists.
- Rate limit form submissions per address and per IP, and cap how many confirmation requests the same address can trigger, as FIRE recommends.
- Add bot protection such as reCAPTCHA or a hidden honeypot field to embedded, pop-up and demo request forms, not only to hosted pages.
- Watch for bursts of new signups from addresses at one company or domain that never engaged with you, and suppress them before your welcome sequence runs.
- Answer abuse reports quickly when a victim or provider complains, and remove the address from every list it was added to.
- Brief your own staff that IT will never phone them on Teams to fix an email flood, and that any support contact must be checked through the usual helpdesk.
- Review allowlist exceptions for shared delivery platforms and prepare a temporary, recipient-scoped block you can apply and remove quickly.
Sources
- Fortra Intelligence and Research Experts: Mail bombing as a pretext for a Teams vishing attack, November 2026 (primary source)
- Mailchimp: About fake signups (24-hour audience restriction, reCAPTCHA, honeypot fields)
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter