Strikes on Sulaymaniyah: Why Iran hit a PUK Peshmerga depot, and what that says about its Kurdish file
Initial reports framed the July 17 drone strikes on Sulaymaniyah as a hit on Kurdish opposition groups. A clearer picture now points to the depot of the PUK-affiliated 70th Unit of the Kurdistan Region's Peshmerga. The gap between the two readings is the story.

At roughly 19:02 UTC on 17 July 2026, Iranian drones hit ammunition depots in the Sulaimani and Tasluja area of the Kurdistan Region of Iraq. The first reporting identified the targets as Kurdish opposition positions. By the time the dust had cleared, the picture was tighter, and more awkward: the struck depot in Sulaymaniyah belongs to the Peshmerga forces of the Kurdistan Region's 70th Unit, a formation affiliated with the Patriotic Union of Kurdistan (PUK) rather than with the Tehran-targeted Kurdish opposition exile groups long accused by Iran of fomenting unrest inside the Islamic Republic. (Monexus has not independently corroborated the precise unit designation.)
That single correction reframes the strike. It does not change the fact of Iranian firepower reaching into Iraqi territory, which Tehran has done many times before. It changes the question. A strike on a Kurdish opposition depot reads as a familiar extension of the Islamic Republic's regional security doctrine: reach hostile groups wherever they hide. A strike on a PUK-linked Peshmerga depot reads as a warning closer to home, sent across the Green Line to a Kurdish-Iraqi party that co-governs the Kurdistan Region with the Kurdistan Democratic Party (KDP), and that maintains ties with Iran that have historically been warmer than Washington's.
The wire cycle made the misidentification first and the correction second, which is itself worth a paragraph. Telegram channels monitoring Iranian and Iraqi military traffic moved on the strike within minutes. They called the target what the launch pattern and the geography seemed to point at: the eastern mountain belts where Iranian Kurdish opposition parties have long sheltered. Only when imagery and field contacts fed in did the cleaner picture of a 70th Unit depot inside the Sulaymaniyah operational zone emerge. The sequence is a small lesson in how fast the initial frame around a strike can lock in, and how slowly it moves once it does.
The two Sulaymaniyahs
Sulaimani (the city) and the surrounding Sulaymaniyah Governorate sit on the eastern edge of the Kurdistan Region, with Iran's West Azerbaijan province on the other side of a mountain frontier that ranges are not much of a barrier to a low-flying Shahed-type drone. The province is the PUK's political heartland. The Peshmerga forces of the Kurdistan Region's 70th Unit are part of the regional government's internal security architecture under the Kurdistan Region's Ministry of Peshmerga Affairs; the PUK and the KDP each maintain their own affiliated formations, with the two parties also holding joint duty in disputed areas under post-2014 arrangements.
Iranian strikes over the past decade have a clear target-of-opportunity preference: Kurdistan Workers' Party (PKK) rear bases in the Qandil mountains further north; Komala, PJAK and other Iranian Kurdish opposition positions scattered through border villages; and, more occasionally, camps and logistics hubs linked to the Iraqi Kurdish parties themselves when Iran believes they have overstepped. The 70th Unit designation sits inside the regional Peshmerga order of battle rather than inside any exile-opposition roster, which is what makes the reading from the second wire item a politically loaded one. A PUK-aligned Peshmerga depot is not the same kind of target as a Komala or PJAK safe house, and Tehran knows the difference.
That knowledge did not stop the strike.
Why now
The timing question matters more than the target one. In the absence of any reported direct Iranian-Iraqi incident in the preceding forty-eight hours, the more economical reading is that the strike is one increment inside a longer-running Iranian pressure campaign against Kurdish-on-Kurdish violence that flares whenever Tehran feels its western periphery tightening. Several threads run in parallel inside that campaign.
First, the opposition-into-Iran track. Tehran has long accused Iraqi Kurdish territory of hosting the movements it blames for unrest inside its northwestern provinces. Drones, artillery and IRGC ground teams have hit those targets repeatedly since at least the late 2010s. A strike on a PUK Peshmerga depot would, on that reading, be either a misidentification elevated to a strike, or a deliberate signal that operational zones inside the Region are not as off-limits as Erbil and Sulaymaniyah might prefer.
Second, the Iraqi sovereignty track. Baghdad's federal authority over its own territory is, in practice, more constrained in the Kurdistan Region than anywhere else in the country. Iranian fire crossing into Iraq at will, particularly fire that does not produce a phone call between the prime minister's office in Baghdad and the foreign ministry in Tehran, underlines that constraint in a way diplomatic memoranda cannot. The PUK's particular relationship with Tehran, through historical exile networks and through a senior PUK figure who was long a fixture in Iranian-Iraqi back-channel dealings, partly explains why Baghdad has less room than it would like to protest.
Third, the message-track. If the target was what the second wire item says it was, the message Tehran is sending is not to the PKK or to Komala. It is to the PUK: do not assume that standing between Washington and Tehran buys you a perimeter. The PUK has been courted by successive US administrations looking for cooperators in Iraqi Kurdistan who are not the KDP. A strike on its Peshmerga territory tells those cooperators what the cost of non-cooperation with Tehran can look like in physical terms.
What the opposition groups are not
It is worth being precise about what the initial framing got wrong, and what it got right.
The initial framing got right that Iranian drones did strike in the Sulaimani and Tasluja area on 17 July. It got the geography and the platform correct. It got wrong the institutional affiliation of the target when it identified the depot as belonging to Kurdish opposition groups. That identification is not pedantic. Kurdish opposition parties are, in the Iranian state media register, the existential enemy in the northwest; Peshmerga units of a co-governing party of the Kurdistan Region are, in the same register, a foreign state that tolerates that enemy. The two designations carry different legal cover, different political consequences inside Iraq, and different signals to Washington, Ankara, and the Gulf.
The opposition groups the first wire likely had in mind are the ones Tehran routinely names: Komala, the PJAK (the PKK's Iranian franchise), and various smaller Iranian Kurdish exile formations whose presence in Iraqi Kurdistan is a long-running irritant in Tehran-Erbil relations. That Iran has hit those groups many times is well documented. That it hit one of them on 17 July is what the second wire item pushes back on, saying the actual target was a PUK Peshmerga depot of the 70th Unit.
What the sources do not say
Three things remain genuinely unclear on the available reporting.
Casualty and damage figures from the strike are not specified in the wire items this article is built on. No death toll, no depot inventory loss, no operational impact on Peshmerga readiness. The first wire item references wounded reports it does not fully cite; the third wire item describes the target affiliation and does not get to effects.
Iranian state media's account of the strike is not in the record this article has access to. Mehr, Tasnim, IRGC-affiliated outlets and PressTV will, by long habit, eventually publish a statement taking credit if Tehran chose to claim the operation. Until they do, the silence is itself information.
Whether Baghdad, Erbil, or the Kurdistan Region's Council of Ministers has issued a formal protest, demanded an explanation, or summoned the Iranian chargé d'affaires is also not in the available record. The pattern after previous strikes inside the Region has been a ritual of protest that is filed away in Ankara, Riyadh and the corridors of the UN Security Council without a follow-up. Whether 17 July repeats that pattern or breaks it is a question worth waiting on, not guessing at.
What it adds up to
The structural reading is the more useful one. The Islamic Republic has spent fifteen years refining a doctrine of remote denial along its western border, using a mix of IRGC ground operations, ballistic and cruise missile strikes, and drone swarms to extend the reach of its security perimeter into Iraqi territory. That doctrine treats the Kurdish Region as a graduated space: more or less permissible to hit depending on what is there and who is reading the signal. Strikes on opposition parties are routine, almost bureaucratic. Strikes on Peshmerga units of a governing party are the upper end of the ladder, used sparingly because they cost Iran relationships it would prefer not to jeopardise.
If the target was indeed the 70th Unit, the cost calculus on the Iranian side has shifted. Either Tehran calculates the PUK is owed a reminder; or it has accepted the diplomatic bill for one more breach of Iraqi sovereignty with no expectation of paying it; or the strike was, despite the affiliation, intended as opposition-target work and missed. The first two are strategic choices; the third is a different kind of policy, the kind that erodes Iranian intelligence credibility inside Iraqi Kurdistan more than any protest note ever could.
Either way, the next seventy-two hours matter more than the past twenty-four. Watch for an Iranian claim, a PUK statement, and an Iraqi federal protest note, in roughly that order of arrival. They will tell you which of the three readings Tehran is operating under. Until they land, what we know is narrow: Iranian drones hit ammunition depots near Sulaymaniyah on 17 July 2026, and the depot in Sulaymaniyah itself belonged to a PUK-affiliated Peshmerga unit rather than to the Kurdish opposition groups the first wave of reporting named.
That gap, between the first frame and the corrected one, will outlast the news cycle. Frames travel faster than corrections. By the time the slower version of the story circulates, the easier version is already in the air. That asymmetry is, in its own right, part of how the region works.
Desk note: Monexus built this account from three wire items posted to Telegram on 17 July 2026 by BellumActaNews, treating the second item as the corrective frame rather than the first. Iranian state-media claims, Iraqi federal statements, and PUK official communiqués are not yet in the public record this piece can verify and have been left out rather than guessed at. We will update as they land.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/BellumActaNews
- https://t.me/BellumActaNews
- https://t.me/BellumActaNews
- https://en.wikipedia.org/wiki/Sulaymaniyah_Governorate
- https://en.wikipedia.org/wiki/Patriotic_Union_of_Kurdistan
- https://en.wikipedia.org/wiki/Peshmerga
- https://en.wikipedia.org/wiki/Kurdistan_Region
- https://en.wikipedia.org/wiki/Party_of_Free_Life_of_Kurdistan
- https://t.me/BellumActaNews
- https://t.me/BellumActaNews
- https://t.me/BellumActaNews
- https://en.wikipedia.org/wiki/Sulaymaniyah_Governorate
- https://en.wikipedia.org/wiki/Patriotic_Union_of_Kurdistan
- https://en.wikipedia.org/wiki/Peshmerga
- https://en.wikipedia.org/wiki/Kurdistan_Region
- https://en.wikipedia.org/wiki/Party_of_Free_Life_of_Kurdistan