rust Wallet Chrome Extension broken after proxy change – wallet data corrupted

[darwinsz]

Hello everyone,

I’m posting here as a last attempt to see if there is any possible recovery path, even if the chances are very low.
I was using the Trust Wallet browser extension (Chrome, Manifest v3) inside a separate browser profile (not incognito tab, but an isolated profile). The wallet was working normally until I changed the proxy used by this browser profile.
After changing the proxy, the Trust Wallet extension started showing an “Oops! An error occurred” screen and no longer loads. Even after reverting
When checking the Chrome DevTools console, I consistently get er

Cannot convert undefined or null to object
Cannot read properties of undefined
Errors inside functions such as getAccountsOfSupportedCoins and `registerWallet

This suggests the extension’s IndexedDB / local storage state may du

Important details:

I do NOT have the seed phrase backe
The wallet was only used on this browser extension, not im
The extension files themselves are intact (manifest, background.js, wasm files, etc.), but the UI crashes before allowing any access.
I have not uninstalled the extension yet, to avoid wiping any remaining local data.

My question is not about breaking encryption or doing anything malicious. I’m simply asking:

👉 Is there any known method, experimental or theoretical, to:

Repair a corrupted Trust Wallet extension state, or
Force the extension to reindex/reload accounts from existing encrypted local data, or
Recover access if the encrypted storage still exists but the UI fails?

I fully understand that without the seed phrase, recovery is usually impossible. I’m posting here only to confirm if there is absolutely no technical path left, or if anyone has ever seen a similar case resolved.

Any insight from developers or experienced users would be appreciated.

Thank you for your time.

[ABCbits]

1. Since you didn't mention anything about customer support, have you tried contacting them for help?
2. If you haven't do it, consider backup all data created Trust Wallet extension. I just tried https://www.w3tutorials.net/blog/chrome-extension-local-storage-how-to-export/ and i can see data for my other browser extension, but i don't know whether this guide also work for Trust wallet extension.

Any insight from developers

FYI Trust Wallet isn't open source. So developer who can help is likely limited to Trust wallet developer, who probably doesn't visit this forum.

[nc50lc]

Any insight from developers or experienced users would be appreciated.

I checked the extension storage and it looks similar to how MetaMask stores its "vault data".
But this is not for certain since it's a closed-source wallet.

If you want to get that data:
You can try to export a copy of it from from Chrome's DevTools' Application tab (Refer to ABCbit's link),
But instead of going directly to "Storage", browse to "Extension Storage->Local" instead, there, you can get the value of your "trust:vault".
It's the value that looks like this (has "data", "iv" and "salt"):

Code:

{"data":"cPdalue...P7lbhU=","iv":"oo58...4L7g==","salt":"L2fFx6...AJbTLmnfQ="}

But the problem is, although there's an available 'vault decryption tool' made by Metamask, it seem to be using a different encryption.
Their open-source Vault Decryptor (GitHub) doesn't work on Trust Wallet's vault data although it's 100% identical.
And Trust Wallet's encryption is not documented (or at least I haven't heard of its documentation)

[Pmalek]

It's too bad that you didn't make at least one backup of your seed phrase when you set up your wallet. Trust Wallet is closed-source, but it's still non-custodial, giving you access to the seeds of your wallets. I assume the same is true for the browser extension as it is for the mobile app. Hopefully, you will learn from this problem and in the future you won't repeat it again and take shortcuts. If you don't manage to recover your wallet, I hope at least that it won't be too expensive of a lesson.

I doubt Trust Wallet's customer support can be of much help, but I would still contact them and ask. Tell them about the error messages you see and what you did to cause them. Also, google those error messages to check if there are people who have already reported similar problems. Maybe there is a solution or tip there somewhere on how to fix it.

[BattleDog]

If you don't have the seed phrase, your only real lifeline is that the encrypted vault is still sitting in the Chrome profile somewhere and the UI is just face-planting before it can render.

So treat that browser profile like evidence in a crime show: make a full copy of the whole profile directory first, before you "try one more thing" and Chrome helpfully garbage-collects something.

Changing a proxy didn't magically delete keys, but it can absolutely make an extension crash if it expects to fetch coin lists/config and gets a weird network state, and then the front-end throws those "undefined" errors you're seeing.

[BitMaxz]

I don't know why some people are still using the Trust Wallet extension despite the recent incident in which some Trust Wallet users lost $6M+. It was just recent issue last month and maybe this might be the reason why your wallet data or the extension become corrupted.

I am using Trust Wallet, but I only use their mobile version to receive airdrops.

I think you need some help from Trust Wallet support since the only way that I know to recover your wallet is by using seed backup. If you don't have a seed backup, the chances of recovering your wallet are pretty slim.

I did some research and found this one below; it might be helpful, but make sure to make a backup of the extension data folder and make sure to run the decryptor or the extractor offline for safety purposes. Based on the guide provided from that link, it could generate the bip39 seed or extract a base58 private key. Let's see if this one will work on Trust Wallet.

- https://www.binance.com/en/square/post/21131027767362