Back to collectionA wallet-compromise report receives a ticket response
A participant reported a compromised wallet in two community channels and asked for help stopping withdrawal and redemption requests allegedly initiated by an attacker. A Xai ambassador replied directly to the report and said a response had been provided in the participant's ticket. These messages were authored on June 9 UTC, although the displayed local date was June 10. The repeated reports concern the same participant, not independent evidence of multiple incidents.
A participant reported a compromised wallet in two community channels and asked for help stopping withdrawal and redemption requests allegedly initiated by an attacker. A Xai ambassador replied directly to the report and said a response had been provided in the participant's ticket. These messages were authored on June 9 UTC, although the displayed local date was June 10. The repeated reports concern the same participant, not independent evidence of multiple incidents.
The public exchange establishes a support report and acknowledgment. It does not reveal the ticket contents, prove an on-chain loss, establish that a transaction was blocked or show recovered assets. The operational question is whether an incident-response process can resolve the reported exposure; this exchange does not document that outcome. It also provides no support for the earlier estimate of aggregate airdrop value or for a claim that Night Ash handled the case.