Skip to main content
AVOID.NET
← Clippy Token ($CLIPPY) — Microsoft X Account Hijackreviewed 2026-10-27 · 15 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Clippy Token ($CLIPPY) — Microsoft X Account Hijack against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #4[disputed][awaiting moderator]in section: Microsoft's Response and Legal Position
    “Microsoft also reportedly posted and later deleted an apology.”
    reviewerMicrosoft reportedly posted and later deleted an apologySources say the apology/disclaimer was posted by the attackers, not Microsoft. The page attributes it to Microsoft.
    Proposed correction (not yet applied)
    A fake apology and a disclaimer appeared on the hijacked account and were later deleted; Microsoft said it did not post them.
  2. #5[disputed][awaiting moderator]in the timeline
    “it later deleted an apology/disclaimer post”
    reviewerTimeline: Microsoft later deleted an apology/disclaimer postThe cited CryptoBriefing page does not mention the apology. Other sources attribute it to the attackers.
    Proposed correction (not yet applied)
    an apology/disclaimer post that Microsoft said it did not write was later deleted

unverifiable

2 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #2[unverifiable][awaiting moderator]in section: Microsoft's Response and Legal Position
    “A spokesperson, identified as Brent Colburn, gave the statement.”
    reviewerThe Microsoft spokesperson who gave the statement was Brent ColburnNeither cited tier-1 source names Brent Colburn, and a targeted search found no source linking the name to the incident. Recommend removing the name unless a source is produced.
  2. #3[unverifiable][awaiting moderator]in the timeline
    “October 2: Microsoft regained control within about 30 minutes, removed the unauthorized posts, and spokesperson Brent Colburn confirmed the breach and ongoing investigation.”
    reviewerTimeline: spokesperson Brent Colburn confirmed the breachSame unsupported name as in sections[2]. The rest of the entry is supported.

partially supported

4 claims

The cited evidence supports part of the claim but not all of it.

  1. #7[partially supported][awaiting moderator]in the summary
    “On October 2, 2026, unknown attackers hijacked Microsoft's official X account (13+ million followers) for about 30 minutes”
    reviewerThe hijack occurred on October 2, 2026Publication date is October 2, but 'Thursday' conflicts with the calendar and one source says October 1. I cannot support a specific correction.
  2. #10[partially supported][awaiting moderator]in section: Microsoft's Response and Legal Position
    “and would pursue appropriate legal action over the unauthorized use of its brands and intellectual property.”
    reviewerMicrosoft said it would pursue legal action over unauthorized brand useLegal-action intent is supported, but BleepingComputer's update says the deleted disclaimer tweet was not Microsoft's, so some of the quoted wording may come from the fake post. The exact quote was not verified.
  3. #12[partially supported][awaiting moderator]in section: The $CLIPPY Token and Alleged Pump-and-Dump
    “showed in early October 2026 a market cap of about $1,500, liquidity of about $2,700 and 75 holders, with the top 10 holders controlling 99.39% of a 995.53 million supply.”
    reviewerSolana token 'Microsoft Mascot' metrics: market cap ~$1,500, liquidity ~$2,700, 75 holders, top 10 hold 99.39% of 995.53M supply; created October 29, 2024Live figures differ slightly from the page's early-October snapshot, which is expected for on-chain data. Market cap and supply match. The October 29, 2024 creation date was not on the fetched page. The page itself says reporting has not tied this contract to the incident.
  4. #15[partially supported][awaiting moderator]in the cited sources
    “http://web.archive.org/web/20261002175303/https://blockonomi.com/u-s-spot-bitcoin-etfs-record-second-highest-daily-net-inflows-at-886-75-million/”
    reviewerBlockonomi archive of Microsoft India SIM-swap articleThe stored archive_url points to an unrelated Bitcoin ETF article, not the cited SIM-swap piece. The quoted string is only a partial match to the stored value (the field has no 'http://' mismatch but the correct archive was not found), so no correction is proposed. I did not fetch the live page; the 2024 Microsoft India incident is covered by the Winbuzzer source.

confirmed

7 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Microsoft's Response and Legal Position
    “Microsoft confirmed 'unauthorized access to our account on X including posts that did not come from Microsoft,' said the account was secured and the posts removed, and that it was continuing to investigate.”
    reviewerMicrosoft confirmed unauthorized access, said account secured and posts removed, still investigatingStatement matches BleepingComputer and SecurityWeek.
  2. #6[confirmed][no action needed]in section: The X Account Hijack
    “Microsoft's verified X account (@Microsoft, 13+ million followers) was taken over by unknown attackers for about 30 minutes.”
    reviewerHijack lasted about 30 minutes and @Microsoft had 13+ million followersSupported. Note on date: sources and the page say Thursday, October 2, 2026, but October 2, 2026 is a Friday, and CryptoBriefing dates Microsoft's statement October 1. The exact date should be rechecked against a primary source.
  3. #8[confirmed][no action needed]in section: The X Account Hijack
    “Microsoft has not disclosed how the account was compromised; security reporting noted possible vectors including SIM swapping, email-based password resets, infostealer malware harvesting session cookies, or compromise of a third-party social media management tool, none of which Microsoft has confirmed.”
    reviewerPossible compromise vectors were noted in security reporting; Microsoft has not disclosed the methodMatches SecurityWeek.
  4. #9[confirmed][no action needed]in section: The X Account Hijack
    “X subsequently suspended @clippymsftcto.”
    reviewerX suspended @clippymsftctoSupported by SecurityWeek and BleepingComputer.
  5. #11[confirmed][no action needed]in section: The $CLIPPY Token and Alleged Pump-and-Dump
    “Over $200,000 of liquidity tied to $MSFT-paired pools was alleged but could not be confirmed from primary sources.”
    reviewerOver $200,000 of liquidity was alleged but unconfirmedHedged appropriately.
  6. #13[confirmed][no action needed]in section: The $CLIPPY Token and Alleged Pump-and-Dump
    “reached an all-time high market cap of about $36.6 million on August 11, 2025.”
    reviewerClippy PFP Cult reached an all-time high market cap of about $36.6 million on August 11, 2025Matches LoreScreener.
  7. #14[confirmed][no action needed]in section: Attribution and Investigation Status
    “The @ClippyMSFT account continued promoting the token after the hijack and was active at initial reporting; its current status is unconfirmed.”
    reviewerBrent Colburn / microsoft attribution status: @ClippyMSFT continued promoting the token and no suspect namedAppropriately hedged.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.