The latest published intelligence briefing for each active theater, most active first. Every section links to the live theater view on the dashboard.

All 12 reporting threads across Gaza and the West Bank in the 24-hour window are single-sourced and unverified, but the geographic spread — with notable clustering in the South Hebron Hills and multiple West Bank flashpoints — marks a broad uptick against the 7-day baseline.

Reporting volume rose across nearly every sub-theater versus baseline, though every item is unconfirmed. Hebron governorate carried two separate threads: a settler attack on Palestinian homes and farmland in Umm al-Khair (Masafer Yatta) reportedly injuring six under IDF cover, and a broader settler-violence signal elsewhere in Hebron — a sharp shift from the 0.1/day baseline. In Gaza, threads include a reported drone strike on a refugee tent in western Gaza City, a claimed IDF strike killing a Hamas training commander in northern Gaza, and two overlapping reports of fresh strikes killing at least six amid described ceasefire violations. West Bank activity extended to a clash in Madama south of Nablus, house demolitions in Shuqba (Ramallah) with parallel raids and four detentions in Jenin, a reported attack on border police at Kalandiya, and a checkpoint incident in which an infant reportedly died after being denied passage. Inside Israel, a suspected ramming and Israeli fire on a vehicle were reported in Modiin, alongside a poorly-localized "Shifa, Ha'afon" fighting signal in the Northern District.

The pattern — if borne out — combines kinetic Gaza strikes described against a ceasefire backdrop with simultaneous settler-led escalation in the South Hebron Hills and multi-node West Bank friction (checkpoints, raids, demolitions). That mix historically stresses de-escalation frameworks more than Gaza-only activity.

Watch for second-source corroboration of the northern Gaza commander strike and the Gaza City tent strike; confirmation would indicate a material break in reported ceasefire conditions. Watch Masafer Yatta and Hebron for follow-on settler mobilization, and Kalandiya, Modiin, and West Bank checkpoints for repeat security incidents that would indicate a widening West Bank friction cycle rather than isolated events.

Ukrainian long-range and drone operations expanded into Russian rear areas — hitting the Kursk NPP-2 cooling tower, Belgorod gas pipeline infrastructure, and Azov Sea sanctioned tankers — while Russian combined missile/drone strikes across Ukrainian cities continued at baseline intensity.

Cross-border strike activity rose sharply against the 7-day baseline: Belgorod recorded two incidents (up ~186%) — a verified fire at the Belgorod Linear Production Directorate of Main Gas Pipelines, and a verified drone strike on a passenger bus on the Nikolskoye–Tavrovo road that injured six, including two children. Kursk registered a partial-confidence report (up ~233%) of 12 drones directed at Kurchatov, with one reportedly striking the cooling tower of the under-construction second unit at Kursk NPP-2; the regional governor stated operations were undisrupted. In the Sea of Azov, AFU Unmanned Systems commander Brovdi claimed strikes on eight sanctioned tankers, a dry cargo vessel, and a ferry allegedly moving fuel to Crimea — partially sourced and unverified in effect. Inside Ukraine, activity tracked at or below baseline: partial reports of Shahed/FAB strikes on Zaporizhzhia, Kryvyi Rih and Dnipro; a strike in Kharkiv reportedly killing a Nigerian medical student; and a nationwide missile/drone salvo with fighting reported in Kyiv, cited at 21 killed and 77 injured.

The concentration of Ukrainian strikes on Russian energy nodes (Kursk NPP-2, Belgorod gas directorate) and shadow-fleet tankers indicates continued pressure on Russian rear-area energy and logistics rather than frontline mass. The Belgorod bus incident raises civilian-harm exposure for Kyiv's cross-border campaign.

Watch for Rosatom or IAEA follow-up on Kursk NPP-2 — any radiological or structural confirmation would materially change the risk picture. Monitor Belgorod and Kursk for retaliatory salvos against Kharkiv and Sumy, which would indicate escalation linkage. Track independent confirmation of the Azov tanker strikes; vessel-tracking silence on the named hulls would corroborate Brovdi's claims.

Reporting over the past 24 hours points to a sharp uptick of activity around El Obeid/al-Abyad in North Kordofan, with over 5,500 children reportedly displaced, but every event in the period is single-sourced and unverified.

