TLP:CLEAR · Disclosure is not limited.

Jordan's al-Tuf strikes: casualty claims and coordination dispute

Time window: Last 1 day · Audience: General analyst · Type: Situation report · DTG: 2026-11-04 09:38Z · Overall confidence: HIGH

BLUF

Jordan very likely conducted airstrikes at al-Tuf in Daraa on 26 October, three days after the attack at St George's Greek Orthodox Church in Hammoud. The latest reporting says nine people were killed in al-Tuf, while the identity of the strike targets and whether Damascus coordinated with Amman remain unresolved.

Executive summary

Reporting places Jordanian Air Force strikes at al-Tuf, in Daraa countryside, on 26 October. A report gives a toll of nine dead, including three children and one woman, and three wounded. Jordanian security services say the captured Hammoud attackers belonged to ISIS, but formal charges include conspiracy, which is in tension with the security account that the attack was spontaneous. Damascus denies prior coordination, while Jordan says the strikes were coordinated. Syria lodged a formal protest and announced an urgent joint field and security committee; a subsequent joint statement expressed regret over civilian deaths and respect for Syrian sovereignty. Residents in Daraa protested, with some calls to close the Jordanian embassy in Damascus.

Change from previous assessment

Since the 3 November 2026 brief, new reporting gives an al-Tuf toll of nine dead, rather than the seven deaths previously reported by Syrian authorities. Jordanian security services now say the captured Hammoud attackers belonged to ISIS and acted spontaneously; the formal charges include conspiracy, adding tension to that account. A Syrian-Jordanian joint statement expressing regret over civilian deaths and respect for Syrian sovereignty, alongside Syria's announced joint committee, adds evidence of official engagement but does not resolve the coordination dispute or establish a link between the defendants and the al-Tuf targets.

Key judgments

1. Jordan very likely conducted airstrikes at al-Tuf in Daraa countryside on 26 October, three days after the 23 October attack at St George's Greek Orthodox Church in Hammoud, Karak Governorate. The reported operation name, Jordanian Deterrence-Hammoud, associates the strikes with the church incident in Jordanian public framing. (Confidence: medium · REPORTED)
   • I&W: A Jordanian military statement naming the Air Force and al-Tuf as the site of the 26 October strikes would add confirmation; a Syrian inquiry attributing the strikes to another actor would challenge this judgement. (0-30 days)
2. Nine people, including three children and one woman, were reported killed at al-Tuf, with three others wounded. Raseef22 reported these figures; the later Syrian-Jordanian joint statement acknowledged civilian casualties but did not give a total. (Confidence: medium · REPORTED)
   • I&W: A newly published official casualty list giving nine deaths and three injuries would corroborate the reported toll; a revised list with different figures would change it. (0-30 days)
3. It is unlikely that the available reporting establishes that the al-Tuf targets were ISIS positions linked to the Hammoud attackers. Jordanian officials say the attackers belonged to ISIS and that the strikes targeted ISIS, but the reporting does not independently establish either the target identity or a link between the targets and the defendants. Formal charges include conspiracy and promoting a terrorist group's ideas, in tension with the security account that the attack was spontaneous. (Confidence: low · ASSESSED)
   • I&W: A State Security Court record naming ISIS links between the Hammoud defendants and the al-Tuf targets would support the linkage; a final court account that identifies no such link would weaken it. (1-3 months)
4. The question of prior coordination between Jordan and Syria remains unresolved. The Jordanian army said the strikes were coordinated with Damascus; the Syrian government denied coordination or prior notification. Syria summoned Jordanian ambassador Sufian al-Qudah, issued a protest memorandum and announced a joint field and security committee. A subsequent joint statement expressed regret over civilian casualties and respect for Syrian sovereignty, but did not settle what notice was given before the strikes. (Confidence: medium · ASSESSED)
   • I&W: A joint committee finding that records prior notification would support Jordan's account; a Syrian or joint finding that no notice was given would support Damascus's account. (0-30 days)

Outlook & scenarios

Managed bilateral containment (55%)

Jordan and Syria are likely to keep the dispute in official channels through the announced joint field and security committee and continued ministerial contact. Amman's expression of regret and respect for Syrian sovereignty helps limit the immediate dispute, while leaving target identity and prior coordination unresolved.

Public dispute hardens (30%)

Daraa protests continue, and calls to close the Jordanian embassy in Damascus gain traction if the committee produces no findings or the civilian toll remains contested. The governments maintain formal contact, but public criticism constrains their ability to present the strikes as a shared security action.

Renewed cross-border escalation (15%)

An unlikely, high-impact path begins with a new armed incident on the Syria-Jordan border that Amman attributes to ISIS. A Jordanian response inside Syria, especially without agreed notification, would sharpen the existing dispute over sovereignty and risk further protests in Daraa.

Recommendations

1. Track public outputs from the Syrian-Jordanian joint field and security committee, with particular attention to prior notification, strike locations, target identification and civilian casualty figures.
2. Keep Jordanian statements about ISIS affiliation and target identity distinct from independently established findings. Update the assessment if State Security Court proceedings provide evidence linking the Hammoud defendants to the al-Tuf targets.
3. Monitor official statements and observable protest activity in Daraa, including renewed demands to close the Jordanian embassy in Damascus.
4. Maintain separate reporting lines for the strike's occurrence, casualty toll, target identity and coordination status. Do not treat evidence for one of these points as confirmation of the others.

Confidence & uncertainty

Overall confidence is high for the basic sequence of events: reporting from major media and a think tank places Jordanian strikes at al-Tuf on 26 October, while separate reporting covers the Hammoud attack and Jordanian court proceedings. Confidence is lower on the civilian toll, the ISIS identity of the targets, any link between those targets and the Hammoud defendants, and prior coordination. Jordan and Syria directly contradict one another on coordination, and the reporting does not resolve that dispute.

Intelligence gaps

• [EEI 1.2 · UNCOVERED] Changes in Jordanian force posture, border closures, air-defense deployments, or military alert levels along the Syria border. Recommended collection: official statements/local reporting
• [EEI 1.3 · PARTIAL] Jordanian government statements defining red lines, attribution standards, or conditions for additional strikes. Recommended collection: government statements
• [EEI 1.4 · UNCOVERED] New attacks on Jordanian territory, border personnel, security forces, or religious sites attributed to ISIS or Syria-based actors. Recommended collection: incident reporting/security services
• [EEI 2.1 · UNCOVERED] ISIS claims of responsibility, threats, operational instructions, or propaganda referencing the church attack, Jordan, or the retaliatory airstrikes. Recommended collection: militant communications
• [EEI 2.2 · UNCOVERED] Evidence of ISIS casualty, leadership, weapons, logistics, or command-and-control losses at the reported strike locations. Recommended collection: satellite imagery/intelligence reporting
• [EEI 2.4 · UNCOVERED] Attempts to move ISIS personnel, weapons, or facilitators across the Jordan-Syria border after the strikes. Recommended collection: border security reporting
• [EEI 3.1 · PARTIAL] Syrian government condemnation, military alerts, air-defense activity, or announced retaliatory measures against Jordan. Recommended collection: Syrian official statements/military reporting
• [EEI 3.2 · UNCOVERED] Military movements or operational changes by Syrian forces, Iran-aligned groups, or other armed actors near southern Syria and the Jordanian border. Recommended collection: satellite imagery/local security reporting
• [EEI 3.3 · UNCOVERED] Public or private diplomatic interventions by the United States, Russia, Gulf states, Israel, or Arab League members concerning the strikes. Recommended collection: diplomatic statements
• [EEI 4.1 · PARTIAL] Additional attacks, sectarian threats, protests, communal violence, or mobilization linked to the church attack or the airstrikes. Recommended collection: local media/social media
• [EEI 4.2 · UNCOVERED] Changes in border-crossing operations, refugee movements, commercial traffic, or humanitarian access between Jordan and Syria. Recommended collection: border authorities/humanitarian reporting
• [EEI 4.3 · UNCOVERED] Changes in travel advisories, embassy security measures, foreign force protection, or warnings concerning Jordan and southern Syria. Recommended collection: government advisories

Red cell review: CONCUR

TLP:CLEAR