Conversation hijacking is the insertion of a fraudulent actor into an existing email thread so the request appears to continue a legitimate discussion. The attacker relies on prior message history, familiar tone, and trusted recipients to bypass human suspicion and complete the fraud path.
How conversation hijacking works
Conversation hijacking succeeds because the attacker does not need to invent a fresh story. They step into an active thread, inherit context from the prior exchange, and use the legitimacy of the existing conversation to make a fraudulent request seem routine, time-sensitive, or already approved.
The technique is especially effective in business email compromise because recipients often trust the thread history more than the latest message sender details. The content may look consistent, the tone may mirror prior participants, and the request can appear to continue a normal workflow rather than introduce a new one.
Why conversation hijacking is hard to spot
The danger is not only the forged message, but the social proof carried by the thread itself. A reply inside a real conversation can bypass the instinctive checks people use when a request arrives from an unknown address or in a stand-alone email.
Small changes are often enough to hide the intrusion: a compromised mailbox, a lookalike display name, a reply routed through a forwarding rule, or a message that references details already present in the thread. That makes manual review difficult because the attack blends with the normal cadence of work.
Conversation hijacking also works across organisational boundaries. If a supplier, customer, or executive mailbox is compromised, the attacker can exploit trusted relationships between multiple parties at once, not just one account.
Common fraud path and business impact
Once the attacker is inside the thread, the usual goal is to redirect money, sensitive information, or an approval decision. The request may ask for an updated bank account, a file share change, a credential reset, or an urgent exception that appears to come from a trusted sender.
Because the thread already contains a history of legitimate discussion, the compromise can lead to payment diversion, data disclosure, or follow-on access to related accounts and systems. In many cases the real harm comes from the trust relationship being reused, not from any technical exploit in the email platform itself.
How organisations reduce exposure
Reducing exposure starts with assuming that thread continuity is not proof of legitimacy. Organisations should treat any change in payment details, delivery instructions, approval flow, or sensitive request as independently verifiable even when it arrives in a familiar conversation.
Controls that help include mailbox protection, sender authentication, strong account recovery controls, and visibility into forwarding rules and suspicious delegation. The goal is to make it harder for an attacker to enter the thread and harder for a fraudulent reply to pass as routine business communication.
Staff awareness matters most when requests are urgent, confidential, or unusually aligned with the tone of the thread. A healthy process is one that forces a second verification step when the consequence of error is high.
Risk and Threat Considerations
Conversation hijacking is risky because it turns legitimate collaboration into an attack surface. The attacker is not trying to break trust from the outside; they are trying to inherit it, then use the normal credibility of the thread to move a fraudulent request to completion.
Failure mechanism: The attacker compromises or impersonates a participant, inserts themselves into an existing message chain, and relies on context, urgency, and familiarity to suppress scrutiny.
Impact: The result can be payment fraud, data theft, unauthorised account changes, or downstream compromise of related business relationships.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses 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 |
|---|---|---|
| MITRE ATT&CK | T1566 — Phishing | Conversation hijacking is a phishing-style social engineering path via trusted email threads. |
| Recommendation — Map suspicious reply patterns to phishing detections and verify thread-based requests out of band. | ||
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Compromised mailboxes and abuse of trusted accounts make account governance central to the threat. |
| Recommendation — Review mailbox and delegated-account ownership regularly and remove stale access paths. | ||
| CIS Controls v8 | CIS-9 — Email and Web Browser Protections | Email thread abuse is directly mitigated through email protection and browser-side controls. |
| Recommendation — Harden email protections and block malicious message delivery paths that support thread hijacking. | ||
| NIST CSF 2.0 | PR.AA-05 — Least Privilege | Limiting mailbox and delegation privileges reduces an attacker's ability to persist in conversations. |
| Recommendation — Apply least privilege to mailboxes, forwarding, and delegation settings that can be abused in hijacking. | ||
Practitioner Guidance
What to watch for: Treat any material change in beneficiary details, instructions, or approval path as a separate verification event, even if it appears in a live thread. The thread is evidence of prior contact, not proof that the current request is genuine.
Governance implication: Organisations should define who can approve exceptions, how out-of-band verification is performed, and when an email request must be escalated to another channel before action is taken.
Practitioner takeaway: The safest assumption is that a believable thread can still be hostile, so verification should follow the request, not the familiarity of the conversation.
Related resources from NHI Mgmt Group
- How should security teams detect conversation hijacking used to deliver malware through email?
- Why does conversation hijacking increase the success rate of phishing campaigns?
- How should security teams detect email thread hijacking when attackers reuse an existing conversation to request payment or access changes?
- What happens when finance teams trust invoice requests or conversation hijacking attempts at face value?
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 October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org