0x3fd607383fd6…3fd60735

ConfirmedSecurity544 vB176 sat/vB3 min decode

Lighter resumes withdrawals after API-key theft incident

Lighter restored withdrawals after roughly 5 million USDC returned through its Guardian safeguard. Ethereum records show a separate 10.39 million USDC left its contract.

Lighter Says Withdrawals Resume After API-Key Theft
WitnessLighter Says Withdrawals Resume After API-Key TheftIgorShubin / pixabay

Outputs

  1. Lighter reported roughly 5 million USDC returned through its Guardian safeguard after withdrawals were paused.

  2. Ethereum records show about 10.39 million USDC left Lighter’s contract at 5:11 a.m. ET.

  3. A Nov. 16 update reflected Lighter’s announcement that deposits and withdrawals had returned to normal.

  4. Lighter said affected accounts reused nonces; its official signing tools and software development kits were not affected.

  5. Public-pool transfers now require a wallet signature, and API-key signatures are no longer public.

Lighter said roughly 5 million USDC had been recovered when its Guardian safeguard paused withdrawals and enabled the Security Council to return the funds.

In a Nov. 16 update, the platform said deposits and withdrawals had returned to normal. The reported recovery came during that pause. It was not a voluntary repayment announced by the attacker.

Two recovery figures, two different outcomes

A separate withdrawal remained outside the reported recovery. At 5:11 a.m. ET, about 10.39 million USDC left Lighter’s contract, according to Ethereum transaction records. The money went to a wallet Lighter later identified as believed to be associated with the attacker. Its latest account did not announce recovery of that earlier withdrawal.

Lighter had previously described the recovery target as funds involved in an additional withdrawal attempt. The Security Council returned roughly 5 million USDC during the Guardian pause. That was a council-led recovery, not a voluntary repayment announced by the attacker.

The two figures need separate treatment. Lighter supplied the 5 million USDC figure, while Ethereum transaction records show the 10.39 million USDC outflow, and the platform has not announced recovery of that earlier transfer. The 5 million USDC figure should not be read as a full offset to the 10.39 million USDC transfer.

How the keys leaked

Lighter attributed the incident to unsafe signing code used by the affected accounts. It said its official signing tools generated nonce values safely, and its official software development kits were not affected.

A nonce is a secret, one-time value used to generate a digital signature. The affected code reused that value, which let the attacker calculate the private API keys from publicly visible signatures, according to Lighter.

Lighter’s assurance was that “its protocol, smart contracts and infrastructure were unaffected.”

The stolen keys could not directly withdraw funds to somebody else’s wallet. The route ran through a public pool. Lighter said a pool created by an account counted as that account’s own sub-account, allowing an API key to transfer funds into it.

The attacker bought pool shares through a separate account. It then moved the trader’s funds into the pool without creating additional shares, redeemed the shares and withdrew the proceeds. Lighter’s account-permission explanation shows how access became withdrawals, without a reported compromise of the protocol or its smart contracts.

What changes for traders?

Lighter has changed two controls:

  • Transfers into a public pool now require a wallet signature, so an API key alone is no longer sufficient.
  • API-key signatures are no longer public.

For traders using custom or third-party signing software, the immediate instruction is to rotate all API keys. If they are unsure whether their code reused a signing nonce, Lighter advised switching to an official signing toolkit.

Lighter is adding more protections:

  • Restrictions on which servers may use a key.
  • Configurable permissions and limits for each key.

Lighter did not specify a completion date for that work. Traders using custom code still need to rotate their keys, even with the new pool-transfer rule in place. The immediate test is the revised pool-transfer rule, which separates API access from wallet authorization while Lighter adds key restrictions and urges traders to rotate exposed credentials.

via cryptonews.net (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,456 articles