North Kordofan recorded four events against a 7-day baseline of 0.4/day, all unconfirmed. Save the Children reporting, echoed across two entries, describes 5,500 children displaced from the El Obeid/al-Abyad area amid fighting and drone attacks. A separate unverified claim attributes an RSF ground approach toward al-Abyad alongside SAF airstrikes, with RSF commanders also asserting continued control of Karmak under SAF siege. GDELT-derived signals — not independently corroborated — flag additional fighting inside El-Obeid itself. In North Darfur, a single unverified GDELT assault entry for El Fasher lifts the tally to one event against a 0.3/day baseline. West Darfur registers one unverified fighting entry with no prior baseline, though its linked reporting appears to recycle the El Obeid displacement figure, raising doubts about the geolocation.

If the El Obeid/al-Abyad cluster holds up, it would mark a westward pressure point on a SAF-held urban anchor in Kordofan and a significant civilian displacement event. The convergence of a displacement report, a claimed RSF advance, and reported SAF airstrikes is consistent with contested lines around the city, but no element is corroborated. The West Darfur entry should be treated cautiously given apparent sourcing overlap with El Obeid.

Watch for independent confirmation of the al-Abyad drone strikes and displacement figures; second-source reporting would upgrade confidence. Monitor whether SAF or humanitarian channels acknowledge fighting inside El-Obeid, and whether El Fasher reporting resolves into a specific incident. Renewed West Darfur sourcing distinct from the El Obeid thread would indicate a genuine second axis rather than a data artefact.

A cluster of single-sourced reports describes renewed Houthi ground pressure on the Hays front south of Hodeidah and a UKMTO-flagged maritime incident in the Red Sea off Al Hudaydah, all unconfirmed but consistent in geography and timing.

Al Hudaydah governorate registered four reported incidents in the 24-hour window against a 7-day baseline of 0.1 events/day, and the Red Sea off Al Hudaydah registered one event with no prior baseline. All five reports are single-sourced and unverified. Three separate reports place fighting on the Hays front south of Hodeidah — in the Dabas/Jabal Dubas mountains and Khokha district — with two of them describing the same reported Houthi assault on the 14th Infantry Brigade "Second Zaraniq" and 14 government soldiers killed, and a third claiming over 50 Houthi fatalities. A separate report from Hodeida city references a cargo ship reportedly attacked offshore. UKMTO Warning 080-26 reported a maritime attack in the Red Sea/Gulf of Aden area with no vessel, actor, or weapon specified.

If corroborated, the Hays-front reports would mark the first substantive ground engagement in the sector against a near-zero baseline, and the reported order for maximum readiness across Yemeni government military branches suggests the government side is treating it as a broader escalation rather than a local skirmish. A concurrent UKMTO maritime warning off the same coastline raises the possibility of coordinated land-sea pressure, but with all reporting single-sourced, the pattern is suggestive rather than established.

Watch for second-source confirmation of the 14th Brigade casualty figures and of Houthi losses in the Dabas mountains; independent corroboration would shift the Hays front from anomaly to active axis. Watch for UKMTO follow-up or shipping-industry identification of the vessel behind Warning 080-26; a named vessel or claim of responsibility would indicate a return to active anti-shipping operations off Hodeidah. Watch Yemeni government readiness posture beyond Al-Khawkhah for signs the alert is being operationalized.

Ukrainian long-range strikes reached unprecedented depth into Russia during the period, with the Ukrainian General Staff confirming a hit on the Omsk oil refinery (~2,500 km from the border) and drone warnings extending to Novosibirsk, alongside a separately reported strike on an unspecified major refinery linked to a domestic fuel crisis.

Activity shifted sharply eastward beyond the typical European Russia baseline. Omsk registered a partially corroborated strike on its oil refinery, confirmed by the Ukrainian General Staff and reported across three sources — a 150% spike over the 0.4/day baseline. Novosibirsk, roughly 1,900 miles from Ukraine, saw Russian Telegram channels warn of approaching attack drones, contextualised against the reported unveiling of Fire Point's FP-1 variant claimed to exceed 2,000-mile range; three sources, partial confidence. A third partial report references a strike on an unnamed "largest refinery" tied to worsening fuel shortages, with neither location nor attacker specified. All three events are partial, not verified.

The Omsk strike, if the General Staff claim holds, marks one of the deepest-penetration Ukrainian strikes on Russian territory recorded to date and extends the demonstrated threat envelope well past the Urals. The Novosibirsk warning, whether or not impacts are subsequently confirmed, indicates Russian air-defence and civil-warning postures now extend to Siberian population centres. The unattributed refinery strike, framed in Russian-language commentary as compounding an existing fuel crisis, points to downstream economic pressure on the domestic refining sector independent of any single event.

