What happened
Polkadot urged Fearless Wallet users to create new keys after reports of private-key leakage.
Why it matters
If confirmed, users of the affected extension may need to react to the risk of key compromise; the source description indicates coverage of 6 000 users.
Polkadot warned Fearless Wallet users after a private-key leak and urged holders to generate new keys and transfer funds. This was reported by The Defiant.
In the accessible source description, Chrome continued to show the affected extension version, used by 6 000 people. There is no data in the package about the number of compromised wallets or funds stolen.
The material is based on a single independent report and metadata, not on the full text or a confirmation from Polkadot. Therefore, the scope of the incident and its technical details remain unclear.
Confirmed facts
- The Defiant reported that Polkadot warned Fearless Wallet users after a private-key leak.
- Users were advised to create new keys and transfer funds.
- The source description noted that Chrome continued to display the affected extension version, which had 6 000 users.
- There is no data in the package about the number of stolen funds or compromised wallets.
Context
The Defiant source was published on 21 October 2026 year. The evidentiary basis is limited to metadata and a single independent source; there is no primary Polkadot statement in the package.
What remains unknown
- Did Polkadot confirm the private-key leak in an official statement?
- Which Fearless Wallet version was affected and when was the issue resolved?
- How many wallets and funds were actually at risk?
- Has the affected extension version been removed from the Chrome Web Store?
Editorial context
Confidence: medium
A likely consequence is that users of the affected extension version will need to replace keys if the warning is confirmed. The next observable signal will be official clarification by Polkadot or data on removal of the extension version from Chrome. Substantial uncertainty remains due to the absence of a primary statement and full technical information.