Houthis claim two Saudi tanker strikes in the Red Sea, including the Wafa off Yanbu

Yemen's armed forces spokesman Yahya Saree said on the morning of 5 August 2026 that his forces had struck the Saudi-owned oil tanker NCC Wafa in the northern Red Sea, off the coast of Yanbu, with ballistic missiles, and had claimed a direct hit. The statement was relayed by Telegram channels Clash Report, GeoPolitical Watch, Iran's Tasnim news agency and The Cradle on the same morning, beginning at 07:02 UTC. The Cradle and Clash Report separately framed the strike as the eighth Saudi oil tanker hit since the launch of the Houthi maritime blockade.

A second announcement, carried by the rnintel channel at 07:09 UTC, said Ansarullah had targeted the Saudi tanker NCC Ghazal in the Red Sea, accusing the vessel of violating the Houthi blockade on Saudi Red Sea ports. That post is the single source item that bundles the Ghazal claim with a wider count, characterising the Ghazal announcement as marking the fourth Saudi tanker reportedly struck by the Yemeni group. The "eighth" and "fourth" counts are presented by the channels in their own framing; the items reviewed do not provide an independent registry that reconciles them. Both announcements are claims from the group itself; none of the items reviewed carries independent tracking data, satellite imagery, or third-party confirmation from the vessel owners, the Saudi energy ministry, or international maritime authorities.

The source items also point to a wider running tally than either count alone suggests. The Cradle's Wafa framing sits inside a campaign the channel dates to the launch of the maritime blockade, while the rnintel post refers to the wider pattern of Saudi shipping pressure in the Red and Arabian Seas and at Bab el-Mandeb. Read together, the two announcements describe a maritime campaign that has narrowed from broad disruption of commercial shipping into a more pointed pressure line against Saudi-flagged or Saudi-owned tanker traffic in the Red Sea.

What was claimed, by whom, and in what order

The first item in the morning's relay chain was posted at 07:02 UTC on 5 August 2026 by Clash Report, which said Yemen's Houthis had struck the Saudi oil tanker Wafa with ballistic missiles in the northern Red Sea off Yanbu and had claimed a direct hit. The outlet described the strike as the eighth Saudi oil tanker hit since the launch of the maritime blockade. Two minutes later, at 07:04 UTC, GeoPolitical Watch reposted the same core claim, specifying the northern Red Sea off the coast of Yanbu as the strike location.

At 07:09 UTC the same morning, the rnintel channel posted the Ghazal claim: Ansarullah had targeted the Saudi tanker NCC Ghazal in the Red Sea, on the stated ground that the vessel had violated the Houthi blockade on Saudi Red Sea ports. The rnintel post framed the Ghazal announcement as marking the fourth Saudi tanker reportedly struck by the Yemeni group, and it is the only source item that bundles the Ghazal allegation with a wider count.

At 07:10 UTC, Iran's Tasnim news agency carried Yahya Saree's statement directly, recording that the Yemeni armed forces spokesman had issued the announcement on Wednesday morning. The Cradle, a Beirut-based outlet that has tracked the Houthi campaign closely, posted at 07:24 UTC with the headline that Yemen had hit its eighth Saudi oil tanker since the launch of the maritime blockade, tying the announcement to the armed forces' formal statement issued earlier that morning.

The "eighth" framing is associated in the source items with the Wafa claim, as carried by Clash Report and The Cradle. The "fourth" framing is associated in the source items with the Ghazal claim, as carried by rnintel. The two counts travel through different channels and are not reconciled inside any single item reviewed here. The Cradle item does not repeat the Ghazal allegation in the same form; the Ghazal-specific framing travels through rnintel alone in the items available to this article.

The structural frame: a blockade with a price tag

Monexus analysis: read together, the announcements describe a maritime campaign with two distinct targets. The first is the throughput of Saudi crude and product exports along the Red Sea coast near Yanbu. The second is the credibility of the Saudi-flagged fleet itself: by naming vessels, claiming a running count of hits, and tying strikes to alleged violations of Houthi rules of access to Saudi Red Sea ports, the movement is trying to convert a tactical capability into a regulatory regime that shipowners must price in.

That is a campaign that can be sustained with fewer missiles and produces better propaganda per round, because each claim carries an explicit list of prior hits. The earlier strikes in the campaign were justified, in Houthi statements, as solidarity with Palestinians in Gaza and as pressure on Israeli-linked shipping; the items reviewed do not reproduce those earlier justifications in the Wafa and Ghazal announcements. The Saudi-flagged tankers do not fit the Gaza frame, which is why the Ghazal announcement leans on the blockade-of-ports justification rather than the Gaza one. The two justifications now coexist in the same news cycle.

What remains unverified

The source items are claims, not confirmed hits. None of the items reviewed carry independent tracking data, satellite imagery, or third-party confirmation from the vessel owners, the Saudi energy ministry, or international maritime authorities. The Cradle's framing of the Wafa strike as the eighth Saudi tanker since the blockade began is consistent with the group's own sequencing; it has not, in these items, been audited by an independent maritime database.

The Ghazal count is ambiguous on a second axis. The rnintel excerpt characterises the Ghazal announcement as marking the fourth Saudi tanker reportedly struck by the Yemeni group. Read literally, that is a tally of distinct vessels rather than a claim of repeat strikes on the same hull. The source items reviewed do not name a prior incident list with dates, and they do not specify whether the "fourth" refers to a fourth vessel or, in the group's own framing, to a fourth strike event more broadly. Readers should treat the specific count as the group's own tally until an independent registry confirms it.

The rnintel post also points to a wider pressure picture across the Red and Arabian Seas and at Bab el-Mandeb, where the channel has previously tracked Saudi shipping diversions; the items reviewed do not enumerate that wider pattern. The "direct hit" language originates with the Houthi claim itself; the channels are relaying it, not independently establishing it. The items reviewed do not specify casualties, cargo type, damage severity, or the vessels' last known positions from automatic identification system feeds.

Stakes: who pays if the campaign holds

If the Wafa and Ghazal claims hold up under independent verification, the cost falls first on Saudi Aramco's shipping partners and on the insurers who price Red Sea transits. Saudi Arabia's response options range from naval escort to expanded overland pipeline usage, but each carries a price: armed escorts raise the political stakes of any future incident, while pushing more crude eastward through any internal pipeline network adds domestic refining constraints and concedes the Red Sea route to the Houthi narrative.

The wider pattern is harder to read. A campaign that singles out Saudi tankers forces a choice on Riyadh: absorb the cost, escalate militarily against the Houthis on a second front, or push harder for a Gaza ceasefire that would, in the Houthi framing, justify a stand-down of the maritime campaign. The next forty-eight hours will test which of those paths the kingdom chooses; the price of any tanker in the Red Sea is now, by design, also the price of that decision.

This article relies on Houthi-aligned and regional Telegram channels and on outlets that relay their statements. The Cradle and Tasnim are identified by name in the source items; independent confirmation of either strike has not been published in the items reviewed, and Monexus has not independently verified the vessel hits, the casualty count (which the sources do not specify), or the cumulative tally of Saudi tankers struck.

Wire provenance

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

• https://t.me/ClashReport/91524
• https://t.me/GeoPWatch/38187
• https://t.me/rnintel/65309
• https://t.me/JahanTasnim/228548
• https://t.me/thecradlemedia/65590
• https://t.me/TheCradleMedia/65590