Phishing and BEC through hijacked Amazon SES accounts: leaked IAM keys let attackers send mail that passes SPF, DKIM and DMARC
Kaspersky: attackers use leaked AWS IAM keys to send phishing and fabricated-thread BEC through legitimate Amazon SES accounts
Analysis
Kaspersky reports that phishing sent through Amazon Simple Email Service (SES) rose in January 2026 and stayed steady through the first quarter (Kaspersky Securelist, 2026-05-04). Attackers mostly reach SES through leaked AWS IAM access keys that developers leave in public GitHub repositories, ENV files, Docker images, configuration backups or publicly accessible S3 buckets; bots built on the open-source secret scanner TruffleHog find the keys, and the attackers then check each key's permissions and sending limits (Kaspersky Securelist, 2026-05-04). Because the mail is sent from legitimate infrastructure, it passes SPF, DKIM and DMARC, almost always carries .amazonses.com in its Message-ID header, and comes from sender IPs that reputation blocklists cannot block without blocking all SES mail (Kaspersky Securelist, 2026-05-04).
A common early-2026 lure was a fake electronic-signature notification whose link led to a sign-in form hosted on amazonaws.com (Kaspersky Securelist, 2026-05-04). In a business-email-compromise case Kaspersky investigated, an email posing as an employee went to the company's finance department with a fabricated thread about an outstanding invoice and PDF attachments holding only payment details and supporting documentation, with no malicious link or QR code (Kaspersky Securelist, 2026-05-04). BleepingComputer reported the research the same day (BleepingComputer, 2026-05-04).
Updates1
Kaspersky's report names no sector, country or manufacturing victim; its business-email-compromise case is a single fabricated invoice thread sent to a company's finance department (Kaspersky Securelist, 2026-05-04). The earlier text said Kaspersky observed finance departments at European manufacturing firms being targeted, which no source supports, and cited a Securelist address that does not exist. In most cases attackers use leaked IAM access keys.
Sources2
Revision history
- Published 2026-05-08-migrated
- Correction 2026-10-11T1307Z-audit
The cited Kaspersky URL did not exist; the report is 'Phishing campaigns and BEC attacks through Amazon SES' of 2026-05-04, now cited with BleepingComputer's coverage. The claim that Kaspersky saw finance departments at European manufacturing firms targeted is in no source and is removed, the credential source is described as leaked IAM keys as the report says, and the entry gains its rating, ATT&CK mapping and labelled guidance from the report.
Changed: title headline summary event_date regions techniques sources verification classification body
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.