Inbox Floods Followed by Fake IT Calls: How Mail Bombing Is Being Used to Hijack Accounts
Fortra Intelligence and Research Experts (FIRE) are tracking a campaign in which criminals deliberately flood a target's inbox with emails, then follow up by pretending to be the victim's IT helpdesk. In an update published on November 19, the researchers described how the two steps work together to compromise user accounts.
Mail bombing does not require access to the target's mailbox. Instead, attackers submit the victim's email address to newsletter, registration and other signup forms across many unrelated websites. The resulting flood can disrupt customer service and routine correspondence, and it can bury account alerts, payment notifications and other messages that need attention. FIRE said there are indications the attacks may use an AI agent instructed to crawl webpages for subscription boxes. Mailchimp and its transactional service Mandrill were the most commonly observed delivery services, followed by Amazon SES and SendGrid. Fortra said an attack peaks at around 10,000 messages per active campaign, roughly 1,000 emails per day.
Once the inbox is overwhelmed, the attacker makes contact through Microsoft Teams. Claiming to be internal IT, they give the user verbal and email instructions that supposedly stop the flood, but are really an attempt to compromise the account, the device, or both. FIRE has also seen phishing messages sent during these waves, which are harder to spot among the legitimate-looking emails.
Detection is difficult because individual subscription emails look normal and may contain no malicious links. Allowlist exceptions covering the delivery platforms carrying the flood can also make containment harder. Fortra recommends monitoring email volume per recipient against a normal baseline, and investigating bursts from many unrelated senders, subscription wording and mailing-list headers. Teams should also confirm scope and duration with the delivery provider. Mailchimp said senders can request temporary subscription blocking for a specific recipient, and it has an automatic control that restricts an address from joining more audiences for 24 hours after rapid repeated signups. Fortra did not attribute the campaign to any group.
Why it matters
This attack manufactures the problem that the fake helpdesk then offers to solve, so a user who is overwhelmed is primed to trust the caller. It also exposes weak points in email defences: harmless-looking subscription mail passes filters, and allowlisting major delivery platforms can let the flood and any hidden phishing through. Businesses that allow external Teams contact and have no per-recipient volume monitoring are most exposed.
What to do
- Monitor email volume per recipient against the normal baseline and alert on sudden bursts.
- Investigate bursts involving many unrelated senders, subscription wording and mailing-list headers.
- Review allowlist exceptions that cover delivery platforms such as Mailchimp, Mandrill, Amazon SES and SendGrid.
- Confirm the scope and duration of a flood directly with the email delivery provider.