In a major blow to the decentralized finance (DeFi) ecosystem, GMX, a leading decentralized perpetual exchange, has suffered a $42 million security breach. The attack, which occurred on July 9, 2025, specifically targeted GMX’s GLP liquidity pool, prompting urgent responses from the platform and blockchain security experts.


How the GMX Exploit Happened

On-chain data reveals that the attacker drained significant funds from GMX’s GLP pool, converting stolen assets through multiple steps to obfuscate the trail. Initially, the hacker converted USDC to ETH, then swapped ETH for DAI, and also extracted millions in FRAX, wrapped bitcoin (WBTC), wrapped ether (WETH), and several other tokens.

Nearly $44 million in crypto assets are now being held in the wallet associated with the attacker, as per data tracked by Arkham Intelligence.

While the exact vulnerability has not yet been publicly disclosed, GMX confirmed that the attack affected its Version 1 (V1) protocol. A developer message sent on-chain offered the attacker a 10% white-hat bounty in return for the funds, promising no legal action if the funds are returned within 48 hours.


GMX’s Response and White-Hat Offer

In response to the breach, GMX developers issued a direct message to the exploiter, recognizing the severity of the attack and extending an olive branch in the form of a 10% bounty. This follows the standard DeFi protocol approach aimed at converting exploits into cooperative disclosures.

GMX stated that if 90% of the funds are returned, it will not pursue legal action and will treat the attacker as a white-hat hacker.

The community and GMX stakeholders are awaiting a full post-mortem report, which is expected to detail the vulnerability exploited and provide a recovery roadmap.


Platform Background: What Is GMX?

GMX is a decentralized perpetual futures exchange that enables users to trade major cryptocurrencies like bitcoin, ether, and avalanche with up to 100x leverage. Launched in 2021 on Arbitrum One, the platform has grown into a key player in the DeFi space.

According to GMX’s official statistics:

  • Total trading volume: Over $305.5 billion
  • Open interest: More than $229 million
  • User base: 714,348 traders and liquidity providers

The GLP pool, which was targeted in the exploit, is a central component of the platform, acting as the liquidity source for leveraged trades.

https://www.theblock.co/post/361806/hacker-drains-42-million-from-decentralized-perpetual-exchange-gmx?utm_source=browser&utm_medium=chrome&utm_campaign=notification


Implications for DeFi Security and Trust

This latest exploit underscores the ongoing risks within DeFi protocols, particularly those offering high-leverage trading with decentralized liquidity models. While DeFi offers transparency and non-custodial access, incidents like this remind users of the importance of robust smart contract audits and security architecture.

As the GMX exploit investigation unfolds, it will serve as another critical case study for developers, investors, and regulators evaluating the resilience and future of decentralized exchanges.


In short

  • $42 million stolen from GMX’s GLP pool on July 9, 2025.
  • Hacker swapped funds across USDC, ETH, DAI, FRAX, WBTC, and WETH.
  • GMX offers 10% bounty and legal immunity if funds are returned within 48 hours.
  • The platform has handled over $305B in total volume and supports 100x leverage trading.
  • Full post-mortem expected to clarify exploited vulnerability.

Disclaimer

This content is for informational purposes only and does not constitute financial, investment, or legal advice. Cryptocurrency trading involves risk and may result in financial loss.

logo

blockto.io

info@blockto.io

Blockto.io Copyright © 2025, All rights reserved

News
Rates
Buy
More
We use cookies to personalize content and ads, provide social media features, and analyze our traffic. In accordance with GDPR/AVG and EU cookie regulations, data is processed only with your consent. We may share information about your use of our website with our social media, advertising, and analytics partners, and you can manage or withdraw your consent at any time. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Privacy Policy

At BitxJournal.com, we respect your privacy and are committed to protecting your personal data. This Privacy Policy explains how we collect, process, store, and protect personal information in accordance with the General Data Protection Regulation (GDPR) and AVG (EU privacy legislation).

1. Data Controller

BitxJournal.com acts as the data controller for all personal data processed through this website.

2. Personal Data We Collect

We may collect and process the following categories of data:

Personal Data

  • Name and email address (when you subscribe to newsletters or contact us)

Technical & Usage Data

  • IP address, browser type, operating system

  • Device information

  • Pages visited, referral sources, and interaction data

This data is collected via cookies, log files, and analytics technologies.

3. Legal Basis for Processing

We process personal data only when a lawful basis exists, including:

  • Consent – when you explicitly agree (e.g., cookies, newsletter sign-up)

  • Legitimate interest – to operate, secure, and improve our website

  • Legal obligation – when required by applicable laws

You may withdraw your consent at any time.

4. Purpose of Data Processing

Your data is processed for the following purposes:

  • Operating and maintaining the website

  • Improving content, usability, and performance

  • Sending newsletters or updates (only with consent)

  • Analyzing traffic and user behavior

  • Responding to inquiries or support requests

5. Cookies & Consent Management

We use cookies and similar technologies in compliance with EU Cookie Law.

  • Non-essential cookies are placed only after explicit user consent

  • Users may accept, reject, or manage cookie preferences at any time

  • Consent can be withdrawn without affecting prior lawful processing

Detailed cookie information is available in our Cookie Settings panel.

6. Third-Party Data Processing

We may share limited data with trusted third-party service providers, including:

  • Analytics providers (e.g., Google Analytics)

  • Advertising partners (for personalized or non-personalized ads)

These third parties act as data processors and process data only under contractual obligations compliant with GDPR/AVG.

7. International Data Transfers

Where data is transferred outside the European Economic Area (EEA), we ensure appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) or equivalent legal mechanisms.

8. Data Retention

We retain personal data only for as long as necessary to fulfill the purposes outlined in this policy or as required by law.

9. Data Security

We implement appropriate technical and organizational security measures to protect personal data against unauthorized access, alteration, disclosure, or destruction.

10. Your GDPR Rights

Under GDPR/AVG, you have the right to:

  • Access your personal data

  • Rectify inaccurate or incomplete data

  • Request data erasure (“right to be forgotten”)

  • Restrict or object to processing

  • Data portability

  • Withdraw consent at any time

  • Lodge a complaint with a supervisory authority

11. Changes to This Privacy Policy

We reserve the right to update this Privacy Policy at any time. Any changes will be posted on this page with a revised effective date.

12. Contact Information

For privacy-related inquiries or GDPR requests, contact:

📧 Email: support@blockto.io
🌐 Website: https://blockto.io

Save settings
Cookies settings