f9a4d833-7
LUKSO Links Theft of 1.4M LYX to Email Recovery Flaw
LUKSO says a flaw in its email recovery process exposed about 300 profiles and roughly 1.4 million LYX was stolen. Email recovery is being retired; affected holders still face manual key cleanup.

Outputs
Roughly 1.4 million LYX stolen via email recovery flaw
About 300 user profiles affected
LUKSO is retiring email recovery entirely
Affected holders must still manually remove the attacker's key from their profiles
LUKSO has attributed the theft of roughly 1.4 million LYX to a flaw in its email recovery process, an incident that exposed about 300 user profiles on the network. The project disclosed the figures and the root cause in its statement on the incident, and its response runs on two separate tracks: retiring the email recovery feature outright, and requiring affected holders to remove the attacker's key from compromised profiles themselves.
The distinction between those two tracks matters for practitioners. Retiring email recovery addresses the mechanism LUKSO linked to the thefts going forward, but it does nothing for profiles that were already hit. Holders whose profiles were affected still need to take a separate, concrete step: removing the attacker's key. The cleanup burden sits with users, not with the protocol.
What does this change for affected holders?
For the roughly 300 profiles identified in the incident, the operational priority is explicit. An attacker's key remains attached to compromised profiles until the holder removes it, which means the exposure does not end with LUKSO's decision to retire the vulnerable feature. Affected holders who do not act retain a live attacker-controlled key within their profile's permission structure.
The scale is material relative to the affected population. Around 1.4 million LYX stolen across roughly 300 profiles works out to an average of roughly 4,700 LYX per affected profile, assuming an even distribution — actual losses per holder will vary with balances and the attacker's targeting. Roughly one in every hundred of the network's widely cited profile base of about 30,000 Universal Profiles was exposed, a narrow slice of the ecosystem but a concentrated one for those inside it.
What does retiring email recovery address?
The structural fix and the remediation task operate at different levels. Email recovery, as a feature, allowed profile recovery flows tied to an email-based mechanism; LUKSO connected that mechanism to the thefts. By retiring it, the project removes the vulnerable recovery path from its architecture entirely rather than patching it.
That is a deletion, not a repair. It prevents recurrence through the same vector but leaves the existing compromise unresolved. The protocol-level change and the profile-level cleanup are therefore complementary rather than interchangeable, and LUKSO's disclosure frames them as such: one changes the recovery process, the other concerns profiles already affected.
The lesson for account-recovery design
For teams building social recovery or delegated recovery into smart account systems, the incident is a case study in how recovery surfaces become attack surfaces. A recovery mechanism is only as strong as the weakest identity check behind it, and an email-linked flow inherits every weakness of email as an identity layer. LUKSO's decision to retire the feature rather than harden it signals a judgment that the trade-off was not worth maintaining.
The immediate deadline facing affected holders is their own: removing the attacker's key is a manual step that remains outstanding until each holder completes it, and the project's disclosure gives no indication it will be performed on users' behalf.
via tokenpost.com (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,574 articles