Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
April 1, 2026, Drift Protocol, a decentralized futures trading platform on the Solana blockchain, suffered a major security breach resulting in the loss of approximately $285 million. The attack exploited weaknesses in Drift’s administrative governance, specifically targeting the multisignature keys controlling critical operations such as price oracles, vault withdrawals, and collateral management. Once the attackers gained partial control, they manipulated internal mechanisms, bypassed safety protocols, and rapidly drained user funds.
Unlike traditional smart contract bugs, this exploit combined social engineering with technical manipulation of Solana features, such as durable nonces, allowing pre-signed malicious transactions to execute without standard timeouts. Blockchain intelligence firms have linked the attack to North Korean‑affiliated threat actors, consistent with patterns seen in prior state-sponsored cryptocurrency thefts.
The immediate impact was severe: Drift’s total value locked fell from around $550 million to under $300 million, the native DRIFT token lost significant value, and deposit and withdrawal functions were suspended to contain damage.
The hack highlights systemic risks in DeFi governance. Even decentralized platforms can have critical single points of failure if multisig groups are too small or lack timelocks. The incident underscores the need for stronger administrative safeguards, transparent operational procedures, and risk awareness among users and developers to prevent similar breaches in