A MetaMask Chrome Extension user says more than a dozen previously hidden wallet accounts became inaccessible through the interface after updating to version 13.52.0, including imported private-key accounts that cannot be recovered from the wallet’s original Secret Recovery Phrase alone.
The report, filed on October 19 at 01:16:54 UTC as GitHub issue #47159 in MetaMask’s official extension repository, says the entire Hidden accounts section disappeared from the account selector. The issue carries the project’s labels type-bug, needs-triage and regression-prod-13.52.0.
Those labels show that the complaint is in the project’s tracking system, not that MetaMask has confirmed a widespread release defect. The issue was open with no maintainer comments when checked. There is no evidence that the extension deleted private keys, erased blockchain balances or caused a financial loss.
What Did the MetaMask 13.52.0 User Actually Report?
The reporter said the problem appeared after updating the production MetaMask Extension in Google’s Chrome browser on Windows. The Hidden accounts section, which had previously appeared beneath the wallet groups in the account list, was no longer visible anywhere in the selector.
According to the filing, around 12 or more accounts had been hidden manually before the update, many of them added through separate private keys. The user said they could no longer select those addresses, show them again or reach the usual account menu to export private keys. The issue includes screenshots and reproduction instructions.
Importantly, the author did not report a transaction attempting to move assets without approval, a missing on-chain balance or an unexpected change to the main seed phrase. The reported failure concerns account discovery and navigation inside the extension’s user interface.
The original issue also says there is no error code. The account switcher simply lacks the previously available section. That makes it harder to determine whether the extension is still storing the account records but failing to display them, or whether some wallet-state migration changed the metadata used to show hidden accounts.
How Should Hidden Accounts Work in MetaMask?
MetaMask’s current Help Center documentation states that extension users can hide accounts through the three-dot account menu. To restore visibility, they should open the account selector, expand Hidden accounts and choose Show account on the relevant entry.
The help text therefore describes an expected interface that differs from the user’s reported experience. That is meaningful corroboration of the intended feature behavior, not independent proof that version 13.52.0 behaves incorrectly for other customers.
MetaMask allows accounts derived from its primary Secret Recovery Phrase to be generated again from that phrase. Separately imported wallets can originate from a different recovery phrase, a standalone private key or other account material and are not necessarily derivable from the original wallet’s phrase.
The distinction matters because a user who retains only the main recovery phrase may be able to restore their standard accounts after reinstalling, while failing to recover accounts imported from unrelated secrets. MetaMask’s own documentation warns that imported accounts may need their separate phrase or private key to be restored on a new installation.
For some wallet setups associated with supported social-login credentials, account synchronization works differently. The precise backup and recovery path depends on how the wallet was created and the type of account imported, so it would be misleading to claim that every imported account is unrecoverable in every setup.
Why Can an Interface Problem Become a Custody Risk?
Blockchain balances are associated with addresses and signing keys, not with the order in which accounts appear in a browser menu. Hiding an account should not destroy its tokens or transfer custody to another party. But access can still become operationally important when a user cannot find an account’s signing controls or retrieve the independent private key needed to access funds elsewhere.
For example, a self-custody user may see an account’s holdings in a block explorer while being unable to submit a transfer through the extension. If the corresponding key was imported years earlier and never backed up separately, resetting the extension could turn a temporary display problem into a much harder recovery challenge.
That is why a prudent response is not to uninstall MetaMask, reset wallet data, clear browser storage or follow strangers’ recovery instructions before verifying backups and checking official support guidance. The available complaint does not establish which recovery technique will work, and reckless attempts could make the situation worse.
Other wallet software incidents show why the distinction between access and theft matters. DaveFinances previously covered a Ledger Filecoin integration disruption affecting wallet functions, where users’ ability to manage accounts was impaired without evidence that the underlying blockchain or keys had been compromised.
What Should Affected MetaMask Users Do?
Users seeing a similar interface change should record the extension version, browser version, operating system, account type and relevant screenshots without sharing confidential wallet information. They can compare the account selector with MetaMask’s official instructions and watch the public GitHub issue for verified triage or a fix.
Anyone who knows their affected public addresses can verify balances through a trusted block explorer without connecting a wallet to an unfamiliar service. This confirms public on-chain state, but cannot prove what secret material remains available inside the extension.
Users with separate backed-up private keys or recovery phrases have a different recovery situation from those without them. They should not enter secrets into websites or support forms. Scam operators frequently exploit urgent wallet-access problems with fake assistance; a guide to recognizing wallet scams before connecting explains why recovery requests can introduce a second and unrelated security threat.
MetaMask’s public instructions discourage resetting account activity except when its support team advises it. In a case involving allegedly inaccessible imported keys, preserving the current installation and seeking guidance from the official support channel is particularly important.
What Evidence Would Confirm a Production Regression?
The decisive next step would be reproduction by MetaMask maintainers or additional independent reports from users on the same extension release. Developers could then determine whether the regression affects only a particular combination of hidden accounts, imported wallets and grouped account settings, or whether it is more widespread.
A fix would need to restore visibility without compromising key custody. It would also be useful to establish whether account data remained intact throughout the incident, whether previous versions exhibit the behavior, and whether any supported recovery method can restore the hidden imported accounts without destroying locally stored information.
Investors should distinguish the issue from a supply-chain attack or stolen-wallet incident. For comparison, hardware-wallet tampering warnings concern possible compromise of secret material; the MetaMask report at present alleges only that the interface cannot reach accounts that were previously available.
As of the latest reviewed issue state, the report remains an untriaged single-user complaint about version 13.52.0. It justifies close attention because imported keys can create unique recovery risks, but it does not justify claims that MetaMask deleted accounts, lost customer funds or introduced a confirmed platform-wide defect.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574