What four Telegram channels say happened at Muwaffaq Salti on 11 July 2026, and what they do not

At 09:09 UTC on 11 July 2026, an account called FotrosResistancee posted on Telegram that "low-res satellite imagery confirms Iranian ballistic missiles struck at least 2 aircraft hangars on US Muwaffaq Salti Air Base, in Jordan," adding that "these were freshly built hangars." Within a minute, the channel IntelSlava carried a slightly more cautious version of the same claim, noting that "low-quality satellite images released by Iranian media allegedly show the aftermath of Iranian missile strikes on Jordan's Muwaffaq Salti Air Base." Two minutes later, at 09:11 UTC, IntelSlava identified four western Iranian launch cities (Arak, Khomein, Urmia, and Tabriz) as the origin points and named Muwaffaq Salti as the likely target. By 10:58 UTC, the geopolitical channel DDGeopolitics had republished the FotrosResistancee post verbatim, attributing the imagery credit to an account called MenchOsint.

The thesis the four channels collectively advance is straightforward: Iran struck a US base in Jordan with ballistic missiles launched from multiple western Iranian cities, hit at least two newly built hangars, and the proof is in low-resolution satellite frames now circulating on Iranian media. What is striking, and what any careful reader should pause on, is that the entire evidentiary chain, from launch point to launch point, from image to image, runs through channels that are either Iranian-aligned, pro-Iran in editorial slant, or republishing those two. No Western wire service has, in this thread, independently confirmed the strike. No US military spokesperson is on the record. No Jordanian official is on the record. No commercial satellite operator has released higher-resolution imagery. The narrative, as of 11:30 UTC on 11 July 2026, exists in one ecosystem only.

What the channels actually wrote

The four posts can be read almost as a relay. FotrosResistancee makes the strongest claim first: confirmation, in the present tense, that hangars were hit and that those hangars were freshly built. IntelSlava softens that framing twice. At 09:10 UTC it writes that the images "allegedly show" the aftermath. At 09:11 UTC it does not assert that the launch cities targeted Muwaffaq Salti; it says they "likely" did, while also folding in a Kuwait flag emoji that is unexplained by the surrounding text. DDGeopolitics, almost two hours later, lifts the original FotrosResistancee wording and reattributes the open-source credit to MenchOsint. None of the four posts include geocoordinates, image metadata, weapon type beyond "ballistic missile," casualty figures, or any official statement from any state party to the alleged exchange. The Iranian flag emoji used in three of the four headers signals editorial alignment; the Kuwait flag in one IntelSlava post is a small puzzle this thread does not resolve.

Where the dominant framing leans

Coverage of any Iran strike on a US base in a third country faces a structural problem of source asymmetry. Iranian state media can release imagery quickly because Tehran has an interest in framing the event. US Central Command, the Jordanian government, and major Western wire services all have institutional reasons to wait: confirming a successful strike on friendly soil is rarely a message a government wants to send unprompted. That asymmetry produces a window in which Iranian-aligned channels can shape the initial narrative before any countervailing voice arrives. The four Telegram posts in this thread all fall inside that window. They cite one another, cite Iranian media releases, and credit an open-source account (MenchOsint) without any independent verification of MenchOsint's own sourcing. The result is a self-reinforcing picture that is, as of this writing, uncorroborated outside its own information ecosystem.

What we verified, and what we could not

The verification ledger on this story is unusually thin, and the honesty of that matters more than the appearance of having it nailed down.

What we have: four Telegram posts from three distinct accounts, published between 09:09 UTC and 10:58 UTC on 11 July 2026, all of which converge on the same core claim: an Iranian ballistic-missile attack on US Muwaffaq Salti Air Base in Jordan, with damage to at least two aircraft hangars described as newly built. Launch-point cities named are Arak, Khomein, Urmia, and Tabriz. Imagery is described as low-resolution and is attributed to Iranian media releases. Open-source credit is given to an account called MenchOsint, whose own sourcing is not laid out in any of the four posts.

What we do not have: any statement from US Central Command, the Pentagon, the US Embassy in Amman, or the Jordanian government. Any wire-service confirmation from Reuters, the Associated Press, the BBC, Al Jazeera, or the Wall Street Journal. Any image metadata, geolocation coordinates, or independently timestamped commercial-satellite imagery. Any independent confirmation that the mench osint account's claims hold up under standard open-source verification. Any casualty figures on any side. Any official Iranian government statement, distinct from Iranian media reporting. Any record of what aircraft, if any, were inside the hangars alleged to have been hit. The Telegram accounts themselves disagree on register. FotrosResistancee and DDGeopolitics state confirmation; IntelSlava hedges with "allegedly" and "likely." That internal disagreement inside the same information ecosystem is itself a finding.

Why this story still matters

The caution above should not be read as dismissal. If the underlying event happened, it is significant by any measure: a direct Iranian missile strike on a US installation in a third Arab country, against hangars that, if the "freshly built" framing holds, were constructed during the period of heightened regional tension. The geopolitical consequences of such a strike would extend well beyond Muwaffaq Salti. Air basing in Jordan underpins US operations across the Levant, and any hardening of Iranian capability to put high-value aircraft on the ground at risk has strategic weight. So the underlying claim deserves continued reporting. The point of the ledger above is that the current public record of this story does not yet support the framing now dominant inside the Telegram ecosystem.

Readers should treat the four posts as a starting position: a coordinated narrative released by channels with a known editorial line, supported by imagery whose provenance has not been independently audited, and unaccompanied by any statement from the governments on either side of the alleged exchange. Independent satellite operators, OSINT communities outside the Iran-aligned orbit, and wire-service confirmations from the major agencies will, if they arrive, determine whether the picture sharpens or dissolves. Until then, the strike is reported by its presumed perpetrator and those who amplify that reporting.

What to watch in the next 24 hours

Three signals will tell us whether the strike happened. First, a US Central Command statement, or its conspicuous absence. Second, any commercial-satellite imagery of Muwaffaq Salti from Planet Labs, Maxar, BlackSky, or comparable operators, posted publicly or referenced by major wires. Third, a Jordanian government statement, given that strikes on Jordanian soil, even against a foreign base, are politically consequential in Amman. On the Iranian side, official statements from the Islamic Republic's foreign ministry, defense ministry, or permanent mission to the UN would carry more weight than the media releases cited in the four Telegram posts above. None of those signals has appeared in this thread as of the cutoff for this piece. The story is moving, but it has not yet been verified outside the channel that broke it.

Desk note: this article is built on a deliberately narrow source base, four Telegram posts from three accounts, because that is the entire public record Monexus could verify as of the cutoff. Monexus does not assert the strike happened, did not happen, or happened in the form described. The piece names the channels responsible for the dominant framing, attributes imagery credit where the channels themselves credited it, and flags the absence of independent corroboration. Where wire confirmation arrives, Monexus will publish a follow-up that puts it alongside, or in place of, the ledger above.

Wire provenance

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

• https://t.me/FotrosResistancee
• https://t.me/intelslava
• https://t.me/intelslava
• https://t.me/DDGeopolitics