“This extension is not listed in the Chrome Web Store”
H1 is the Chrome string. The fix is not a registry tweak — it is the official listing ID and a hash if you still have a .crx you should not load.
Security Guides · 6 min · Updated Aug 2026 · Expert
When Chrome says the extension is not listed in the Chrome Web Store, you are sideloading or the listing was pulled. That is not how you install Phantom, Rabby, or MetaMask.
Do not enable Developer mode to “make it work.” Open the vendor site, confirm the official ID, and only then hash a leftover .crx if you are doing forensics.
Do this now
- Leave Developer-mode unpacked folders. Remove the unpacked wallet. Official wallets ship as store listings, not Discord zips.
- Install from the vendor’s store URL. Phantom ID
bfnaelmomeimhlpmgjnjophhpkkoljpais the example preset on this page. MetaMask and Rabby have their own IDs on the ID guide. - Hash a leftover .crx only to identify it. Drop it into the verifier. A catalog match still does not mean Chrome wants you to Load unpacked. Prefer the store.
Chrome message → cause → fix
| Message | Cause | Fix |
|---|---|---|
| Not listed in the Chrome Web Store | Sideload / unpacked / removed item | Install via vendor store URL + official ID |
| This extension may have been corrupted | Altered files on disk | Remove; reinstall from store; do not restore from zip |
| CRX_HEADER_INVALID | Not a valid CRX | CRX_HEADER_INVALID |
What this error cannot mean
It cannot mean “Chrome is broken, sideload the real wallet.” Official MetaMask/Phantom/Rabby are listed. If they were not, you would hear it from the vendor site, not from a pop-up.
WalletGuard cannot push an extension into Chrome.
Frequently asked questions
Why does Chrome say my wallet extension is not listed?
You loaded it unpacked, from a .crx, or the item was removed from the store. Real Phantom/MetaMask/Rabby listings are in the store. Use the vendor’s official URL.
Can I bypass this with Developer mode?
You can. You should not, for a custody wallet, unless you are a developer loading your own code. Users install from the store ID.
Does a matching SHA-256 fix the Chrome error?
No. Chrome is refusing a distribution channel. Hashing identifies a file; it does not list the extension in the store.