Trade.xyz Restores GitBook Docs After Unauthorized Activity, Keeps Link Warning
Trade.xyz said it restored its GitBook documentation on November 2 after detecting unauthorized activity that morning, and told users to avoid links in the docs while an investigation continues. The company said user funds, its trading platform and on-chain settlement on Hyperliquid were not affected.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
What Trade.xyz Reported
Trade.xyz said on November 2 that unauthorized activity had affected its GitBook documentation earlier that morning, and that it restored the previous version of the docs by 9:15 a.m. ET. The company has not described what the activity involved, how access was obtained, or how long altered material was live before the rollback.
The company's advisory is the most immediate instruction. Even with the docs restored, Trade.xyz is asking users not to click any links within the documentation while its review continues. The warning covers all links in the documentation rather than specific pages, and no malicious destination addresses were published.
Scope of the Incident
Trade.xyz said user funds, the trading platform and on-chain settlement were not affected, and that trades continue to settle on Hyperliquid. Because the platform is non-custodial, it does not hold user assets, which limits the direct exposure from a problem on a documentation site. No wallet drains or compromised funds tied to the incident have been reported.
The sources differ on how much the company has disclosed about the cause. One account describes the incident as affecting the docs without naming any intrusion path. The other states explicitly that the announcement did not identify a compromised administrator account, stolen credentials or a vulnerability in GitBook, and did not attribute the incident to a failure on GitBook's platform. Neither account reports a loss figure, an affected-user count or an attacker address, and the company has not said when further findings will be published.
Context: Recent Frontend Incidents
The documentation notice follows a separate set of website incidents on October 31, when Blockaid flagged Flap, Kintsu and ten other projects for compromised frontends, some of which were serving the Step Drainer toolkit. Flap confirmed a DNS hijack that redirected visitors from its official domain. Trade.xyz's announcement does not name Step Drainer or link its GitBook incident to those attacks, and no source establishes a connection.
Trade.xyz's Regulated Market Plans
Four days before the docs notice, Trade.xyz announced an agreement with ICE, owner of the New York Stock Exchange, to bring Hyperliquid-based perpetual futures into a regulated U.S. market. The company said its existing markets had processed more than $650 billion in cumulative volume in just over a year. ICE's October 29 announcement said the business would require regulatory approvals, including permission for leveraged trading, and that ICE would operate the regulated markets exclusively and make a strategic investment in Trade.xyz. The agreement does not open the existing offshore markets to U.S. traders.
Open Questions
Users have not yet been told what the unauthorized activity was, how it happened, or what controls are being added to prevent a repeat. Until Trade.xyz publishes its findings, the scope of the incident and the duration of any altered content remain unconfirmed.
Why It Matters
For Traders
Trade.xyz says trades are still settling on Hyperliquid, but users who opened its docs on November 2 should avoid clicking links until the company completes its review.
For Investors
The incident is limited to documentation and not settlement, but repeated frontend and docs incidents across DeFi raise the operational risk of front-facing infrastructure.
For Builders
Protocols hosting public docs on third-party platforms should review access controls and link integrity, since a documentation compromise can still expose users even when funds are unaffected.
This article is for information only and is not financial advice. Read the full disclaimer.
