Thread hijacking
Thread hijacking is an email attack that inserts a deceptive message into an existing conversation, or reuses its contents, to make the new request appear part of a trusted exchange.
A real conversation carries a new request
Proofpoint has documented attackers using compromised supplier mailboxes to join ongoing invoice conversations. Real invoice details and earlier replies give the fraudulent message a history that a cold email would lack. It also observed attackers moving those conversations to impersonation accounts by changing reply-to or copied addresses. Recovering the original mailbox may leave that separate conversation going.
This differs from simply copying a sender’s name. The attacker uses the conversation’s context, and may send from a genuine account. Email authentication can pass for mail sent through a compromised account, so it cannot settle whether the request is authorized.
Verify what changed
Check the new instruction, even when the earlier exchange is genuine. For payment changes, the FBI recommends confirming with the requester through an independently established contact route. Replying to the same thread asks the potentially compromised conversation to verify itself.
For responders, the message history can help explain what the attacker knew. Check mailbox access, forwarding rules, and changes to participants or reply destinations. A familiar quoted thread alone does not prove that the sender still controls the original mailbox.
The supplier bank-change article covers the payment decision; external mail forwarding explains how correspondence can leave a mailbox without an obvious new participant.