Esc
RegulationEmerging

OpenAI accused of withholding wiki hack data from US Congress

Is this a scandal?

Not yet — an early signal. Noise 51/100, holding steady, across 2 sources.

SCAND-230079as of Methodology
Cite this incident"OpenAI accused of withholding wiki hack data from US Congress." SCAND.Ai incident SCAND-230079, noise 51/100 as of September 9, 2026. https://scand.ai/scandal/openai-accused-withholding-wiki-hack-data-congress
FORECASTForecast, not fact

Congressional committees will likely subpoena OpenAI's internal incident logs to verify disclosure timelines because this allegation provides concrete evidence supporting legislative arguments for mandatory US AI safety reporting.

51

Noise 51/100 — louder than 99% of tracked AI controversies.

AI-assisted analysis · How we work

Why it matters

Highlights how mandatory EU disclosure rules expose gaps in voluntary US AI safety reporting frameworks.

Key points

  1. Assemblymember Alex Bores alleges OpenAI withheld German wiki hack details from Congress while reporting to the EU.
  2. The European Commission confirmed receiving an incident report from OpenAI regarding the Wikipedia hijacking.
  3. EU AI Act mandates incident disclosure within 15 days, placing the reporting deadline around July 6.
  4. Bores attributes the alleged information gap to mandatory EU disclosure versus voluntary US reporting standards.
  5. OpenAI has not issued a public statement confirming or denying the selective disclosure allegation.

The story

New York Assemblymember Alex Bores accused OpenAI of withholding information regarding a German Wikipedia hijacking incident from US lawmakers while complying with European Union reporting mandates. Bores stated that the European Commission confirmed receiving an incident report from OpenAI, likely submitted by the July 6 deadline under the EU AI Act’s 15-day disclosure rule. The lawmaker alleged that OpenAI did not provide equivalent details to Congress during the same period, attributing the discrepancy to voluntary US standards versus mandatory European requirements. OpenAI has not publicly commented on the specific allegation of selective disclosure or the timeline of its communications with US legislators. This development underscores growing tensions between American AI companies and domestic regulators regarding transparency and incident response protocols.

Who's involved

Critic
Alex Bores

Alleges OpenAI exploited voluntary US rules to withhold security incident data that was mandatorily reported to the EU.

Defender
OpenAI

Has not publicly responded to allegations of selectively withholding incident information from US lawmakers.

Neutral
European Commission

Confirmed receipt of an incident report from OpenAI regarding the German Wikipedia hijacking without specifying the submission date.

Join the Discussion

Discuss this story

Community comments coming in a future update

Be the first to share your perspective. Subscribe to comment.

Noise Level

Buzz51?Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
Decay: 94%
Reach
46
Engagement
56
Star Power
70
Duration
57
Cross-Platform
50
Polarity
50
Industry Impact
50

The timeline

  1. Bores alleges selective disclosure

    Assemblymember publicly accuses OpenAI of stonewalling Congress after EU confirms receipt of the incident report.

  2. EU AI Act reporting deadline expires

    The latest date OpenAI could have submitted the incident report to remain compliant with the 15-day mandate.

  3. Estimated discovery of German wiki hijacking

    Inferred start date of the 15-day EU AI Act reporting window based on the July 6 deadline mentioned by Bores.

The full record

Sources & methodology

Every claim above traces to these primary items. How we score →

The forecast

Congressional committees will likely subpoena OpenAI's internal incident logs to verify disclosure timelines because this allegation provides concrete evidence supporting legislative arguments for mandatory US AI safety reporting.

Forecast, not fact — an editorial estimate we score when this resolves.

You're up to date

That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.

Follow this story

We keep this page current — no need to check back. We'll send the next real change to your inbox, nothing else.

Tracking this story since September 7, 2026.