Yemeni strike claims near Al-Kharj circulate on Iranian state Telegram; only attributed, second-hand reporting in available thread

At 22:31 UTC on 13 October 2026, the Arabic-language channel Tasnim Plus posted that "Arab sources report several explosions in the Saudi city of Al-Kharj." By 23:10 UTC the same channel had re-published that wire with an additional framing line: a Yemeni cruise missile had, per "Arab sources," struck its target near Al-Kharj, with Prince Sultan Air Base cited as one of the Saudi army's most important military installations and located near the impact site. Between those two endpoints, two English-language Tasnim posts (at 22:55 and 23:00 UTC) and a Jahan Tasnim post (at 22:54 UTC) carried paraphrases of the same Arabic-media claim. A fourth Tasnim Plus item, posted at 00:10 UTC on 14 October, framed the episode as a Yemeni journalist's warning to Saudi Arabia that "this war marks the beginning of the process of Saudi Arabia's demise."

That sequence is the entirety of the public-facing wire this article is built on. Read together, it is an Iranian state-affiliated Telegram chain moving a single attributed claim into circulation across two languages inside forty minutes, with the named target escalating from a city to an airbase over the course of the chain. The thread contains only attributed, second-hand reporting from those outlets. This article has not independently established whether the Saudi defence ministry, the Saudi Press Agency, a coalition spokesperson, Al-Masirah, or an independent wire service has, in parallel to this chain, issued any confirmation, denial, or claim of authorship.

How the wording built in real time

The originating posts use attributive, not first-person, language throughout. Tasnim's English channel wrote that "Arabic media reported that a Yemeni cruise missile hit its target near the city of Al-Kharj in Saudi Arabia," and Tasnim Plus used the same construction in Arabic. The English posts and the Jahan Tasnim item do not name an on-the-ground correspondent, a city block, a runway, or a specific installation; they reference "its target near the city of Al-Kharj." The Arabic-language Tasnim Plus post at 23:10 UTC is the only item in the set that names Prince Sultan Air Base, and it does so as part of the contextual framing ("one of the Saudi army's most important military installations") rather than as a confirmed hit.

That phrasing matters on two levels. On the wire side, attribution to unnamed "Arab sources" or "Arabic media" preserves deniability if the underlying report turns out to be wrong, and it signals that the posting newsroom is relaying rather than asserting. On the editorial side, it means any reader who lands on the English-language version is seeing a single-source, single-outlet-family report in which the noun of agency is "Arabic media," not Tasnim itself.

The chain's progression is itself diagnostic. The 22:31 UTC item is the closest to a wire moment: "several explosions in the Saudi city of Al-Kharj," no missile mentioned. The 22:54 UTC Jahan Tasnim post re-states that an Arabic-media-attributed cruise missile "hit its target near Saudi Arabia's Al-Kharj city." The 22:55 and 23:00 UTC English posts paraphrase the same. The 23:10 UTC Tasnim Plus item in Arabic adds the Prince Sultan Air Base framing. The shape of the chain is a claim hardening over forty minutes across three Tasnim-controlled channels, not the shape of a confirmed event corroborated on the ground.

What the thread specifies, and what it does not

The available source items specify the following, and only the following: that Iranian state-affiliated Telegram channels carried an Arabic-media-attributed claim of a Yemeni cruise-missile strike near Al-Kharj between 22:31 and 23:10 UTC on 13 October 2026; that one of those posts named Prince Sultan Air Base as a major Saudi military installation near the city; and that a separate Tasnim Plus post at 00:10 UTC on 14 October carried a Yemeni journalist's warning to Saudi Arabia about the war's trajectory.

The available source items do not specify a casualty count, a missile type or model, the distance between the reported impact point and any airfield asset at Prince Sultan, whether Saudi air defences engaged an incoming projectile, whether debris or shrapnel caused ground effects, or the time at which the underlying "explosions" were first heard on the ground. The thread does not contain a Saudi defence ministry statement, an SPA dispatch, a coalition spokesperson line, or a Yemeni Houthi-aligned channel claim of authorship. This article has not independently established whether any such statement has since been issued through a channel outside this thread.

Monexus assessment: how to read this chain

The outlets in the chain are Iranian state-affiliated. That is a provenance fact, not a verdict on the underlying claim, but it sets the editorial frame. Posts in this chain carry a structural interest in presenting Yemeni missile capability in maximal terms, and they have done so before. The cautious, second-person phrasing ("Arabic media reported") is consistent with a newsroom that has received a claim through intermediaries and is not yet in a position to vouch for it independently. A Western wire would normally add a Saudi on-record denial or confirmation before publishing the same headline; nothing equivalent appears in the available thread.

Monexus assessment: the most natural reading of the chain is that an unattributed "several explosions" wire at 22:31 UTC hardened into a fully attributed "Yemeni cruise missile" strike by 23:10 UTC, with the named target escalating from a city to an airbase over forty minutes. The available thread contains only attributed reporting from Iranian state-affiliated channels, and this article has not independently established the status of any Saudi or Houthi-side response.

What to watch next

The reasonable next moves are corroboration, denial, or silence. If the Houthi military spokesperson claims authorship through Al-Masirah or a successor Houthi media channel in the hours after the originating chain, that claim becomes the moment the strike is formally attributed rather than rumoured. If Saudi Arabia's defence ministry, SPA, or a coalition spokesperson issues a denial, an interception confirmation, or a no-comment, each carries a different signal: a denial would track with how Saudi readouts have historically treated similar claims; an interception confirmation would imply the air-defence layer worked; a no-comment would leave the original Telegram chain as the only wire in circulation. Satellite imagery from Planet Labs, Maxar, or Sentinel-2 over the Prince Sultan footprint would, within 24 to 72 hours, be the most direct evidence either way on damage to runways, hardened shelters, or radar installations.

Until any of those moves happens, the public record this article rests on is the Iranian state-affiliated Telegram chain, and the headline it produces is an attributed one. Monexus framed the Al-Kharj reporting as an Iranian-aligned attributed claim rather than a confirmed strike, and noted in the lede that the available thread contains only attributed, second-hand reporting from those outlets.

Desk note: Monexus declined to call the strike confirmed in the title or lede because the available thread is a single, Iranian state-affiliated chain using second-person attribution ("Arabic media reported"). The piece foregrounds the wording of the chain, makes clear the source items do not specify several key facts, and labels the pattern read as Monexus assessment rather than as observed fact.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/tasnimplus/127770
• https://t.me/tasnimplus/127765
• https://t.me/tasnimnews_en/43054
• https://t.me/tasnimnews_en/43053
• https://t.me/JahanTasnim/239617
• https://t.me/tasnimplus/127761