[Bug]: Deleting metamask over different Chrome profiles

[uwenohg]

Describe the bug

I would like to report a potential issue related to the use of MetaMask in Google Chrome.

When Chrome's synchronization for extensions is enabled, deleting the MetaMask extension in one synchronized profile can result in it being removed from all other synchronized profiles.

This behavior poses a significant risk, as users who have not securely backed up their seed phrase or private keys could lose access to their wallets permanently. Many users may not be aware of the implications of Chrome's extension sync functionality.

To address this, it might be helpful if MetaMask users were informed about this behavior, for example:

Displaying a warning during the setup process in Chrome.
Recommending that users disable extension synchronization in Chrome when using MetaMask.
Thank you for your dedication to creating one of the best wallet solutions available!

I am conscent, this is firstly a Chrome issue, but I thought you should know.
Best regards,
Uwe

Expected behavior

Independent Management of Extensions Across Profiles
What should happen: If a user deletes or modifies the MetaMask extension in one Chrome profile, it should not automatically impact other profiles, even if they are synchronized.
Why: Each Chrome profile often represents a separate user or use case. Users expect extensions and data in each profile to be managed independently unless explicitly linked.

Screenshots/Recordings

No response

Steps to reproduce

Steps:
Set up MetaMask in Profile A:

Open Chrome Profile A.
Install the MetaMask extension from the Chrome Web Store.
Complete the setup (import a wallet or create a new one).
Enable Synchronization:

In Profile A, go to Settings > Sync and Google Services > Manage What You Sync.
Ensure Extensions is enabled for synchronization.
Verify Synchronization in Profile B:

Open Chrome Profile B (also synchronized with the same Google account).
Check that the MetaMask extension is automatically installed in this profile as a result of synchronization.
Delete MetaMask in Profile A:

Go to Chrome Menu > More Tools > Extensions in Profile A.
Locate MetaMask and click Remove.
Confirm the removal.
Observe the Result in Profile B:

Switch to Chrome Profile B.
Check if the MetaMask extension is still present.
You will notice that MetaMask is also removed in Profile B, even though you only intended to remove it from Profile A.
Expected Result:
The MetaMask extension should remain installed and unaffected in Profile B, even if it is deleted in Profile A.
Actual Result:
Deleting MetaMask in Profile A also removes it from Profile B due to synchronization of extensions.
Key Observations:
The removal happens automatically without any explicit warning or prompt.
If the user does not have a backup (Seed Phrase or private keys), they may permanently lose access to their MetaMask wallet.

Error messages or log output

N/A

Detection stage

In production (default)

Version

12.9.3

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[DanielTech21]

Hello @uwenohg

Thank you for raising this issue with us.

Our team will review it and get back to you.

Thank you.

[gauthierpetetin]

Hi @uwenohg , thanks for your suggestion here but unfortunately there's nothing we can do upon deletion of the Extension. Even if we did show a message to warn users, it would be upon deletion, so harm would already be done.

Instead of warning users in-app that they shall be cautious before deleting their Extension, we currently encourage users to backup their SRP, as it prevents against a wider range of issues.