Onyx Treasury transferred 620 million XCN tokens, according to blockchain security firm Blockaid, which issued an exploit alert tied to the transaction. The move was part of a migration proposal Onyx had publicly promoted. What's left in the project's Ethereum treasury contract is about 1.89 million XCN — a rounding error next to what just moved.
The migration that emptied the treasury
Onyx didn't hide the plan. The migration proposal was public, and the treasury transfer appears to follow it. That matters because it splits the story in two. On one side, there's a team executing a roadmap item it told holders about. On the other, there's a security firm looking at the same transaction and deciding it warranted an exploit alert.
The 1.89 million XCN remnant is the detail that's hard to ignore. If the migration was routine, you'd expect either a clean sweep or a locked contract with a clear explanation. What's on-chain now is neither.
What Blockaid saw
Blockaid's alert doesn't come with a public post-mortem attached to these facts. The firm flagged the transfer as an exploit — that's the label, and in crypto, that label travels faster than any clarification. Security alerts often land before teams have their messaging ready, which leaves holders refreshing explorers and waiting for someone to say whether the contract was drained by design or by someone else.
There's no confirmed answer yet on which it was. The public migration proposal is the strongest piece of evidence pointing toward intentional movement. The exploit alert is the strongest piece pointing the other way. Both can be true at once if the migration mechanism itself had a flaw that Blockaid's systems caught.
Why the treasury contract matters
Ethereum treasury contracts are where token projects park the supply they haven't put into circulation, typically with some form of multisig or timelock protecting withdrawals. When one goes from holding hundreds of millions of tokens to holding under two million, the question is who signed off and under what conditions.
Onyx hasn't issued a statement addressing the alert in the facts available here. That silence, combined with the near-empty contract, is why this is more than a routine migration story. Holders watching the treasury address can see the balance. They can't see the intent.
The awkward part
Publicly promoting a migration and then having a security firm flag the resulting transfer as an exploit is a bad look regardless of what actually happened. If Onyx executed its own plan correctly, it now has to explain why Blockaid's monitoring treated it as an attack. If it didn't, the 620 million XCN question gets much worse very quickly.
The timing isn't great either. Migration proposals are supposed to reassure holders. This one has produced the opposite effect so far.
The next concrete thing to watch is whether Onyx responds directly to the Blockaid alert — and whether that response includes the destination of the 620 million tokens or just a restatement of the migration plan. Until one of those two things happens, the treasury contract balance is the only hard number anyone has.




