0x528a8b91528a…528a8b8e
Suspected Lighter Attacker Routed $15.5M Through Hyperliquid
0xTria says exposed Lighter API keys enabled a $15.5 million theft through a signature-free pool route, followed by reported Monero purchases on Hyperliquid.

About $15.5 million was stolen after API keys for two Lighter market makers were exposed, according to the account 0xTria. The account said: "API keys for two Lighter market makers were exposed and about $15.5 million was stolen."
Lighter is a trading platform. The account attributed the loss to compromised market-maker access, not a conventional withdrawal credential, but the report did not include transaction hashes, contract addresses or a detailed timeline.
How could exposed API keys move funds without withdrawal rights?
According to 0xTria, the exposed API keys could not directly withdraw funds. Instead, the route reportedly relied on accounts under a shared L1 address, which could transfer funds between themselves without a signature.
That distinction changes the risk calculation. Exposed credentials did not need withdrawal authority if the shared-address arrangement already permitted signature-free transfers between accounts.
The source does not explain how the attacker obtained the keys, why the affected accounts shared the L1 address, or whether Lighter has revoked the credentials. It also does not say whether other users had exposure to the same route. The reported route was an internal-transfer failure, not a conventional withdrawal hack.
What was the public pool used for?
0xTria described a sequence that reportedly began with the attacker closing victims' positions. Those actions created a public pool with a 0% fee, according to the account.
The attacker then spent about $10,000 to acquire a 99.99% share in that pool. The purchase amount equals roughly 0.065% of the reported $15.5 million loss, illustrating how little capital the account said was needed to gain majority control.
If the stated ownership share was accurate, the attacker would have controlled nearly the entire pool while other participants held a combined 0.01%. That concentration is material, but the source supplies no contract address or code with which to verify the arrangement.
After gaining the share, the attacker moved USDC through the pool in batches of about $1 million and redeemed it. The account did not specify whether the $1 million batches covered the whole loss, came from every affected market maker, or included other funds. A $10,000 pool purchase reportedly gave the attacker control over the route for moving roughly $1 million chunks of USDC.
Where did the proceeds go next?
Funds tied to the Lighter incident moved into Hyperliquid and funded Monero purchases, according to 0xTria. The account presents Hyperliquid as a downstream trading venue, rather than the place where the original loss occurred.
The report gives no quantity of Monero purchased, no execution prices and no addresses for the reported transfers. It therefore cannot establish how much of the reported $15.5 million reached Hyperliquid, or whether the attacker still controls any resulting XMR.
The absence of a Monero amount also limits any assessment of exposure after the purchase. A transfer into a trading venue does not, by itself, demonstrate liquidation, withdrawal or final disposition of the assets.
The source identifies no law-enforcement investigation, court filing, regulatory action, asset freeze or recovery. It does not say whether Lighter reimbursed affected market makers or whether any stolen assets have been recovered. The destination is known, but the size, status and recoverability of the converted holdings remain unspecified.
What must Lighter establish next?
A complete account would need to show which API keys were exposed, how shared L1 addresses authorize internal transfers, and whether the signature-free route still works. The source does not report any of those disclosures.
For market makers, the relevant issue is control over execution and settlement paths, not merely the ability to block withdrawals. The described sequence links compromised API access, position closure, pool ownership and redemption within one reported route.
The source does not establish whether other platforms share the same address design. It also does not identify the two affected market makers, so sector-wide conclusions about comparable exposures would go beyond the available evidence. The next checkpoint is Lighter's incident report and key-revocation record, which would show whether the signature-free transfer route has been closed and when.
via tokenpost.com (Source)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles