Trade.xyz restores GitBook docs after unauthorized activity, warns users off links
- Published
- Updated
- Since then
- 4 new reports
- Also mentions
- HYPE
Trade.xyz said it detected unauthorized activity on the GitBook pages hosting its documentation and told users not to click links there while it investigated. It later restored the docs after identifying the issue on Nov. 2, and GitBook separately said attackers accessed infrastructure credentials in an AI-assisted breach and that it shut down and reset tokens.
Key claims & sources
What it means
GitBook is the documentation host used by a large share of crypto projects, including Trade.xyz, which runs stock, index and commodity perpetual futures on Hyperliquid. Attackers have repeatedly targeted project documentation and Discord channels in past years to insert phishing links that mimic legitimate interfaces, since these pages carry user trust but often sit outside a project's own security perimeter. GitBook's own infrastructure, not just a single client's content, was compromised in this case.
Traders and developers who rely on Trade.xyz's docs for API references or contract addresses had to treat every link there as hostile for roughly a day, until the previous version was restored at 9:15 a.m. ET on November 2. GitBook's response went further: it shut down affected systems and reset tokens, forcing any team using its platform to rotate credentials, not just Trade.xyz. That cost falls on documentation teams across the industry, regardless of whether their own content was altered.
A breach in a shared documentation host exposes a weak point that sits outside any single project's control: users assume a docs page is safe because the protocol behind it is audited, but the hosting layer rarely gets the same scrutiny. GitBook's disclosure that the intrusion was AI-assisted adds a newer variable to an old problem, phishing through trusted-looking links, without changing the basic lesson that supply-chain dependencies carry risk even when the underlying protocol is sound.
The open question is scope: whether GitBook's investigation finds other projects' documentation altered during the same window, and whether Trade.xyz's own review turns up any user harm tied to the malicious period before Monday's warning. GitBook's token reset and shutdown suggest containment, but confirmation of how many credentials or projects were touched, and any follow-up disclosure from Trade.xyz once its probe closes, will determine whether this stays a contained incident or widens.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 1 days ago | Loopscale Lending · Unknown incident | no figure in dollars |
| 1 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 1 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 3 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
| 4 days ago | Solana MEV Bot King · Hot wallet key compromise incident | $856k |
4280 incidents stored