DKIM replay is the reuse of a legitimately signed email so it continues to appear authenticated after the attacker modifies the lure elsewhere in the delivery chain. The signature may still validate, but the message can be repurposed to support phishing or fraud.
How DKIM replay works
DKIM replay happens when an attacker takes a legitimately signed email and reuses it so the DKIM signature still validates, even though the message has been repurposed elsewhere in the delivery path. That makes the email look trustworthy to recipients and filtering systems that rely too heavily on authentication alone.
Because DKIM validates message integrity and signing domain association, replay abuse is dangerous precisely where trust is inferred from a valid signature. The attacker does not need to forge the signature, only to exploit the fact that a previously valid message can still look authentic after it is reused in a different context.
Why DKIM replay is dangerous
Replay is especially effective in phishing and fraud because the message can carry the credibility of a real sender while the surrounding lure, landing page, or request has been changed. That lets an attacker preserve the appearance of legitimacy while redirecting the victim toward a malicious action.
The risk is not limited to message content. A replayed message can also preserve organisational trust signals such as a familiar sender domain, making the lure harder to challenge than an unsigned or plainly spoofed email. The strongest defence is to avoid treating DKIM as a standalone proof that the email, as received, is safe to act on.
Where organisations should look for exposure
Exposure is most likely in mail flows that accept authenticated mail from outside the organisation, especially when messages can be forwarded, relayed, or reintroduced into campaigns after they have been captured. The practical question is whether the message can be copied, modified around the edges, and still arrive with a valid signature that downstream tools will trust.
Review the mail path end to end, including inbound gateways, forwarding services, mailing lists, partner relays, and any system that rewrites headers or envelope data. NHI Management Group’s DMARC, SPF and DKIM Guide is a useful reference for understanding how DKIM fits into a broader email authentication stack, including alignment and enforcement choices.
Prevention and response
Defence should assume that a valid signature is necessary but not sufficient. Organisations should tighten domain policy, reduce opportunities for replay through stronger alignment and enforcement, and make sure email security controls evaluate context, not just cryptographic validity. Where mail is distributed through third parties, the policy and operational model should be explicit about what is allowed to be resent or rewritten.
If replay is suspected, examine whether the same signed message has appeared in multiple places with altered surrounding content, unusual recipient targeting, or suspicious conversion behaviour. NHI Management Group’s Email Identity and BEC Guide helps connect email authentication weaknesses to the broader fraud patterns they support, including invoice fraud and mailbox takeover.
Replay-resilient email handling is strongest when authentication is paired with policy, filtering, and user verification steps that do not depend on the signature alone. For organisations dealing with active abuse, the right response is usually to block the campaign pattern, review the sending path, and harden the delivery rules that allowed the message to be reused.
Detection and post-incident review
Detection is partly a mail-security problem and partly an investigation problem. Look for repeated signed content reaching different recipients, sudden reuse of otherwise legitimate sender identity, and message bodies that are similar except for the lure elements attackers have changed outside the signed portion. A single valid DKIM result should not close the case if the message behaviour looks wrong.
After a suspected replay, review whether any downstream trust decisions were made on the basis of the signature alone. RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP) is not an email standard, but it is a useful reminder of the general security principle that proof should be bound to the intended use, not merely valid in isolation. In email, the analogue is to validate sender authenticity, message context, and recipient-facing intent together.
Risk and Threat Considerations
DKIM replay turns a legitimate authentication signal into an abuse path. The attacker is not trying to break cryptography, but to reuse a trusted message so the victim and the mail stack continue to treat it as genuine while the lure is repurposed for phishing, invoice fraud, or other deception.
Failure mechanism: A previously signed message is copied or relayed into a new context where the signature still validates, but the attacker has altered the surrounding delivery or targeting logic to make the message serve a malicious purpose.
Impact: The result can be higher click-through, better bypass of naive trust filters, and a stronger chance that users or automated systems act on a message that appears authenticated but is no longer trustworthy in its current form.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Replay abuse depends on the lifecycle and trust of authenticators and signed material. |
| Recommendation — Bind authentication material to its intended use and rotate or revoke it when reuse risk appears. | ||
| CIS Controls v8 | CIS-5 — Account Management | Email trust abuse often succeeds where legitimate accounts and send paths are not tightly governed. |
| Recommendation — Limit and review who can send through trusted mail paths and remove unused delivery permissions. | ||
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | Replay is an abuse of legitimate trust material that remains valid after reuse in another context. |
| Recommendation — Treat reusable trust material as compromised when it can be repurposed beyond its intended delivery path. | ||
| MITRE ATT&CK | T1566 — Phishing | DKIM replay is commonly used to strengthen phishing by making the lure appear authentic. |
| Recommendation — Correlate authenticated-email indicators with phishing content and delivery anomalies in your detection workflow. | ||
| NIST CSF 2.0 | PR.DS-10 — Data-in-Transit | The concept involves trust in transmitted email content and its integrity across the delivery chain. |
| Recommendation — Protect message integrity across transit paths and validate downstream handling that can alter trust context. | ||
Practitioner Guidance
Why practitioners should care: DKIM replay is a reminder that email authentication is only one trust signal. Mail teams should treat a valid signature as part of the evidence set, not as a complete decision. The practical objective is to make sure policy and filtering can still distinguish a genuine message from a reused one.
What to watch for: Pay attention to legitimate-looking messages that reappear in new recipient groups, contain altered calls to action, or arrive through unusual forwarding and relay paths. Those patterns often matter more than the signature result itself when replay is involved.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org