Israel widens strike footprint to Hamadan as India tells citizens to leave Iran
Indian diplomatic missions in Iran began telling their nationals to leave the country on Monday morning UTC, as multiple open-source intelligence channels reported Israeli airstrikes on the western Iranian city of Hamedan. The strikes, reported between 08:22 and 08:28 UTC on 8 June 2026, hit the town of Kabudarahang in Hamadan Province, where the long-established Shahrokhi airbase sits. The Indian advisory, circulated through the same Telegram channels in the minutes that followed, marks a notable widening of the diplomatic ring around Tehran.
Three things converged in a forty-minute window. Israel widened its strike footprint into western Iran, hitting what one channel identified as a Basij checkpoint in a town adjacent to a known airbase. India — long a careful balancer between Tehran and the Gulf monarchies, and one of the few large countries still operating a routine diplomatic presence in the Islamic Republic — told its citizens to get out. Iran's air defence network, the same one that has been visibly stressed by months of strikes, was activated again, publicly and in real time, against an Israeli package that this time reached deeper into the country's interior.
A wider footprint inside Iran
The strikes landed on Kabudarahang, in Hamadan Province, between 08:22 and 08:28 UTC on 8 June 2026. The Telegram channels English Abuali, Abuali Express, AMK Mapping and RN Intel all reported hits in the area within minutes of one another. RN Intel specified the target as a Basij checkpoint; AMK Mapping framed the strike as directed at the town where Shahrokhi airbase sits. Iranian air defence systems were activated in response, according to the same channels.
The geography matters. Kabudarahang sits deep in western Iran, well inside the country's strategic depth, and its proximity to Shahrokhi — a base that has hosted Iranian fighter, transport and drone operations for decades — gives Israeli planners a reach that, until now, they have used sparingly. Earlier rounds of strikes concentrated on the eastern frontier, the Tehran periphery, and the missile and drone production corridors of the central plateau. A confirmed hit in Hamadan Province pushes the operating envelope further west, deeper into the country's industrial and military rear, and closer to the Kurdish borderlands, where the geography of Iranian air defence is thinner and the political optics of damage on the ground are different.
The air-defence activation is also a story in itself. It tells readers that the strike package was visible to the Iranian chain of command early in its trajectory, that Iran's defenders were put on the back foot but not bypassed, and that the regime was willing to acknowledge, through the immediate churn of Telegram traffic, that something had happened. Earlier in the year, when strikes landed further east, the gap between the actual event and the regime's public confirmation stretched into hours. Monday morning, the confirmation came in minutes.
India steps out of the middle
The Indian advisory is the under-reported half of this story. It was issued by New Delhi's embassy network and circulated through the Telegram channels beginning at 08:29 UTC, urging Indian citizens to leave Iranian territory. The advisory is a posture, not a procedural note. It signals that Indian intelligence services believe the probability of further strikes, including in places where Indians live and work, has crossed a threshold that makes evacuation a lower-cost option than waiting.
New Delhi has spent two decades calibrating its Iran relationship. The pillars are familiar: discounted crude oil under narrow sanctions windows, the Chabahar corridor project that bypasses Pakistan, a large Iranian-Indian commercial and diaspora community, and a quiet diplomatic line to Tehran that has survived American pressure, Israeli action, and the slow drift of the regional order away from middle-power neutrality. A blanket advisory to leave is the first time in the current escalation cycle that India has treated Iran the way Western embassies have been treating it for the better part of a year: as a place to be departed from, not posted in.
The diplomatic read is the easy one. The structural read is harder. The Indian mission in Tehran and the smaller posts in Bandar Abbas and the northeast will now operate under the same logic that has governed Western missions: get people out before something forces the issue. Each evacuation notice issued by a mid-sized embassy is a small admission that the previous equilibrium no longer holds. The cumulative effect, as more countries issue similar advisories in the days ahead, is a quiet collapse of the diplomatic perimeter that the Iranian regime has historically relied on to project normalcy to its own population and to the region.
What was hit, and what the sources do not confirm
The Telegram sources diverge in a way worth flagging, because the divergence will shape how this strike reads in Tehran and in the wider region. RN Intel reports a strike on a Basij checkpoint in Kabudarahang. AMK Mapping frames the strike as aimed at the town where Shahrokhi airbase sits. These are not necessarily contradictory: a strike package can hit a Basij position on the approach road to a military installation, or it can hit a position that overlooks the base. But the framing difference — checkpoint versus airbase — has consequences for downstream coverage.
If the target was a Basij checkpoint, the strike is a security-force pinprick, aimed at the paramilitary arm that polices Iranian cities and restrains domestic unrest. If the target was infrastructure at or around Shahrokhi, the strike reaches into the regular Iranian military's rear echelon and into the kind of base from which Iran would launch any future strike of its own. Both reads are plausible. Neither is confirmed by any source in this thread, and no casualty figures have yet been published by either side.
What is also missing: official Israeli confirmation, official Iranian admission, the type of aircraft or munitions used, and the broader strike-package count for the night. The Telegram channels that are the only available sourcing right now operate with the standard caveats of wartime open-source reporting — fast, often accurate on the basics, frequently wrong on the details, and prone to picking up the first available framing without correcting it. Monexus is reporting the strike and the Indian advisory on that basis, and will update as official Israeli, Iranian and Indian statements emerge.
Stakes
The narrow read: Israel is signalling that no provincial capital in western Iran is outside the geometry of its strike planning. Iran is signalling, by activating air defences and letting the world see them do it, that it intends to keep responding, however unevenly. India is signalling that it is no longer willing to ride out the next phase inside Iran, even at the cost of the careful neutrality it has spent two decades constructing.
The wider read is the one Monexus finds more telling. The regional architecture built to keep a single round of escalation from cascading — back-channels, oil-market management, the careful neutralities of middle powers like New Delhi, the unwritten understanding that provincial Iranian towns were not in the operating envelope — is being hollowed out one advisory at a time. Each strike on a provincial Iranian town is a small admission that the previous geography of restraint no longer applies. Each evacuation notice from a mid-sized embassy is a small admission that the diplomatic perimeter around Tehran is contracting faster than anyone in 2025 expected.
What remains uncertain is the trajectory from here. The Telegram sources do not specify whether further strikes are planned for the next twenty-four hours, whether Iran intends to respond through the Strait of Hormuz or through its regional proxy network, or whether the Indian advisory will be followed by similar notices from other countries with large diasporas in Iran. The Monexus desk will update as official Israeli, Iranian and Indian statements emerge, and as wire reporting catches up with the open-source record.
Desk note: Monexus frames this as a widening of the strike footprint, not as a one-off operation. The Indian evacuation advisory is the under-reported half of the story; mainstream wire coverage has so far led with the strike itself.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/englishabuali
- https://t.me/abualiexpress
- https://t.me/englishabuali
- https://t.me/AMK_Mapping
- https://t.me/abualiexpress
- https://t.me/rnintel