# Lighter Perps (zkLighter) API Key Compromise: Lighter perpetual futures platform reportedly lost $10M through compromised API keys
Source page: https://vaultx.llc/hacks/lighter-perps-exploit-2026-11 · VaultX incident report by Sentinel · first published 2026-11-18, updated 2026-11-19
- Date: 2026-11-16
- Reported loss: $10.0M (reported $10M by DeFiLlama, not independently confirmed)
- Attribution: unknown
- Chains: zkSync Era
- Status: developing
- Severity: 62/100
- Response score: 35/100 (No public response documented within 2 days; lack of transparency and user communication)
On November 16, 2026, Lighter (zkLighter), a decentralized perpetual futures trading protocol on zkSync Era, reportedly suffered a $10 million loss through compromised API keys, according to DeFiLlama. The incident involved unauthorized access to administrative credentials rather than a smart contract vulnerability. Details remain limited as the incident is very recent and full disclosure has not yet occurred. The attack vector and fund destination are not yet publicly documented.

**What happened**
According to DeFiLlama, Lighter (also known as zkLighter), a decentralized perpetual futures trading platform built on zkSync Era, lost approximately $10 million in a security incident on November 16, 2026. The breach was characterized as an API key compromise rather than a smart contract exploit.
The attacker reportedly gained unauthorized access to Lighter's API credentials, which provided administrative or operational control over platform functions. This type of access could potentially allow manipulation of orders, unauthorized fund movements, or changes to system parameters.
As of November 18, 2026, detailed technical information about the exploit mechanism, affected user funds, and the platform's response remains limited. The incident is still developing and full post-mortem analysis has not been published.

**How it worked**
The attack vector involved compromised API keys that granted the attacker elevated access to Lighter's platform infrastructure. Unlike smart contract exploits that leverage code vulnerabilities, API key compromises are operational security failures where authentication credentials are stolen, leaked, or otherwise obtained by unauthorized parties. Once in possession of valid API keys with sufficient privileges, an attacker can issue commands as if they were legitimate system administrators, potentially including fund withdrawals, trading parameter modifications, or order book manipulation. The specific method by which the keys were compromised—whether through phishing, insider threat, infrastructure breach, or other means—has not been publicly disclosed.

**Where the money went**
Fund destination and laundering methods not yet publicly disclosed. No information available on frozen or recovered amounts.

**The response**
No public response or post-mortem from Lighter has been documented as of November 18, 2026. The platform's communication with affected users and remediation plans remain unknown.

**Impact**
Impact on users and markets not yet fully documented. The $10 million loss represents a significant security incident for a decentralized perpetuals platform. User fund status and trading disruption details have not been disclosed.

**Timeline**
- 2026-11-16 API key compromise incident occurs on Lighter platform, reportedly resulting in $10M loss
- 2026-11-16 DeFiLlama reports the incident with estimated $10M in losses

**How to protect yourself**
- API key management is a critical security concern even for decentralized protocols; keys with administrative privileges must be secured with hardware security modules, multi-signature requirements, and strict access controls
- Users should evaluate the operational security practices of DeFi platforms, not just smart contract audits; centralized API access points create single points of failure
- Platforms should implement monitoring and alerting for unusual API activity, rate limiting, and IP whitelisting to detect and prevent unauthorized access
- Incident response plans should include immediate public communication; two-day silence after a $10M loss erodes user trust and prevents others from taking protective action

**Still unknown**
- How the API keys were compromised (phishing, infrastructure breach, insider threat, or other vector)
- Which specific assets were stolen and their breakdown
- Exact wallet addresses involved in the theft and fund movement
- Whether user funds or protocol treasury was affected
- What percentage of total value locked was lost
- Whether any funds have been frozen or recovered
- Lighter's official statement and remediation plan
- Whether affected users will be compensated
- What security measures were in place before the incident
- Whether law enforcement has been contacted

**Sources**
- DeFiLlama Hacks Database https://defillama.com/hacks
- defillama.com https://defillama.com/
- rekt.news https://rekt.news/

---
VaultX: free crypto news and intelligence, https://vaultx.llc
