TODAY’S PAPER | April 26, 2026 | EPAPER

IRGC warns US against escalation, vows response beyond expectations

Iran ties recent tensions to a broader conflict narrative, framing restraint as calculated deterrence


Web Desk April 26, 2026 1 min read
Members of the Islamic Revolution Guards Corps (IRGC) navy participate in an exercise in Abu Musa Island, in this picture obtained on August 2, 2023. IRGC/WANA (West Asia News Agency)/Handout via REUTERS/File Photo

The Islamic Revolution Guards Corps (IRGC) warned that any new aggression against Iran would trigger a response “beyond the enemy’s expectations,” after a recent US strike in Isfahan.

In a statement on Saturday, it called the attack a repeat of past US “humiliation” and linked it to the anniversary of the failed 1980 Operation Eagle Claw, Iran Republic News Agency (IRNA) reported.

Referencing a “third imposed American-Zionist war,” the IRGC praised Iran’s “victory” and said its current restraint is a deliberate, strategic choice, not weakness.

It cautioned that this restraint could swiftly turn into a “hellish storm” if adversaries miscalculate or launch further attacks, adding that Iran’s territory could become a “field of defeat” for aggressors.

Also Read: Oman’s Sultan, Iranian FM discuss regional crises, push for diplomacy, peace

The IRGC urged Washington to “accept reality” and not act as a tool of Israeli Prime Minister Benjamin Netanyahu.

It also claimed US regional bases are effectively destroyed and called for a full American withdrawal, while reaffirming control of the Strait of Hormuz as a key strategy.

The statement reiterated Iran’s path of “dignity and power,” warning any further aggression would provoke an overwhelming response.

The remarks come during a ceasefire that began April 8, after US-Iran talks collapsed over Washington’s demands, following a February 28 conflict in which Iran says senior leaders were assassinated.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