“In the end he was right, but only because he made sure that was the case.”
Our reading, the sentence that was checked:
Altman's early-2023 warning that AI could be used for offensive cyber-attacks proved right, but only because Altman made sure it was the case.
Assessment: Unresolved Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, AI Is Already In Dangerous Hands, paragraph 85.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-ai-is-already-in-dangerous-hands-57d845-a1
We recorded 34 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2026-09-14. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Causal claim
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No horizon
- Deadline state on 2026-10-29
- No horizon (the release’s reference date)
From the speaker
- he was right
- but only because
- he made sure that was the case
Our interpretation
- He refers to Sam Altman and his early-2023 warning about offensive cyberattacks.
- The immediate context identifies the July 2026 Hugging Face attack as the event that fulfilled the warning.
- Made sure is read as attributing consequential development or operational decisions to Altman; it need not imply that he personally ordered the attack.
- Only because asserts more than general executive responsibility: Altman's actions must be shown to have been necessary to the claimed outcome.
- The causal episode is July 2026, described in the post as two months earlier. The 2023 warning is background.
Counts as supported if: Records establish the attack and connect identifiable Altman decisions to its occurrence, with evidence supporting the claim that it would not have happened without those decisions.
Counts as contradicted if: Reliable records establish that the attributed decisions were not Altman's, or that the relevant attack occurred independently of the causal role assigned to him.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Does the evidence support the cause?
Outcome: Unresolved
The record was checked, and the evidence available by the cutoff does not settle it.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No horizon
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
The warning and the later OpenAI attack are documented. The incident records also identify consequential company-level choices and missing safeguards. They do not establish that Altman personally made the relevant decisions or that his actions were necessary to the attack. That leaves the sentence's central causal attribution unresolved rather than disproved.
Limitations
- OpenAI's own account may not fully establish executive responsibility.
- A technical report's silence about Altman does not exonerate him.
- A weaker claim about institutional responsibility would require a different contract.
Evidence (3 items)
Context only: ABC News,
could be used for offensive cyberattacks
Why it matters here: The original interview verifies the warning invoked by Zitron. It does not establish Altman's role in the later incident.
- Publisher
- ABC News
- Kind of source
- News report
- Describes events of
- Public from
Context only: METR,
OpenAI gave approval to restart experiments.
Why it matters here: The investigation connects company-approved experiments with the subsequent attack and documents the agents' conduct. This passage identifies OpenAI, not Altman, as the decision-maker.
- Publisher
- METR
- Kind of source
- Independent measurement
- Describes events of
- Public from
Context only: OpenAI,
These protections were not applied
Why it matters here: OpenAI acknowledges that production safeguards were absent from the evaluation environment. This supports an operational explanation for the attack but does not identify Altman's personal decisions or establish necessary causation.
- Publisher
- OpenAI
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
What would settle it
Decision logs, correspondence, or reliable testimony identifying Altman's role in the relevant experiments and safeguards, together with evidence assessing whether those decisions were necessary to the incident.
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, AI Is Already In Dangerous Hands
In the end he was right, but only because he made sure that was the case.
- Where
- paragraph 85
- Published
- 2026-09-14
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-ai-is-already-in-dangerous-hands-57d845-a1: Current. Outcome: Unresolved. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
About assessment wyea-ai-is-already-in-dangerous-hands-57d845-a1.