Mail Bombing Sets Up Helpdesk Impersonation and Account Takeover Attempts

src-d13b6692

Cybercriminals are flooding targeted inboxes with subscription messages and then contacting recipients while posing as internal IT staff, according to Fortra Intelligence and Research Experts (FIRE). The researchers say the combined activity is intended to distract users and use the apparent disruption as a pretext to compromise accounts or systems.

FIRE described the campaign in an update published November 19, 2026. Mail bombing in this activity does not require an attacker to access the victim’s mailbox. Instead, attackers submit a target’s email address to newsletter, registration and other signup forms across unrelated websites, causing legitimate services to send a high volume of messages.

The flood can interfere with customer service and ordinary correspondence. It can also make it harder for a recipient to spot important notices—such as account alerts or payment notifications—amid the volume of subscription emails. FIRE said individual messages can look routine and may not contain malicious links, complicating detection based on message content alone.

Distraction followed by a helpdesk pretext

FIRE has observed phishing attempts during mail-bombing waves. The researchers said such attempts are harder to identify when mixed in with otherwise legitimate subscription messages. The activity has also been followed by vishing calls made through Microsoft Teams.

In those calls, the caller claims to represent the organization’s internal IT team and gives the target verbal and email instructions purportedly intended to stop the incoming messages. Fortra said the instructions are instead aimed at compromising the user’s account, system or both. The combination gives attackers a plausible reason to initiate contact at a moment when the recipient may be distracted and looking for help.

The reported pattern makes verification especially important. An unexpected caller who knows about an inbox disruption should not be treated as legitimate solely because the problem is real. Employees should use established internal channels to confirm a support request, rather than following unsolicited instructions from a caller or relying on contact details supplied during the call.

Scale and delivery services

Fortra reported that the observed campaigns have reached a peak average of 10,000 delivered messages per active campaign, with roughly 1,000 emails per day. Mailchimp and its transactional email service, Mandrill, were the most frequently observed delivery services, followed by Amazon SES and SendGrid.

The use of legitimate email delivery platforms helps explain why blocking individual senders may not be sufficient. Fortra noted that allowlist exceptions can make containment more difficult when they cover platforms carrying the subscription flood. The researchers also said there are indications the activity may involve an AI-agent setup instructed to find newsletter subscription forms across webpages. That possibility has not been established as a confirmed explanation for every observed campaign.

Fortra has not attributed the activity to a particular threat group. The reported use of signup forms means the delivery volume can be generated without a mailbox compromise, so organizations should avoid assuming that a flood by itself proves an account has been accessed.

Monitoring and response

Fortra recommends comparing email volume for each recipient with that recipient’s normal baseline. Security teams should investigate abrupt bursts from many unrelated senders, particularly when messages contain subscription language or mailing-list headers. Reviewing the pattern at the recipient level can help distinguish an unusual coordinated flood from routine mail traffic.

Teams should also contact the relevant email delivery provider directly to confirm the scope and duration of the activity. During FIRE’s investigation, Mailchimp advised that senders could request temporary subscription blocking for a specified recipient. Mailchimp also documents a separate automatic control that prevents an address from joining additional audiences for 24 hours after repeated signups in a short period.

For incident responders, the operational challenge is to manage the flood without weakening protections or creating overly broad allowlist exceptions. At the same time, staff should be reminded that a claimed IT intervention arriving during the disruption needs independent verification. Monitoring recipient-level volume, coordinating with providers and validating helpdesk contact through trusted channels address different parts of the same reported sequence.