Blockchain
LUKSO Blames Email Recovery Flaw for Profile Thefts
Publication: The Defiant
Author: The Defiant
Source published: 19/11/2026, 01:13:31 UTC
Briefing created: 19/11/2026, 01:28:45 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 19/11/2026, 01:27:25 UTC.
Briefings
A project named LUKSO reported approximately 300 accounts were compromised, resulting in a loss of 1.4 million LYX tokens. The project announced the retirement of email recovery mechanisms, though affected users must manually remove attacker keys. This incident occurred in November 2026, with the project citing a specific flaw in the email recovery system as the cause. The source material does not specify the number of unique accounts lost, only the total number of accounts affected, nor does it provide details on the specific date of the flaw's discovery or the project's current operational status beyond the November 2026 timeframe.
Key points
- LUKSO reported approximately 300 accounts were compromised, resulting in a loss of 1.4 million LYX tokens.
- The project announced the retirement of email recovery mechanisms, though affected users must manually remove attacker keys.
Context
This incident highlights a critical vulnerability in cryptocurrency project security, specifically regarding email-based authentication methods. The loss of 1.4 million LYX tokens represents a significant financial impact for the project's ecosystem, necessitating immediate security upgrades and user education.
Limitations
The evidence does not specify the number of unique accounts lost, only the total number of accounts affected. It does not provide details on the specific date of the flaw's discovery or the project's current operational status beyond the November 2026 timeframe. The source material lacks information on the specific technical nature of the flaw or the project's long-term recovery plan.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 19/11/2026, 01:28:45 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeibo3u5nmxvri4oi4f7rqhgdskmf5baeu6bfhzn4fzinctoc5xu4fu