Watch for independent confirmation of damage assessments at the Omsk refinery; imagery or throughput reporting would indicate whether the strike produced sustained output loss. Monitor whether the Novosibirsk drone warning is followed by corroborated impact or debris reporting, which would substantiate the claimed FP-1 range. Track Russian-language commentary and fuel-price signals for identification of the unnamed refinery referenced in the fuel-crisis context.

A partially corroborated Iranian strike on an outbound loaded LNG tanker in the Strait of Hormuz on the night of 7 July marks the period's only reported incident and represents a sharp escalation in a chokepoint that had averaged 0.3 events/day over the prior week.

Activity in Hormozgan Province rose roughly 233% against the 7-day baseline, driven by a single partially verified event: Iranian forces reportedly attacked a laden LNG carrier transiting outbound through the Strait of Hormuz, setting the vessel ablaze (four sources, not fully verified). No further activity was reported across the other baseline hotspots — South Lebanon, West Azerbaijan, Erbil, the Red Sea off Al Hudaydah, Tehran, Quneitra, Kermanshah, or the Northern District — during the reporting window.

If corroborated, a direct Iranian engagement of a loaded LNG tanker in the Strait of Hormuz is a material departure from the harassment-and-seizure pattern that has characterised recent Hormozgan incidents. The Strait handles a significant share of global LNG and crude flows; a burning laden gas carrier in the transit lane raises immediate risks to co-transiting traffic, insurance and routing decisions, and the political threshold for a Gulf-state or extra-regional response. The partial confidence label is important — attribution and target type remain single-cluster and unverified in detail.

Watch for independent imagery or AIS reconstruction confirming the tanker's identity, cargo state, and the nature of the attack — corroboration would move the event from partial to verified and clarify whether this was a missile, UAV, or boarding action. Monitor IRGC Navy and Iranian state media messaging; explicit claim or denial would indicate intent. Watch war-risk insurance notices, VLCC/LNG rerouting around the strait, and any uptick in Bab el-Mandeb or South Lebanon activity, which would indicate a coordinated posture rather than an isolated incident.

Reporting for the 24-hour period is effectively null: a single unconfirmed assault report near Ashkelon is the only entry, insufficient to establish any verified change in the theater.

No verified or partially corroborated activity was recorded across Israel during the period. A single-sourced, unconfirmed report referenced an assault event in the Ashkelon area of the Southern District late on 6 July, extracted from a GDELT-indexed news item with no actor, target, or weapon detail. This nominally represents a deviation from the Southern District's flat 7-day baseline, but the absence of corroboration means the shift cannot be treated as real. The Northern District, which carried a marginal 0.1 events/day baseline, produced no reporting in this window.

With zero verified events, the operational picture is one of reporting silence rather than confirmed de-escalation. The Ashkelon-area item, if later corroborated, would sit in a coastal southern zone historically sensitive to rocket fire and cross-border activity, but on current evidence it cannot support any assessment of intent, attribution, or intensity. Analysts should avoid treating the single data point as indicative of a trend.

Monitor for second-source corroboration of the Ashkelon-area report; independent confirmation from Israeli civil defence channels or local outlets would upgrade its status and warrant reassessment of Southern District activity. Watch the Northern District for any return to its low baseline, as a continued zero-reporting posture over multiple cycles would itself be notable. A sustained absence of verified events across both districts would indicate the current quiet is genuine rather than a reporting artefact.

Reporting for the period is thin: a single unconfirmed account of regime airstrikes on Mindat in southern Chin State is the only item on the wire, and it cannot be treated as established fact.

There is no 7-day baseline for comparison, so any activity registers as a nominal increase. The sole reported incident — a single-sourced, unverified claim of a Myanmar military air attack on Mindat town and a nearby village in southern Chin State, alleging one woman killed and ten houses destroyed, with a secondary reference to an earlier strike on Shaim village said to have killed three children — remains uncorroborated. No verified or partially corroborated events were recorded in the window.

With only one unconfirmed report, operational significance cannot be established from this period's data alone. If corroborated, continued regime air activity over Mindat would be consistent with the pattern of aerial targeting in Chin State's south, but drawing that link from a single post would overreach the evidence. The absence of any other reporting across the theater in a 24-hour window is itself notable and may reflect a collection gap rather than a lull.

• Watch for independent corroboration of the Mindat and Shaim strike claims from local Chin civil society, medical, or church-linked channels; secondary confirmation would move this from rumor to a documented incident.
• Watch for imagery or damage assessments of the ten reportedly destroyed houses in Mindat; their appearance would indicate the strike occurred broadly as described.
• Watch for follow-on regime air activity elsewhere in southern Chin State; a cluster would indicate a deliberate campaign rather than an isolated sortie.
• Watch for the reporting drought across other states to break; continued silence would point to a collection or connectivity problem rather than a genuine quiet period.

