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

  1. Leave Developer-mode unpacked folders. Remove the unpacked wallet. Official wallets ship as store listings, not Discord zips.
  2. Install from the vendor’s store URL. Phantom ID bfnaelmomeimhlpmgjnjophhpkkoljpa is the example preset on this page. MetaMask and Rabby have their own IDs on the ID guide.
  3. 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

MessageCauseFix
Not listed in the Chrome Web StoreSideload / unpacked / removed itemInstall via vendor store URL + official ID
This extension may have been corruptedAltered files on diskRemove; reinstall from store; do not restore from zip
CRX_HEADER_INVALIDNot a valid CRXCRX_HEADER_INVALID
Enterprise policy can pin extensions. A phishing site telling you to disable that policy to install “Phantom” is not IT.

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.

Live artifact · preset phantom_chrome

Catalog hash loads from WalletGuard’s wallet database. Confirm the same string on the developer’s signed release before you install.

Hash this file in the browser

Nothing is uploaded. Web Crypto SHA-256 stays on this device.

·
SHA-256

Compare to the catalog hash

This page pre-selects phantom_chrome. Switch wallets if you grabbed a different build.

Preset hash: loads from catalog

No file selected yet.

Open the full verifier with this preset →

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.