Claim: A video circulating online shows a recent Iranian attack on Tel Aviv — Verdict: Unverifiable without the actual footage

The claim is that a video circulating online depicts a recent Iranian attack on Tel Aviv. The verdict is unverifiable — not because the underlying conflict is fictional, but because the specific video has not been identified or provided for examination, making any confident judgment impossible in either direction.

Start with what is confirmed. According to BBC News's Iran–Israel conflict timeline, Iran launched a direct missile and drone attack on Israel on April 13–14, 2024 — the first direct Iranian strike on Israeli territory in history — and followed with a second ballistic missile salvo on October 1, 2024. These are real events. The geopolitical premise of the claim is not fabricated. That matters, because it gives recycled or misattributed footage a plausible hook.

Here is where the claim runs into serious trouble. The IDF's official statements confirmed that Iranian ballistic missiles in the October 1, 2024 attack were largely intercepted before reaching Tel Aviv. The IDF did not confirm significant impact footage from within Tel Aviv city limits. That means any video specifically claiming to show a successful Iranian strike landing in Tel Aviv requires extraordinary verification — the military record makes such footage inherently unlikely. Meanwhile, AFP Fact Check documented multiple instances in both April and October 2024 where videos purporting to show Iranian strikes on Israel were actually footage from Syria, Gaza, or earlier conflicts entirely. This was not an occasional error; AFP described it as a systematic pattern of misattribution during these escalations.

The steelman version of the claim is straightforward: real attacks happened, real video exists from those events, and some of it is authentic. That is true. But authenticity of some footage does not validate any particular video. The critical flaw in sharing an unverified clip is the missing verification step. Bellingcat's established methodology for conflict-zone videos requires geolocation — matching landmarks and street layouts to a specific location — chronolocation using sun angle and shadows, and metadata analysis of the file itself. First Draft's verification protocols are equally direct: without the actual file, URL, or cryptographic hash, no fact-checker can confirm whether a described video is authentic, recent, or correctly placed. A description of a video is not a video.

The manipulation pattern here is a classic two-step. First, anchor the claim in a real event so it feels plausible. Second, strip the footage of its original context — location labels, dates, source accounts — so it cannot be easily traced. The result is a video that feels urgent and credible precisely because the underlying conflict is real, but which may depict something entirely different. Watch for this whenever a high-tension news event breaks: the first wave of viral video almost always contains misattributed footage, and the emotional urgency of the moment is the mechanism that bypasses normal skepticism.

The responsible position is to withhold judgment until the specific video is identified and subjected to geolocation, chronolocation, and cross-referencing against official damage assessments. Sharing it as confirmed — in either direction — before that work is done is itself part of the problem.