The Ledger
LUKSO says email recovery flaw led to theft of about 1.4M LYX
LUKSO says an attacker exploited its email-based recovery backend to take around 1.4 million LYX from about 300 Universal Profiles. The service has been switched off, and the project says it is working on a reimbursement plan.

About 300 profiles affected
LUKSO says an attacker exploited a flaw in its email-based recovery backend to take around 1.4 million LYX from about 300 Universal Profiles. The project’s post-mortem, published November 18, says the attack happened overnight from November 17 to 18.
The attacker took control of the recovery service’s “recovery” profiles, then used them to add the attacker’s own key to affected accounts and move assets out, according to LUKSO.
Recovery service shut down
LUKSO says it found the issue and switched off the email-based recovery system, stopping the attack. The service is being decommissioned while the investigation continues.
The stolen LYX was bridged to Ethereum and swapped through decentralized exchanges, including Uniswap, LUKSO said. LUKSO put the proceeds at roughly 50 ETH, or about $95,000, which is not the same as the market value of the stolen tokens, The Defiant noted; Etherscan showed no bridged LYX remaining in the destination wallet.
Chain and profile contracts not affected, project says
LUKSO says the incident was confined to its email recovery system. It says the LUKSO blockchain and Universal Profile protocols and smart contracts were not affected, and that private keys and recovery phrases were not leaked. Profiles that did not use email-based recovery were not at risk, according to the post.
The company describes a Universal Profile as a smart-contract account controlled by keys and other smart contracts, with permissions assigned to each controller. It says the keys are separate from the account itself, allowing an owner to remove an attacker’s key while retaining the profile and its name, history, followers and remaining assets.
Users told to remove controller keys
LUKSO says shutting down the recovery service prevents new profiles from being affected, but an attacker’s key left on an account could still move tokens and collectibles remaining there. The project directs affected users to check their profiles through its incident-check website and remove the attacker’s controller key.
After that, the post tells users to remove the recovery controller or revoke its “Add Permission” permission, a change from the earlier alert, which asked for both controllers to be removed. LUKSO will publish reimbursement details through its official channels.
The project says it is working on a solution to reimburse affected users’ funds and plans to share details in the coming weeks. It said multiple parties would need to be involved in the process.
Sources
- Original source LUKSO on Medium medium.com
Other pages read
- The Defiant (via Cryptonews) cryptonews.net
- TokenPost tokenpost.com
Related stories
- Curve says fee-burner flaw let attacker take about $38,200
- SGLang flaw could have exposed requests in confidential inference, NEAR AI says
- Ethereum Developers Merge Fix for Glamsterdam Deposit Flaw
- Preprint proposes journal-ordered withdrawal permits for Bitcoin custody
- Keylabs says COLDCARD seed-generation fix holds up in review of shipped firmware