Better tools. Better news.
Sunday, November 22, 2026 · UTC
World

Unknown Missiles Hit Tanker in Strait of Hormuz

UKMTO reports three unknown projectiles struck a tanker near Oman in the Strait of Hormuz.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 12 placed sources from 4 publishers.
The Sidr supertanker was struck by unknown projectiles while transiting the Strait of Hormuz, located 17 nautical miles northeast of Oman's port city of Khasab. [1][2][12] Bahri, Saudi Arabia's national shipping carrier, confirmed on September 2 that two Filipino seafarers were killed on its vessel, the Sidr supertanker, during an incident in the Strait of Hormuz. [3][11] UK Maritime Trade Operations reported the incident occurred at around 20:00 UTC on Monday, approximately 17 nautical miles east of Khasab, Oman. [4][7] The UK Maritime Trade Operations Center stated that the tanker's crew remained safe following the attack. [5] Iran responded with missile attacks against US forces in Jordan, while reports also pointed to anti-ship cruise missile launches towards the strait. [6] US forces struck Iranian rocket launchers on Larak Island over the weekend after US Central Command said Tehran was preparing rockets carrying sea mines for deployment in Hormuz. [8] Iran subsequently carried out retaliation attacks on locations used by US forces in Jordan and the United Arab Emirates. [9] UKMTO reported that there were no reports of casualties or environmental consequences from the missile strike on the tanker. [10]
Proof12 sources · 4 publishers
What this stands on
  1. The UK Maritime Trade Operations Center (UKMTO) reported that three unknown projectiles struck a tanker in the Strait of Hormuz. · Lenta.ruRussia
  2. A Liberia-flagged tanker was struck by three unknown projectiles while transiting the Strait of Hormuz on the Omani side of the waterway. · Splash247
  3. Bahri, Saudi Arabia's national shipping carrier, confirmed on September 2 that two Filipino seafarers were killed on its vessel, the Sidr supertanker, during an incident in the Strait of Hormuz. · TASS
  4. The attack occurred approximately 17 nautical miles east of the city of Hasab, Oman, while the vessel was heading out of the strait. · Lenta.ruRussia
  5. The UK Maritime Trade Operations Center stated that the tanker's crew remained safe following the attack. · Lenta.ruRussia
  6. Iran responded with missile attacks against US forces in Jordan, while reports also pointed to anti-ship cruise missile launches towards the strait. · Splash247
  7. UK Maritime Trade Operations reported the incident occurred at around 20:00 UTC on Monday, approximately 17 nautical miles east of Khasab, Oman. · Splash247
  8. US forces struck Iranian rocket launchers on Larak Island over the weekend after US Central Command said Tehran was preparing rockets carrying sea mines for deployment in Hormuz. · Splash247
  9. Iran subsequently carried out retaliation attacks on locations used by US forces in Jordan and the United Arab Emirates. · Blic.rs
  10. UKMTO reported that there were no reports of casualties or environmental consequences from the missile strike on the tanker. · Blic.rs
  11. The incident involving the Sidr supertanker occurred overnight into September 1 while the vessel was attempting to exit the Persian Gulf. · TASS
  12. The Sidr supertanker was struck by unknown projectiles while transiting the Strait of Hormuz, located 17 nautical miles northeast of Oman's port city of Khasab. · TASS
1 of the 4 publishers publishes from Russia. We do not know which country the other 3 publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 12 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, September 2, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world4 publishers reported the events across 4 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
1 of the 4 publishers publishes from Russia. We do not know which country the other 3 publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)af55c34a4afebb120ae7150e447d1f9fb657ed3fb52d99b59a9d25b55d707305
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.