The decentralized exchange Lighter has faced a security incident that forced the project team to temporarily suspend withdrawals and the creation of liquidity pools. Such measures are standard practice for responding to threats, allowing potential risks to be contained before the circumstances are fully clarified.

According to preliminary estimates by blockchain analysts, the damage from the attack could amount to about $15.5 million. The suspected vector of compromise is the hacking of API keys belonging to two market makers working with the platform. This indicates that the attackers did not act through a vulnerability in the smart contract itself, but through external access points to the infrastructure.

Protocol or Perimeter?

Lighter representatives lean toward the version that the attack affected the external perimeter of interaction with the platform rather than the core of the protocol. At present, the team is conducting its own investigation and has not officially confirmed the exact amount of losses. This scenario highlights the continued vulnerability of the DeFi ecosystem, where even with a robust contract architecture, integrations and third-party access keys remain the weak link.

The Lighter incident fits into a broader trend: in 2025, a significant portion of losses in DeFi is linked not to code exploits but to the compromise of private keys, API access, and the operational infrastructure of market makers. For traders and liquidity providers, this is a signal of the need to revise key management policies and strengthen access controls.

Cryptalist Analysis: The suspension of withdrawals on Lighter demonstrates the maturity of the team's response, but at the same time exposes a systemic problem in the DeFi sector — the concentration of risk at points of integration with external counterparties. The market will have to assess how quickly the platform restores trust and discloses the details of the incident; in the short term, increased investor attention to API security standards and key management at DEX platforms is likely.