A single unconfirmed strike signal referencing a port oil terminal in the Leningrad region — geocoded to Pskov — is the only reported activity in the period. No verified or partially corroborated events.

Reporting volume rose from a zero baseline to one event, all of it unconfirmed. A single-source, single-sourced GDELT signal describes a Ukrainian drone strike on a port oil terminal, dated 07 July. The geocoding places the event in Pskov, but the underlying article headline refers to a target in the Leningrad region — a geolocation discrepancy that is unresolved. No damage assessment, no operator claim, and no corroborating imagery or secondary reporting are present in the input.

If the Leningrad-region reading is correct, a port oil terminal strike would extend the pattern of long-range drone targeting against Russian energy-export infrastructure along the Baltic approaches. If the Pskov geocoding is correct, it would instead indicate targeting deeper along the NATO flank corridor. Because the report is single-sourced and internally inconsistent on location, neither interpretation can be advanced from the input alone. The absence of any baseline activity in the preceding week means this signal has no local pattern to anchor against.

• Watch for secondary reporting (Russian regional officials, port authority statements, shipping notices) that would resolve whether the target sits in Leningrad oblast or Pskov.
• Watch for imagery or fire/smoke geolocation from either area; confirmation at a named terminal would upgrade the signal from unconfirmed.
• Watch for Ukrainian claims of responsibility, which would indicate deliberate targeting of Baltic-facing export nodes rather than incidental routing.
• Continued silence across Russian and Ukrainian channels over 72 hours would indicate the initial report is likely spurious or misgeocoded.

A verified explosion near the Four Seasons Hotel in central Damascus on 7 July marks the only reported incident of the period and lifts Damascus activity above its 7-day baseline.

One verified strike occurred in the vicinity of the Four Seasons Hotel in central Damascus at 07:53 UTC on 7 July, with at least one vehicle reported burning and no casualties stated. This single event places Damascus roughly 67% above its 7-day baseline of 0.6 events/day, while As-Suwayda, Deir ez-Zor, and Rif Dimashq recorded no reported activity during the window. The incident is corroborated across eight sources. No follow-on strikes, claims of responsibility, or attribution details are present in the event set.

The Four Seasons sits in a high-visibility district of central Damascus associated with diplomatic, media, and government-linked foot traffic. A daylight explosion in that immediate vicinity — even without casualties — is operationally significant because of the location's symbolic weight and the concentration of sensitive infrastructure nearby. With only one verified event and no supplied attribution, the incident should be treated as a discrete data point rather than evidence of a broader pattern shift across the theater.

• Watch for follow-on reporting from central Damascus that would clarify device type, target, or attribution; emergence of a claim would indicate a deliberate targeting logic rather than a spillover incident.
• Monitor whether additional incidents occur in the Four Seasons/central Damascus corridor; a second event in the same district would indicate a sustained campaign rather than an isolated strike.
• Watch quiet oblasts (As-Suwayda, Deir ez-Zor, Rif Dimashq) for any reporting; renewed activity there would indicate the Damascus incident is not the sole locus of near-term escalation.

The reporting period yielded no verified or partially corroborated incidents in Venezuela. A single unconfirmed assault signal near La Guaira is the only item of note and does not, on its own, support any assessment of changing conditions.

No baseline activity exists for the prior 7 days, and no verified events occurred during this period. The only input is a single-sourced, unconfirmed assault signal in La Guaira (Vargas) dated 5 July, derived from a GDELT CAMEO-18 tag with three mentions and negative tone. This is a machine-generated indicator, not a corroborated incident, and cannot be treated as a meaningful delta against an absent baseline.

With zero corroborated events, there is no operational or strategic shift to characterize this week. The Vargas signal is notable only because La Guaira hosts Venezuela's principal international airport and main Caribbean port complex, meaning any confirmed security incident in that corridor would carry outsized logistical significance. Absent corroboration, however, the signal warrants monitoring rather than analytic weight.

• Watch for second-source reporting on the 5 July La Guaira assault signal; corroboration from local outlets or official statements would elevate it from a GDELT artifact to a trackable incident.
• Monitor Vargas state security and port-authority channels for any references to disturbances around Maiquetía or the port; silence over the next 72 hours would suggest the initial signal was noise.
• Track whether additional CAMEO-18 signals cluster along the central coast, which would indicate an emerging pattern rather than an isolated data point.