11 Nov 20264 minutes read
Dumpster Diving Attack: How Discarded Data Becomes Email Impersonation

Dumpster diving overview:
- Attackers recover email threads from deleted and trash folders, where messages stay readable until cleared.
- Recovered threads supply the names, references, and wording that make spoofed emails look routine.
- Spoofed emails reach customers, suppliers, and partners unless full DMARC enforcement blocks them.
- Receiving servers that honor p=reject block messages that fail authentication, however convincing the content.
A customer’s accounts payable team receives an invoice email that appears to come from your billing team. The sender’s name is correct, the invoice reference matches an open order, and the request to update your bank details follows the wording of your usual emails. But the email didn’t come from you.
Dumpster diving is how attackers reach that level of accuracy. They recover discarded email data, such as old threads and approval messages left in deleted and trash folders, and use it to write emails that look routine and appear to come from your domain.
Without full DMARC enforcement, those emails reach the inboxes of the customers, suppliers, and partners who trust your organization.
This article explains what dumpster diving reveals, how attackers use it to carry out business email compromise (BEC), and how full DMARC enforcement blocks spoofed emails.
Find out if your domains can be spoofed. Use the DMARC record checker to see where your domains stand.
Email Data Dumpster Diving Exposes
Dumpster diving is an information-gathering technique, and MITRE classifies it as an attack pattern. In email dumpster diving, the dumpster is the deleted or trash folder. Deleted messages stay readable in these folders until the user empties them, or a retention period clears them automatically.
While they remain, those messages hold the information that makes an impersonation email believable.
A dumpster diving attack can expose:
- Address formats and tools: old threads reveal address naming conventions, internal domains, and the names of the platforms your teams use
- Employee names and roles: email signatures, distribution lists, and message threads identify the finance approvers, IT administrators, and executives whose names carry authority
- Customer relationships: invoice and remittance emails reveal which companies you bill, your payment terms, and the email addresses on both sides
- Organizational processes: approval workflows and renewal cycles show how requests are normally made
A dumpster diving attack requires no technical skill. It supplies what generic phishing lacks, which is accuracy.
How Dumpster Diving Enables BEC
Consider an attacker who recovers three items: invoice emails sent to a customer with payment references, the signatures showing who on your billing team sends invoices, and an email thread showing how bank detail changes are communicated.
With that detail, the attacker can send a customer’s accounts payable team a bank detail change request that appears to come from your billing team’s email address. It uses real names, a real invoice reference, and the wording the customer expects.
The customer pays the attacker’s account instead of yours, and your company is left with an unpaid invoice. The fraud also damages the customer’s trust in your brand, because it arrived under your name.
Dumpster diving is one way attackers collect the details that make these requests credible.
How DMARC Enforcement Limits a Dumpster Diving Attack
DMARC lets you tell receiving servers what to do with email that claims to come from your domain but fails authentication. A message passes if SPF or DKIM validates and matches the domain in the “From” address. At p=reject, receiving servers that honor the policy reject messages that fail this check, so unauthenticated emails don’t reach inboxes.
This control works regardless of how convincing the content is. An attacker running a dumpster-diving attack can recover your domain name, your employee names, and your customer details, and still fail authentication because the sending infrastructure isn’t authorized.
At p=none, the result is different. DMARC reports show failures, but the messages are still delivered. Monitoring gives visibility, not protection.
Reaching p=reject requires an accurate inventory of every sender using your domains.
Marketing platforms, HR systems, regional teams, and acquired entities often send email under your domain without being listed in your SPF record. Moving to p=reject before these senders are authenticated risks blocking legitimate email such as invoices and password resets. A staged approach from p=none to p=reject avoids that disruption.
How Sendmarc Can Help Reduce Dumpster Diving Attack Risk
Large, distributed environments create the conditions that a dumpster diving attack depends on: many senders, many domains, and limited visibility. Security and IT teams are already stretched, and tracking every sender manually doesn’t scale.
DMARC Management addresses the sender problem a dumpster-diving attack exploits. It identifies legitimate and unauthorized senders across departments, centralizes SPF, DKIM, and DMARC management across departments and regions, and surfaces misconfigurations before they become incidents.
Sendmarc helps enterprises reach p=reject and provides hands-on implementation support that removes the need for internal DMARC expertise. The staged approach keeps critical communications flowing. Monitoring and optimization continue after enforcement, so protection stays current as your environment changes.
Attackers use the details from dumpster diving to impersonate you. Full DMARC enforcement blocks those emails before they reach an inbox. Explore DMARC Management to see every sender using your domains and move them to full enforcement.


