XMR1 operator attributes key exposure to a hosting breach and promises refunds

Wagyu’s operator says an old server exposed the XMR1 deployer key. The hosting-related explanation remains a claim; refunds have been promised.

Current status: Status under review

At publication

Affected partyWagyu / XMR1
Event dateNovember 20, 2026
NetworkHyperliquid, Ethereum
Status reported by sourceStatus under review
Estimated loss$13,500,000
FrozenNo confirmed data
ReturnedNo 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

  1. Follow-upStatus under review

    XMR1 operator attributes key exposure to a hosting breach and promises refunds

  2. First publicationStatus under review

    XMR1 faces suspected security incident after deployer transfers

Source report:

Sources

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

Submit an application

Leave a request

How to contact you?

Specify Telegram username or email — depending on the chosen method of communication.