At publication
| Affected party | Wagyu / XMR1 |
|---|---|
| Event date | November 20, 2026 |
| Network | Hyperliquid, Ethereum |
| Status reported by source | Status under review |
| Estimated loss | $13,500,000 |
| Frozen | No confirmed data |
| Returned | No confirmed data |
What happened
Wagyu operator PerpetualCow attributed the 20 November XMR1 incident to a breach at hosting provider 1984.hosting. He said retained files from a deleted server contained the token’s deployer key. Reporting confirms the host suffered an attack, but does not independently establish this key-exposure chain.
Bitquery’s analysis, reported by Cointelegraph, puts proceeds from the suspicious token sales at approximately $13.5 million. This concerns XMR1 on Hyperliquid, not a breach of native Monero.
The operator promised personal reimbursement and a later relaunch. No payment timetable or completed refunds are established by the reviewed statements. The promise is therefore not recorded as recovered funds.
Incident history
Source report:
Sources
- Wagyu operator — incident explanation and refund pledge — Original source · x.com · November 20, 2026
- Cointelegraph — Bitquery analysis and operator statement — Report · cointelegraph.com · November 20, 2026
- Decrypt — hosting breach and XMR1 incident — Report · decrypt.co · November 20, 2026
Information is attributed to the linked sources and has not been independently verified by Match Systems. Loss estimates and incident status may change as new evidence becomes available.
Latest incidents
- ExploitElliptic traces at least 2,310 BTC from the Binance theft through coinjoins
- Under investigationFluidkey restores service and links the attack to exposed session data
- Under investigationAbout $1.51 million leaves retired OCEAN pools; circumstances remain unclear
- Under investigationChainflip halts swaps after an estimated $4.86 million vault drain
- ExploitLookonchain tracks another 137,602 ETH from Binance-linked hack wallets
- Under investigationXMR1 faces suspected security incident after deployer transfers