Forum Discussion
My 25+ years Microsoft account got hacked by someone with bibimail, and I can't recover it
I have a similar problem , so here is what i did , waiting to response my microsoft team :
Step 0 — Clean your devices FIRST (non-negotiable)
Microsoft's own guidance: run a full antivirus scan before changing any passwords — if an infostealer is still on your PC, the attacker will just steal the new password and re-take the account. Use Windows Defender full scan + a second opinion (e.g., Malwarebytes free scan). Also check your browsers for suspicious extensions and clear saved cookies.
Step 1 — Try the sign-in helper
Go to Microsoft's "How to recover a hacked or compromised Microsoft account" page and use the sign-in helper tool — it routes you to self-help or an agent depending on your situation.
Step 2 — The Account Recovery Form (your main weapon): account.live.com/acsr
Since your alias was removed, this automated form is your primary path. Critical tactics:
Use your ORIGINAL email address as the account identifier, plus a working contact email you control.
Fill it out from a device and location you previously used to sign in — this significantly raises your success odds.
Accuracy beats quantity — wrong guesses hurt more than blanks.
Provide: old passwords (even years-old ones — check browser saved passwords), exact email subject lines (search your other mailboxes for messages you sent from that account), frequent contacts, Skype ID, and especially purchase proof: order numbers, billing name/address, last 4 digits of the card used.
Xbox users: include the console's hardware/Device ID — that field carries heavy weight.
You can submit 2 times per 24 hours; if rejected, improve the data before resubmitting rather than repeating the same answers.
⚠️ If the attacker enabled 2FA on the account, the form may tell you the request will be ignored — that's the hardest scenario.
Step 3 — Escalate to a human via live chat
Go to support.microsoft.com/home/contact, type "MSA", sign in with any other working Microsoft account (create a temporary new one if needed), choose Microsoft 365 and Office → Manage account security → Chat with Support Agent in Web Browser. Ask the agent to suspend/freeze the compromised account to stop the attacker using it (victims have succeeded in getting hijacked accounts suspended this way), and give them your ACSR case number, purchase receipts, and Xbox device IDs. Be honest with yourself about the limit here: support agents cannot manually reset consumer accounts — but they can suspend, and occasionally escalate strong proof-of-ownership cases.
Step 4 — Report the attacker infrastructure
Report the abuse to the registrar: email address removed for privacy reasons (from your WHOIS lookup) — disposable domains used for account takeover can be flagged. (Note : i dont think it will work.)
Report to Microsoft: https://msrc.microsoft.com/report/abuse and to your local cybercrime authority (e.g., IC3.gov in the US, Action Fraud in the UK).
Part 3 — Protect the Blast Radius (do today)
The attacker will try your Microsoft credentials elsewhere and can reset passwords on anything tied to that inbox:
Change passwords on every account that used the same or a similar password — email, banking, Discord, EA, social media. Use a password manager and unique passwords.
Check the mailbox that received Microsoft's security alerts (the Gmail/etc. that got the "your security info was changed" notification) — Microsoft sometimes includes undo links valid for a limited window. Search it now for any "Remove this alias" or "this wasn't me" links. This is occasionally an instant-recovery path if caught early.
Freeze/notify your bank if cards were stored in the Microsoft account.
If you regain access, immediately: remove the bibimail alias, change password, enable Microsoft Authenticator + a hardware key or passkey, generate and save the 25-digit recovery code offline, review sign-in activity, and purge any malicious Outlook rules/forwarding the attacker set up.
"hi all ,
Almost 1 month and multiple recovery " Recover your Microsoft account" form submissions . multiple agents one simple response "
Greetings,
Thank you for contacting Microsoft Support. My name is ******* , and I’m part of a team dedicated to investigating account security concerns.
The information you have provided either does not match our records or is incomplete. As a result, I am unable to validate account ownership and therefore will not be able to proceed with the investigation.
.........
Thank you for your understanding and patience during our investigation. This case will now be closed, and any further replies will go to an unmonitored mailbox."
I’m posting here because I’ve now gone through the Microsoft Account Recovery process three separate times, and each attempt has been rejected.
In my situation, this account holds for few years now personal data — emails, documents, subscriptions, and identity history. I’ve provided every possible information I can access outside the account, but the recovery form keeps asking for details that are impossible to provide when you’re locked out. If I cannot access the account, I cannot know when I last changed my password or which exact folders I created years ago. I can only submit what I genuinely have.
The hacker who took over my account in matter of mins and fully locking me out. It’s discouraging that a major tech company cannot restore an account with two decades of traceable activity, especially when the user is clearly demonstrating ownership through every available method.
I can see from other posts that I’m not alone - many people here have gone through the same cycle of repeated submissions and repeated rejections. At this point, it feels like the system is designed to close cases quickly rather than investigate them thoroughly.
I’m hoping someone from Microsoft can escalate this or provide a more realistic path forward. When long‑term users lose access, the recovery process should support them, not block them.
Microsoft Support - please escalate this. The recovery system is rejecting valid cases.
- GlosaeOct 13, 2026Copper Contributor
Same. This is absolute disaster.