Capcom reports additional compromised accounts beyond the initial 11.7 million Capcom IDs.

Question

Six frontier AI models put this at 20% by 25 Jan 2027. Full reasoning from every model.

WillHappen.ai · Accepted Answer

20% — the median of 6 frontier models, resolving by 2027-01-25.

Answer

Gemini (Google): 18% — Capcom forensic probes typically conclude before revision windows close, making a post-disclosure count increase rare in 3 months. Most corporate disclosures only revise breach counts upward if ongoing third-party forensic reviews discover wider database exfiltration. With less than three months until the January 2027 resolution date, Capcom has little procedural time left to conclude new audits. Discovery of separate compromised legacy backup databases or a ransomware group leak would immediately trigger an upward revision.

Answer

Claude (Anthropic): 12% — Hinges on whether Capcom's forensic investigation is still active or already closed after initial disclosure. Companies typically finalize breach scope within months; a static 11.7M figure likely reflects a completed investigation. Base rate for upward revisions to already-large disclosed breach numbers is low once initial report is public and detailed. A new attack vector or follow-up lawsuit forcing re-disclosure would be the main thing that could change this.

Answer

GPT (OpenAI): 37% — This hinges on whether Capcom's continuing forensic work finds a distinct larger account population worth publicly quantifying. Capcom's November 2020 incident already produced evolving disclosures, but firms often retain their final affected-count estimate once notice starts. By 25 January 2027, Capcom must both identify extra IDs and issue a public update; neither is legally automatic absent new harm or notification duties. A regulator inquiry, leaked dataset showing more Capcom IDs, or a new breach-linked filing would materially raise the odds.

Answer

Grok (xAI): 22% — Capcom forensics must still find extra IDs and issue a public update by Jan 2027. Capcom already published a precise 11.7 m figure, implying the count is largely complete. Game-account breaches revise upward ~25 % of the time inside 90 days; this case sits at that rate. A fresh dump or regulator filing would be the clearest signal to raise the odds.

Answer

DeepSeek (DeepSeek): 22% — Whether Capcom's own forensic review finds more affected IDs than the 11.7M it already disclosed. Capcom's Nov 2020 statement already revised the figure upward from 350k to 11.7M, and it has since said the count is final unless new evidence emerges. The breach is over five years old; forensic reviews typically conclude within 12-18 months, so a fresh upward revision by Jan 2027 is unlikely. Base rate for companies revising breach totals upward after a completed investigation is low, though Capcom's history of undercounting initially makes it slightly above…

Answer

Qwen (Alibaba): 8% — The 11.7M figure has been stable since 2021; revising a 6-year-old breach disclosure upward requires a new trigger. Capcom's breach disclosure stabilized by mid-2021 and has not been revised since; companies almost never revisit finalized breach counts years later absent new forensic… The resolution window is only ~3 months, and no known investigation, lawsuit discovery, or regulatory action is currently pressuring Capcom to re-examine the Ragnar… A revision would most likely come from a separate new breach being folded into the same disclosure, which is possible but unlikely to happen and be publicly reported…

Capcom reports additional compromised accounts beyond the initial 11.7 million Capcom IDs.

U.S. federal civilian agencies complete the removal of DeepSeek products from IT systems pursuant to the DHS order.

Iran launches a direct military strike against Israel following border airspace maneuvers.

IAEA nuclear inspectors are permitted to return to Iran.

Israel launches a major military operation in the West Bank following the October 23 checkpoint attack.