7206fb5e-a

ConfirmedSecurity586 words3 min decode

Email Recovery Flaw Enabled 1.4 Million LYX Profile Thefts at LUKSO

LUKSO says an email-recovery flaw exposed profile controller keys. On-chain records show about 1.5 million bridged LYX reached one collection wallet on Ethereum.

LUKSO Blames Email Recovery Flaw for Profile Thefts
WitnessLUKSO Blames Email Recovery Flaw for Profile TheftsAI-generated

Outputs

  1. LUKSO reported about 1.4 million LYX stolen, worth roughly $330,000 at CoinGecko's Nov. 18 price.

  2. The controller key flagged by LUKSO moved about 200,607 LYX from one Universal Profile.

  3. The collection address received about 1.5 million bridged LYX on Ethereum across 10 receipts.

  4. The identified destination wallet held 52.4225 ETH, valued at about $92,400 on Nov. 18.

  5. LUKSO says holders must remove the attacker key and may either remove one recovery controller or revoke `Add Permission`.

LUKSO said an email-recovery flaw let an attacker install controller keys and take control of affected profiles, with about 1.4 million LYX stolen. The service shutdown prevents new profiles from being affected, but installed attacker keys can still move remaining tokens and collectibles until holders remove them, according to the post-mortem.

LUKSO said the blockchain, Universal Profile protocols and smart contracts remained unaffected, and no private keys or recovery phrases leaked. The email-recovery service is now being decommissioned. Users who did not enable it were never at risk from this incident.

How did the attacker move the funds?

On-chain logs connect the controller key flagged by LUKSO to a transfer of about 200,607 LYX from one Universal Profile into a collection wallet.

According to The Defiant's tally of Etherscan transfer records, the same address received about 1.5 million bridged LYX on Ethereum across ten receipts. That measure captures tokens delivered through the bridge, not a separate account-by-account tally of losses.

Records show repeated exchanges of bridged LYX for wrapped ether, including a Uniswap transaction that sold about 42,845 LYX for 1.23 WETH. Etherscan showed no bridged LYX remaining in that wallet.

The destination wallet identified by LUKSO held 52.4225 ETH, valued by Etherscan at about $92,400 when checked on Nov. 18. Etherscan listed six ordinary incoming ETH transactions, all from the collection address.

LUKSO put the LYX sale proceeds at roughly 50 ETH, or about $95,000. Those proceeds differ from the quoted market value of the stolen tokens.

At CoinGecko's price of roughly $0.236 at 5:24 p.m. ET on Nov. 18, LUKSO's reported 1.4 million LYX would be worth about $330,000. The 1.5 million bridged-LYX receipt total and the 1.4 million stolen-token estimate are not directly comparable because the former measures bridge deliveries rather than holder losses.

What does this change for profile owners?

The earlier alert from The Defiant directed holders to remove the attacker controller first, followed by the malicious recovery controller, and warned that the attacker key might not appear in the controller list.

LUKSO's post-mortem retains that first step but changes the second. Current instructions replace the original requirement to remove both controllers completely:

  • Remove the attacker's controller key first.
  • Then remove the recovery controller or revoke its Add Permission permission.

The revised second step gives owners more flexibility: they may preserve the recovery controller while withdrawing its authority to add permissions, rather than delete the controller outright.

The post-mortem links an incident checker and updated removal instructions. LUKSO says owners can remove the attacker's key and retain the profile, including its history and remaining assets.

Removing the attacker key remains the decisive step for assets still held in affected profiles; revoking the recovery controller's permission alone does not eliminate the installed key's access. The exposure therefore persists until holders complete that removal, even though the project has stopped the service that enabled the original attack path.

LUKSO said it is working on a solution to reimburse affected users' funds and will publish details through its official channels in the coming weeks. The project did not set a payment date or specify reimbursement terms.

With email recovery decommissioned, affected holders remain in a live access window until they remove installed attacker keys; LUKSO expects to publish reimbursement details in the coming weeks, without a payment date or specified terms.

via cryptonews.net (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,574 articles