Treat a second request from someone you already know as a reason to pause and verify, not as proof either way. A separate profile that copies their name and photos may be a duplicate; a real account that behaves oddly may be compromised. Confirm through a channel you already had before the request, then choose the matching action: if the original account is fine, address the imitation; if the owner is locked out, point them to account recovery.
Find public social profile clues with our TraceSeek app.
Why a second request deserves a pause
If you are already connected to someone, another request from what looks like the same person is an inconsistency worth noticing. That inconsistency is the only reliable starting observation, and it is a reason to slow down rather than a conclusion. From the request alone you cannot tell whether you are looking at a separate lookalike profile or a real account now used by someone else. The next step is the same either way: verify outside the new thread before responding. [Facebook Help: Recover a hacked account]
Duplicate profile versus taken-over account
The practical difference is where the problem lives. In a duplicate scenario, imagine a separate public profile imitating your friend while the original remains under their control. In a takeover scenario, imagine the original account itself being used by someone else. These are hypothetical illustrations, not diagnoses you can make from the request alone. Avoid judging from response speed, photo similarity, friend counts, or how convincing the profile looks, because none of those confirm identity or intent.
| observation | limit | next step |
|---|---|---|
| A second request from a name you already have | Could be a duplicate profile or a real account in someone else's hands; the request proves neither | Contact the person through a channel you already used before this request |
| Similar name and copied-looking photos | Public images are easy to copy and do not establish who runs the profile | Do not accept, reply, or send anything until you confirm by another route |
| A message asking for money or login codes | May suggest a compromised account, but the message alone is not proof | Do not send money or codes; protect your accounts first, then verify through a known channel |
Verify through a channel you already know
Use a route that existed before the request: an independently known number, an already trusted conversation or an in-person conversation. Ask whether the new profile is theirs and whether they notice unauthorized activity in their usual account. Continuing to log in does not by itself rule out compromise. If they identify the second profile as an imitation, report that profile; if they suspect unauthorized access to their existing account, the owner should also use Facebook’s account-security and recovery guidance. Both problems can need attention.
- Reach the person by a number or thread you used before this request
- Describe what you received without clicking or replying in the new thread
- Ask whether they still control their usual account
- Decide on your next action only after that reply
Choosing the right action afterward
Facebook separates recovery of an existing hacked account from reporting an imposter account. That separation matters for what you do next. If your friend confirms their account was taken over, recovery is something the account owner does; the official hacked-account route recommends using a device previously used to log into their own account. If your friend confirms the second request came from a profile that is not theirs, the imitation is the separate issue rather than their account being locked. Keep the two situations distinct so advice to your friend is not muddled with your own reporting. [Facebook Help: Recover a hacked account]
What not to treat as proof
A matching profile picture, a familiar name, mutual friends, a polished page, or a quick friendly reply are all easy to arrange or copy, and none of them establishes identity. Silence, a privacy setting, or a badge is not evidence of wrongdoing either. Do not accuse the person or the profile of anything based only on the request; describe what you observed and ask. If money, login codes, or identity documents are requested, treat protecting your accounts and money as the first action and pause the conversation entirely.
- Do not send money, codes, or documents to the new profile
- Avoid forwarding the suspicious thread to others as proof
- Keep a calm, factual note of what you received and when
A couple more questions
If the profile looks identical to my friend's, is it definitely a clone?
No. Copied names and photos are consistent with a duplicate profile, but a real account can also be taken over and look unchanged to you. Confirm through a channel you already had before deciding.
Should I accept the second request while I check?
Better to wait. Accepting or replying in the new thread gives whoever runs it more access to you, and it does not help you verify anything. Confirm outside the thread first.
My friend says they can still log in. What then?
They should still review unexplained activity; being able to log in does not rule out compromise. Ask whether the new profile is theirs through a known channel. An imposter profile and unauthorized access to the real account are separate issues and can require separate reports or recovery steps.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.