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

Two Saudi oil tankers struck by unknown projectiles in Strait of Hormuz

Two supertankers carrying Saudi crude were hit by unknown projectiles in the Strait of Hormuz late Monday, per shipping firms.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 7 placed sources from 2 publishers.
As of 2026-09-01 15:40 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
Marisks and Kpler, shipping intelligence and tracking firms, reported that two supertankers carrying Saudi oil were struck by unknown projectiles within minutes of each other while transiting outbound through the Strait of Hormuz late on 2025-08-31. [1][6] U.S. Treasury Secretary Scott Bessent said on 2026-09-01 that the Strait of Hormuz could be bypassed in two years as oil pipelines provide alternative routes for Persian Gulf energy shipments, predicting the waterway would become 'a worthless piece of water.' [2] According to Kpler data, the two tankers each loaded 2 million barrels of Saudi crude at the Juaymah terminal in the week before the attack. [3] Marisks reported that the Saudi-flagged VLCC Sidr was struck by unknown projectiles about 16.6 nautical miles northeast of Khasab, Oman at about 1952 UTC on 2025-08-31, and that minutes later the Liberian-flagged VLCC Senegal Prosperity was struck by three projectiles about 17 nautical miles east of Khasab, with all crew reported safe. [4] Oil prices rose on 2025-09-01 after U.S. President Donald Trump threatened further strikes against Iran, following the first exchanges of fire since late July. [5] U.S. Treasury Secretary Scott Bessent said on 2026-09-01 that Washington would likely announce sanctions against another bank that week and an additional bank the following week. [7]
Proof7 sources · 2 publishers
What this stands on
  1. Marisks and Kpler, shipping intelligence and tracking firms, reported that two supertankers carrying Saudi oil were struck by unknown projectiles within minutes of each other while transiting outbound through the Strait of Hormuz late on 2025-08-31. · AL-MONITOR: The Middle Eastʼs leading independent news source since 2012
  2. U.S. Treasury Secretary Scott Bessent said on 2026-09-01 that the Strait of Hormuz could be bypassed in two years as oil pipelines provide alternative routes for Persian Gulf energy shipments, predicting the waterway would become 'a worthless piece of water.' · mint
  3. According to Kpler data, the two tankers each loaded 2 million barrels of Saudi crude at the Juaymah terminal in the week before the attack. · AL-MONITOR: The Middle Eastʼs leading independent news source since 2012
  4. Marisks reported that the Saudi-flagged VLCC Sidr was struck by unknown projectiles about 16.6 nautical miles northeast of Khasab, Oman at about 1952 UTC on 2025-08-31, and that minutes later the Liberian-flagged VLCC Senegal Prosperity was struck by three projectiles about 17 nautical miles east of Khasab, with all crew reported safe. · AL-MONITOR: The Middle Eastʼs leading independent news source since 2012
  5. Oil prices rose on 2025-09-01 after U.S. President Donald Trump threatened further strikes against Iran, following the first exchanges of fire since late July. · AL-MONITOR: The Middle Eastʼs leading independent news source since 2012
  6. Maritime security consultant Marisks said that two oil tankers attempting to leave the Strait of Hormuz were struck by projectiles late on 2026-08-31. · mint
  7. U.S. Treasury Secretary Scott Bessent said on 2026-09-01 that Washington would likely announce sanctions against another bank that week and an additional bank the following week. · mint
We do not know which country they 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 · 7 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 Tuesday, September 1, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 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
We do not know which country they 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)b5f87aeebfd5d12d1dbcb4e1e7ffebc112e15419cf23f4eb8d307f809e877ece
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.