hotmail account comprimised

2026-04-13T03:48:54.4666667+00:00

Hi Team,

I am writing to report a security concern regarding my account. It appears the account has been compromised, as I have observed multiple unauthorized login attempts originating from various geographic regions.

I have already updated my password and enabled Multi-Factor Authentication (MFA); however, I am still receiving persistent "Approve Login" requests via my authenticator app. This suggests that the unauthorized parties may still have access to current credentials or are attempting an MFA fatigue attack.
Please let me know if there are any further organizational protocols I should follow or if the security team needs to perform a deeper forensic audit on the account logs.

Outlook | Web | Outlook.com | Account management, security, and privacy

Answer accepted by question author
EmilyS726 276.4K Reputation points Independent Advisor
2026-04-13T15:11:05.63+00:00

Hello

If you get attempts, as long as they are failed ones, it doesn't mean they managed to get into your account.

If someone knows your email address, they can go to Microsoft online and use the forgot password option to trigger an 2FA ask. This is common if your email address is involved in any data breach.

I would recommend that you do this to stop this:

Go to your Microsoft account online https://account.live.com> Sign in > Your info > Sign in preference. Add an alias - You have two options here: Create new: this will allow you to use the native domain outlook.com to create a new alias. Add existing: this will allow you to add a 3rd party email address, such as yahoo, gmail, as long as they are not already associated with another Microsoft account. Once added, make this new alias your primary alias, do NOT delete the old alias. Then at the bottom, click on "Change sign in preference". On the next page, uncheck the box for the old alias. This means, from now one, the old alias cannot be used to sign into your Microsoft account, but it can be still used to receive emails, etc.

Was this answer helpful?

0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Hannish Parayil Gopalakrishnan 20 Reputation points
    2026-05-08T07:04:39.4966667+00:00

    Thank you everyone for your support. It looks like the issue has resolved itself.

    Was this answer helpful?

    0 comments No comments

  2. Victor1-V 13,045 Reputation points Microsoft External Staff Moderator
    2026-04-13T10:55:19.9933333+00:00

    Hi Hannish Parayil Gopalakrishnan,

    I understand how worrying it is to secure your Hotmail account (password changed and MFA enabled) and still keep receiving unexpected “Approve sign-in request” prompts in Microsoft Authenticator.

    I also noticed there is a Q&A Assist answer in the thread. Its core direction (reviewing sign-in activity and securing the account) is generally aligned with the official account-security flow. Have you had a chance to try the Q&A Assist steps yet? If you did and the prompts continue, I would like to add a few key actions.

    1, Use the “Recent activity” page actions, not just a password change

    On the Recent activity page, you can expand entries and use actions like “This wasn’t me” (when available) and “Secure your account” to trigger the built-in protection flow. This is separate from simply changing the password, and it’s the right place to validate whether any access looks unfamiliar. What happens if there's an unusual sign-in to your account - Microsoft Support

    2, Sign out everywhere (force all sessions to re-authenticate)

    Even after a password change, previously signed-in sessions may remain active until they are revoked. The account security dashboard includes “Sign out everywhere” under Advanced security options to sign out browsers and apps on trusted devices. How to sign out of your Microsoft account everywhere - Microsoft Support

    3, If you have multiple aliases, restrict which one can be used to sign in

    If the account has more than one alias, you can block sign-in for specific aliases using Sign-in preferences. This helps reduce unwanted sign-in attempts targeting an older email/alias while keeping the alias on the account. Block an email address from signing in - Microsoft Support

    4, Check for app passwords (only if you have older apps/devices connected)

    If two-step verification is enabled and older apps/devices are connected, the account may be using app passwords (created under Advanced security options). Reviewing that section can help you identify whether an older device/app is still attempting to authenticate. 

    5, Treat unexpected codes/prompts as “deny and secure,” not something you must approve

    If you receive verification codes or prompts you did not initiate, do not use those codes and do not approve the request. The verification-code guidance explains that unrequested codes can happen when someone is trying to access the account or when information is entered incorrectly, and it points back to securing the account and strengthening sign-in methods.

    Please note that this is a user-to-user forum, so there is no access here to investigate the account directly on the service side, but the steps above are the correct self-service security paths for this situation.

    I hope this helps you fully lock down the account and reduce those unexpected prompts.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".    

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.    

    Was this answer helpful?


  3. AI answer

    2026-04-13T03:49:06.4833333+00:00

    Follow these steps to contain the compromise and harden the account against ongoing attacks:

    1. Review recent sign-in activity
      • For a work or school account, go to the My Account portal → Recent Activity and review each sign-in, including location, app, browser, and operating system.
      • If any successful sign-in is not recognized, immediately change the password again and then go to Security info to update security settings, such as MFA methods and sign-in options.
      • Be aware that IP-based locations can look unfamiliar (for example, mobile traffic routed through another state), so verify device, browser, and app details as well.
    2. Respond to suspicious successful and unsuccessful sign-ins
      • If unfamiliar successful sign-ins are found, treat them as a likely compromise: change the password and update security info.
      • If there are many unsuccessful sign-ins, this can indicate password-guessing or MFA fatigue attempts. Register and enforce strong multi-factor authentication (for example, Microsoft Authenticator with number matching) so that password-only attacks are not sufficient.
      • If any sign-in shows “Additional verification failed, invalid code,” assume the password may already be known to the attacker and change it again, then review and update security info.
    3. Secure the Microsoft account itself
      • If this is a personal Microsoft (Hotmail/Outlook.com) account and there is suspicion that someone accessed it:
        • Check the Recent activity page for unusual sign-ins and mark any that were not performed by the legitimate owner.
        • Follow the guidance in How to recover a hacked or compromised Microsoft account, including:
          1. Run a full antivirus/malware scan on all devices used to access the account before changing passwords.
          2. Change the Microsoft account password using a strong, unique password.
          3. Review account settings such as connected accounts, forwarding, and automatic replies to remove any attacker-added configuration.
    4. Enforce stronger MFA and reduce MFA fatigue risk
      • Keep MFA enabled and ensure only trusted methods are configured in Security info.
      • Remove any unrecognized phone numbers, email addresses, or app-based methods.
      • Do not approve any unexpected MFA prompts. Treat repeated prompts as an attack signal and proceed with password change and security review.
    5. Organizational protocols and escalation
      • For work or school accounts, follow internal incident response procedures:
        • Report the incident to the organization’s security or IT team with timestamps, approximate locations, and screenshots of suspicious sign-ins or MFA prompts.
        • Request that the security team review sign-in logs and conditional access/MFA logs for the account to confirm whether there were successful attacker sign-ins and to identify the source IPs and applications involved.
        • Ask the security team to force sign-out of all active sessions and require re-registration of MFA if necessary.
    6. Ongoing monitoring
      • Continue to monitor Recent Activity / My sign-ins regularly for new suspicious attempts.
      • If new suspicious successful sign-ins appear after remediation, repeat password change, review security info, and coordinate with the security team for deeper investigation.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.