Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unable to recover Vault to decrypt using provided instructions #29417

Open
v0dev opened this issue Dec 23, 2024 · 4 comments
Open

[Bug]: Unable to recover Vault to decrypt using provided instructions #29417

v0dev opened this issue Dec 23, 2024 · 4 comments
Labels
external-contributor INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. regression-prod-12.6.2 Regression bug that was found in production in release 12.6.2 type-bug

Comments

@v0dev
Copy link

v0dev commented Dec 23, 2024

Describe the bug

I recently updated the Metamask Extension on Firefox to the latest version, this resulted in an infinite loop (#29416), I want to recover the vault file and any other data that can be recovered to get the wallets back (by trying reinstall of Metamask).
When trying the guide at: https://support.metamask.io/managing-my-wallet/secret-recovery-phrase-and-private-keys/how-to-recover-your-secret-recovery-phrase/ , to recover the Vault , I get the error below:

Uncaught Error: LavaMoat - property "chrome" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
[runtime-lavamoat.js:13190:11]

Is there any other way to recover the Vault Data (through extension debug I am able to view the extension data but not sure if that contains all the things required) ?

Expected behavior

Show the encrypted vault data for recovery.

Screenshots/Recordings

No response

Steps to reproduce

  1. Open the moz-extension://../home.html for the extension
  2. Enter the command

Error messages or log output

Uncaught Error: LavaMoat - property "chrome" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
[runtime-lavamoat.js:13190:11]

Detection stage

In production (default)

Version

12.6.2

Build type

None

Browser

Firefox

Operating system

Windows

Hardware wallet

No response

Severity

No response

@v0dev v0dev added the type-bug label Dec 23, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Dec 23, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Dec 23, 2024
@metamaskbot metamaskbot added external-contributor regression-prod-12.6.2 Regression bug that was found in production in release 12.6.2 labels Dec 23, 2024
@Ellabell-dr

This comment has been minimized.

@v0dev
Copy link
Author

v0dev commented Dec 23, 2024

#29417 (comment) : This is a scam attempt, please remove/ignore it!

@v0dev
Copy link
Author

v0dev commented Dec 23, 2024

I was able to view the details I needed by inspecting the extension through Firefox -> Debug Addons -> Inspect Metamask , then going to the storage Inspector.

The details can be found under Extension Storage -> data , the Vault detail is stored under KeyringController, the account details (name, keyring type) are stored under AccountsController, I was trying to write a simple JS snippet to extract all the details for the accounts but LavaMoat causes the same issue there as well.

The Documentation should be updated at: https://support.metamask.io/managing-my-wallet/secret-recovery-phrase-and-private-keys/how-to-recover-your-secret-recovery-phrase/ for Firefox so users can easily just copy paste the vault's value instead of going through console if LavaMoat configuration remains the same.

@seaona
Copy link
Contributor

seaona commented Dec 23, 2024

hi there @v0dev 👋 thank you for your report! Indeed there seems to be an issue with the documentation. Glad to hear that you managed to find it :) The alternative command you can use in the console is this one: await stateHooks.getPersistedState().
We'll try to get the documentation fixed soon 🙏

@metamaskbot metamaskbot added the INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. label Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external-contributor INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. regression-prod-12.6.2 Regression bug that was found in production in release 12.6.2 type-bug
Projects
Status: To be fixed
Status: To be fixed
Development

No branches or pull requests

4 participants