Clone phishing
Clone phishing copies a legitimate message and replaces its link, attachment, or other content with a malicious version, using the original message's familiarity to make the copy convincing.
Familiar wording can hide a changed destination
The message looks like one you have seen before. It might claim to resend a document or supply a corrected link. Much of the content is genuine-looking because it was copied; the part you are asked to use has changed.
A replacement link might lead to a fake sign-in page; a substituted attachment might deliver malware. CERT-MU calls this reuse of a previously delivered legitimate email clone phishing.
The copied wording does not establish that the original sender approved this version. Nor does it tell you how the attacker obtained the original. Avoid assuming a particular mailbox was compromised from appearance alone.
A copied message is not necessarily a hijacked conversation
Thread hijacking uses an existing conversation or its history to make a new request credible. Clone phishing focuses on reproducing a message and changing its contents. The techniques can overlap, but a copied notification does not need to be part of an ongoing thread.
For an unexpected resend, open the document service through your normal bookmark or verify with the sender through an established contact route. Do not let the replacement link verify itself. The shared-document article explains why a familiar sharing notification still needs scrutiny.
Report the suspicious message through your normal process. If the original is available, preserve it too so responders can compare the sender details, destinations, and attachments without asking you to open the suspect file.