Two outlets agree Microsoft's account was hijacked to push a crypto token but split on whether the deleted denial came from Microsoft at all.
The hijack is agreed, the denial is not
Crypto.news and U.Today both report that Microsoft's X account was hijacked to promote a Clippy-themed crypto token, and on that point there is no daylight between them. Where they part company is what happened next: a statement appeared on the account distancing Microsoft from the token, and was then deleted. Crypto.news and U.Today disagree on whether the deleted statement distancing Microsoft from the token actually came from Microsoft or was itself part of the hack. That is not a difference of emphasis. It is two incompatible accounts of who was speaking through a compromised account at the moment it mattered most.
The distinction is not academic. If the denial was genuine, Microsoft regained control of its own account long enough to correct the record before someone deleted that correction, which is one story about response speed and internal process. If the denial was itself planted by whoever ran the hijack, then the attackers controlled both the promotion and the apparent retraction, which is a different story entirely, one about how convincing a hijack can be made to look like a cleanup. A reader cannot hold both versions at once. They describe different actors doing different things with the same keyboard.
Nothing here is a primary document, so nothing gets settled
There is no statement from Microsoft itself in either account, deleted or otherwise, that either outlet is quoting directly as confirmed company communication. What exists is two publishers' reconstructions of a sequence that involved a deletion, which is precisely the kind of event that erases the artefact needed to adjudicate it. BlockchainReporter also carried the episode, which puts the underlying hijack among the better-attested stories of the period, carried by three independent publishers in total. That corroboration covers the fact of the hijack and the fact of the token. It does not cover authorship of the denial, because that is the one detail on which the sourcing splits rather than converges.
This is the case for leaving it open rather than picking a side. Neither crypto.news nor U.Today is a primary source here; both are describing a trace that Microsoft itself has not addressed on the record in either account. Declaring one version correct would mean resolving an attribution dispute with the exact tool that produced it, two secondary accounts of a deleted post. The honest position is that the hijack happened, the token was pushed, a denial appeared and vanished, and who typed that denial is not established by anything in front of us.
A corroborated appointment shows what the alternative looks like
Set against that, the reporting on Jay Clayton reads as a clean comparison case rather than a contested one. Cointelegraph, CryptoBriefing and The Cryptonomist EN all report that Trump is expected to name Clayton, the former SEC chairman who led the agency's crypto enforcement push, to a new AI czar role, and none of the three accounts contradicts another on who, what or the substance of the move. That is three independent publishers converging on the same facts, which is the condition under which an edition can treat a claim as reasonably settled even without a primary document, because the accounts reinforce rather than split. The appointment itself remains reported rather than confirmed by an administration statement, which keeps it unconfirmed in the strict sense, but unconfirmed and contested are not the same category. Nobody is describing a different Clayton, a different office, or a different timeline.
Reading the two stories together is the point of this edition. One shows what agreement across publishers looks like when the sourcing converges cleanly. The other shows what happens when two outlets reconstruct the same event and the seam between hack and correction cannot be independently verified, because the only artefact that could settle it was deleted before anyone outside the account could capture it.
The hijack and the token are established; who wrote the deleted denial is not, and no primary statement from Microsoft exists in either account to close that gap.
Stories in this edition
Publisher counts are as at publication and keep moving; each story page carries the live number.
- Was Microsoft's Deleted Clippy Token Denial Real or Fake? 2 independent publishers — this is the central unresolved conflict the edition is built around
- Trump Reportedly Set to Name Jay Clayton as New AI Czar 3 independent publishers — used as the contrasting case of converging, uncontested sourcing
The hijack and the token are established; who wrote the deleted denial is not, and no primary statement from Microsoft exists in either account to close that gap.