Random name is displayed as me in the suggested contacts list

Stephen Kong 25 Reputation points
2026-08-31T11:19:35.6933333+00:00

I was sending myself an email and under my suggested contact is a random name "Omer Maggio", never heard of this name before. Not sure if I have been hacked.

I have:

Updated my password

Searched my contact list for this name

Added my own contact under my correct name

Checked and reset my name in "your info"

Turned off the "suggested people function"

Not sure what else to do, can anyone help please?

Stephen

Outlook | Web | Outlook.com | Account management, security, and privacy
0 comments
Answer accepted by question author
Hornblower409 14,690 Reputation points
2026-09-01T11:14:53.2966667+00:00

@Stephen Kong said

Added my own contact under my correct name
Turned off the "suggested people function"

You have already done the steps that normally fix this kind of problem. So I'm not sure what else to suggest.

1 -- Did you follow instructions like this to Clear and Disable the Suggested People/Autocomplete cache?

See the Answer by "Hornblower409 May 1 2026" at
https://learn.microsoft.com/en-us/answers/questions/5871874/manually-removing-an-email-address-from-the-sugges?orderby=newest&page=1#answers

2 -- If you do Step #1 of these instructions (Export your Suggested People), is it really empty?

3 -- Are you in a MS 365 Corporate environment? In that environment Outlook can pull suggested people from other sources.

4 -- You tagged your Question as Outlook | Web | but are you actually using an Outlook Client? e.g. New Outlook for Windows, Classic Outlook?

https://support.microsoft.com/en-us/office/what-version-of-outlook-do-i-have-b3a9568c-edb5-42b9-9825-d48d82b2257c

Was this answer helpful?

2 people found this answer helpful.

1 additional answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-08-31T11:19:54.2833333+00:00

    This usually points to a bad suggested-recipient entry rather than a hacked account, especially since the password was already changed and the name is only appearing in the suggestion list.

    Since the contact list was already checked and the account name was already corrected, the next useful steps are:

    1. Remove the bad suggestion directly from the compose list.
      • Start a new email.
      • In the To field, begin typing the address.
      • When the incorrect suggested contact appears, select the X next to it to hide/remove it.
    2. If the entry keeps returning, clear the stored suggested-contact data for the account.
      • For a personal Microsoft account, go to the Privacy page for the account.
      • Under Privacy settings in our products, select Expanded people suggestions.
      • Turn the toggle Off.
      • In Outlook on the web/classic Outlook guidance, this is also described as going to Empower your productivity > People suggestions and turning it Off.
    3. If using a work or school account instead of a personal Microsoft account:
      • Go to Settings & Privacy for the account.
      • Open Privacy.
      • Under Data options, expand Manage contact suggestions and discovery or Manage Contact Search.
      • Turn off captured/discovered contacts and clear or reset the stored data.
    4. If the hidden contact needs to be restored later, sending to the full address again or replying to an older message can unhide it after about 24 hours.

    Important details:

    • Suggested contacts are generated from personal contacts, organization contacts, and addresses previously used in messages.
    • Saved personal contacts can still appear in suggestions unless that contact is deleted.
    • Organization directory contacts can still appear unless removed by the administrator.
    • Hiding a suggestion removes it from Microsoft 365 product suggestions such as Outlook and Teams.
    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.