The fence at Sunjuwan was breached in the dark, and the people who breached it did not walk toward the armoury or the operations room or the watchtower. They walked toward the family quarters. That single directional choice, the choice to turn left rather than right after entering an Indian Army cantonment in the small hours of 10 February 2018, is the entire moral shape of what happened next. Seven people died at Sunjuwan over the next thirty-six hours. One of them was a four-year-old child. The fidayeen who carried this out were Lashkar-e-Taiba cadres, and the man who planned and dispatched them, a former Hizbul Mujahideen field commander turned LeT-aligned launch handler named Khwaja Shahid alias Mian Mujahid, would walk free across the Line of Control and live for another five years in Pakistan-occupied Kashmir before his decapitated body turned up in a roadside drainage culvert near Naseerabad in October 2023. The five years between the breach and the body are the period this article reconstructs.

The Sunjuwan attack matters for reasons that exceed its casualty count. Sunjuwan was the first major fidayeen breach of an Indian Army installation after the Uri attack of September 2016 and the surgical strikes that followed it, a sequence that India had publicly framed as the moment doctrine changed. Eighteen months later, four LeT cadres in Pakistan Army-issue combat fatigues climbed a perimeter fence on the outskirts of Jammu and demonstrated that the doctrinal change had not closed the operational window. They demonstrated more than that. By turning toward the family quarters rather than the operational core of the camp, they signalled that the rules of who counts as a target had been rewritten. A four-year-old becomes a target when the goal is not to disable a military function but to inflict pain that political leadership cannot ignore. The attack was a message addressed to the Indian state through its soldiers’ children. The Indian state heard the message, and the long, quiet response that followed produced Khwaja Shahid’s body in a culvert.

What follows is a reconstruction of the attack itself, an account of the mastermind whose name surfaced in the investigation, and an analysis of the five-year chain that connected one to the other. It is also an argument. The argument is that the Sunjuwan-to-Naseerabad chain is the clearest available statement of a doctrine the Indian state has adopted but never named, a doctrine under which the perpetrators of mass-casualty attacks on Indian soil have no statute of limitations, no jurisdictional sanctuary, and no expectation that the passage of years will produce safety. The doctrine is implemented through the same operational architecture that produced the Rawalakot mosque killing of Abu Qasim and the methodology pattern that defines the broader campaign, but in Shahid’s case, the methodology adapted to terrain. The motorcycle and pistol could not reach a man whose movements were confined to the LoC’s western approaches. So the methodology became something else, and the body was left where it could be found.

Background and Triggers

Sunjuwan is not a remote forward operating base. The 36 Brigade Headquarters camp sits on the southern outskirts of Jammu city, the winter capital of the erstwhile state of Jammu and Kashmir, fifteen kilometres from the international border with Pakistan and connected to the city centre by a single arterial road. The camp houses the brigade’s command staff, its administrative apparatus, attached units of military police and engineers, and, critically for what happened in February 2018, the family quarters that house the wives and children of officers and jawans posted to the brigade’s units. In Indian Army cantonment design, the family quarters are placed inside the perimeter fence on the assumption that the perimeter is the security boundary. Inside the wire, families are presumed safe. The Sunjuwan attack inverted that assumption.

Jammu’s strategic geography matters here because the city is the only major Indian population centre in the Jammu region of the former state, and because the southern approaches to Jammu run almost directly to the Pakistani town of Sialkot, sixty kilometres away across the international border. Sialkot is the operational base of multiple LeT and JeM launch coordination cells, a fact extensively documented by Indian intelligence and by Western analysts including Stephen Tankel in his book on LeT’s organisational structure. The Sialkot-Jammu axis is shorter and operationally easier than the Muzaffarabad-Srinagar axis that defines the Kashmir Valley infiltration corridor, and it allows handlers to insert cadres directly into the plains of Jammu rather than requiring them to traverse the high passes of the Pir Panjal range. Sunjuwan sits at the receiving end of that axis. The 36 Brigade is the formation responsible for ground holding in this sector, and its families are the most concentrated population of military dependents in the region.

The triggers for the attack lie in the eighteen months that preceded it. The September 2016 Uri attack, in which JeM fidayeen killed nineteen Indian soldiers in their tents, had produced the publicly acknowledged surgical strikes across the Line of Control by Indian Para Special Forces, a response that the Indian government framed as a doctrinal shift away from strategic restraint. Through 2017, that framing was tested. The Indian state expected that the surgical strikes would produce a deterrent effect on Pakistan-based handlers. Pakistan-based handlers responded by accelerating rather than pausing. The number of attempted infiltrations along the LoC rose through 2017. The number of encounters between security forces and infiltrators in the Kashmir Valley rose. The Indian Army’s own assessment, as carried in the official annual report of the Ministry of Defence for that year, recorded that the operational tempo on the western front had increased rather than decreased after the surgical strikes. The deterrent effect had not materialised, and the escalation that followed culminated in Sunjuwan.

There is a second set of triggers, more specific to LeT. Through 2017, the organisation was under acute pressure inside Pakistan, with Hafiz Saeed under house arrest and the Falah-e-Insaniat Foundation, the LeT charity front, facing FATF-driven scrutiny over funding flows. LeT’s leadership made a strategic decision to demonstrate operational continuity in Indian Kashmir, both to maintain credibility with the cadre base and to signal to Pakistani security agencies that the organisation remained operationally indispensable to Pakistan’s covert posture against India. The decision found expression in a cluster of attempted attacks across late 2017 and early 2018, of which Sunjuwan was the most consequential. The attack was not, in the analysis of Indian intelligence and corroborated by South Asia Terrorism Portal director Ajai Sahni, a freelance operation. It was an organisational statement, executed by a cell that had been launched through Sialkot, equipped with Pakistan Army-issue webbing and ammunition, and dispatched against a target whose value lay precisely in the families it housed.

The choice of Sunjuwan over a forward post or a higher-altitude target reflected an operational calculation. Forward posts in Kashmir had hardened considerably since Uri. The defensive arrangements at Uri had been reviewed and replicated across the Valley. By contrast, rear-area cantonments in the plains of Jammu had not been subjected to the same hardening regime. Sunjuwan was a soft target by comparison, accessible by foot from the Sialkot launching pads, and its family quarters offered a casualty pool whose political effect would exceed its military significance. The cell that walked toward those quarters in the early hours of 10 February 2018 was choosing the soft target deliberately.

The fourth trigger is the date. The attack occurred on the ninth of February by some accounts and the tenth by others, the discrepancy reflecting the time the perimeter was breached, late on the ninth, versus the time the firefight became visible to the brigade as a whole, in the early hours of the tenth. Whichever date is used, the timing carries a coincidence that Indian commentators noticed and that LeT’s own propaganda subsequently exploited. Five years earlier, on 9 February 2013, Mohammed Afzal Guru, the Kashmiri convicted in connection with the 2001 Indian Parliament attack, had been hanged at Tihar Jail in Delhi. The fifth anniversary of his execution fell on the night of the Sunjuwan breach. LeT spokesmen in subsequent claims of responsibility framed the attack as a commemorative action. The framing serves their narrative purposes, but it also illustrates how operational planning inside Pakistani-based jihadist organisations integrates symbolic dates into target selection. The handlers in Sialkot did not pick the night at random.

The Pre-Dawn Assault

By the most reliable reconstruction available from Indian Army press briefings, NIA charge-sheet documentation filed in subsequent years, and reporting from defence correspondents including Ajai Shukla, the cell that breached Sunjuwan consisted of four cadres carrying a substantial loadout designed for sustained engagement. Each cadre carried an AK-series automatic rifle, multiple magazines, hand grenades, and underbarrel grenade-launcher rounds. Three of the four wore tactical webbing of a pattern issued by the Pakistan Army to its Special Service Group, a detail that Indian forensic teams subsequently photographed and entered into evidence. The webbing carried Pakistani markings that had not been removed, an oversight that would later feature in the Indian government’s diplomatic representations. Each cadre also carried a small quantity of dried fruit, a personal water supply, and a copy of selected verses from the Quran, a kit configuration that LeT had standardised for fidayeen operations since the early 2000s.

The breach point was on the southern perimeter of the camp, a section of fence line that ran along an unlit drainage line. The cell approached on foot from cover provided by sugarcane fields adjacent to the cantonment boundary. The fence at that section consisted of a single concertina coil mounted on a chain-link backing, a configuration that served as a deterrent rather than a barrier. The cell cut through the chain-link with bolt cutters at a point where ground depression and vegetation made the cut invisible from the nearest watchtower. The breach occurred at approximately three in the morning. There was no contact at the breach point. The cell entered the cantonment without alerting the perimeter guards.

What happened next is the operationally critical decision. Once inside the wire, the cell did not move toward the brigade headquarters building, the operations room, the armoury, or the vehicle park. Each of these targets would have produced a higher tactical effect on the brigade’s combat capability. The cell turned south-east, away from the operational core, and moved toward the residential blocks that housed the families of officers and jawans of the units attached to the brigade. They covered approximately four hundred metres of internal cantonment ground in this direction without being intercepted, exploiting the gap in internal patrolling that exists in most Indian Army cantonments between the perimeter sentry duty and the dispersed quarter guard duty at residential blocks.

The first contact with the cell occurred at approximately four-thirty in the morning, when a sentry on duty at the entrance to one of the residential blocks observed armed personnel approaching. The sentry challenged. The cell responded by opening automatic fire and throwing grenades. The sentry was killed in the initial exchange. The shooting alerted the brigade’s quick reaction force, and within minutes elements of the QRF were converging on the residential block. The cell, however, had used the engagement window to enter the block itself.

Inside the block, the cell encountered Indian Army families in their quarters, in night clothes, in the small hours of the morning. The conduct of the cell at this point is the morally hardest material in this article, and the reconstruction relies on subsequent statements by survivors, by relatives of those killed, and by the brigade’s debriefing of personnel who responded to the engagement. The cell moved through corridors firing through doors. It threw grenades into rooms in which it could hear voices. It used family members as human shields when QRF elements approached the block. The cell’s pattern of fire indicates that it was attempting to maximise civilian casualties before the QRF could engage decisively. This is the conduct that the Indian Army subsequently described, in a press briefing by the General Officer Commanding the Northern Command, as targeting families. It was not collateral damage. It was the operational object.

The exchange at the residential block continued through the morning and into the afternoon of 10 February. The QRF, joined by elements of the 9 Para Special Forces battalion and reinforced by Para Commando teams flown in from outside the sector, established a cordon around the block and began the painstaking process of clearing it room by room. The cell had taken positions inside several residential units and was using the structural cover offered by reinforced concrete walls and steel-framed doors to fight a defensive engagement against troops who had to advance under continuous fire while attempting to extract civilian survivors. Two of the cell’s cadres were killed in the initial QRF response. The remaining two cadres were eliminated over the next thirty-six hours in a sequence of engagements that required the deployment of breach charges, grenade saturation of suspected positions, and at one point the use of an armoured vehicle to provide cover for an extraction team carrying out wounded children.

By the time the engagement was declared concluded on the morning of 11 February, seven Indian personnel and family members were dead. A Subedar of the Jammu and Kashmir Light Infantry was killed in the initial sentry exchange. A Naik was killed leading the QRF’s first attempt to enter the residential block. A Lance Naik was killed providing covering fire during the extraction of survivors. The father of a serving officer, an elderly retired soldier visiting his son’s family, was killed in his quarters by grenade fragmentation. A wife of a serving jawan was killed by automatic fire through a door. A second wife was killed sheltering children in an internal room. A four-year-old child, the son of a Naib Subedar, was killed by grenade fragmentation in the same room. The fourth cadre of the LeT cell was killed in the final clearance operation. Eleven other Indian personnel and family members, including two children, sustained injuries ranging from gunshot wounds to fragmentation injuries. The brigade’s official casualty list, released after the engagement, was the basis of the casualty count that subsequently entered the public record.

The Day of Battle and the Army Response

The thirty-six hours of the Sunjuwan engagement produced an unusual operational situation in which the Indian Army was fighting an enemy inside its own residential cantonment while attempting to evacuate non-combatants from the line of fire. The tactical complexity of the engagement is one reason the casualty count, while smaller than the casualty counts at Uri or at the 26/11 Mumbai engagement, was nonetheless higher than the Army’s initial assessment had projected. Clearing a residential block held by determined fidayeen who had positioned themselves in family quarters required techniques that ground-holding infantry battalions are not optimised for. The Army adapted on the fly, but the adaptation cost time, and the time cost lives.

The first operational decision the brigade commander faced, in the early morning hours of 10 February, was whether to attempt rapid clearance or systematic clearance. Rapid clearance would have meant pushing infantry into the block to engage the cell at close quarters. The estimated cost of rapid clearance, based on the brigade’s read of the cell’s preparation and equipment, was high in personnel terms but would have shortened the duration of the engagement. Systematic clearance, by contrast, would mean isolating the block, evacuating civilians from adjacent buildings, and using specialist Para SF teams to enter and clear with full engineering support. The systematic option would extend the engagement but reduce the cost. The brigade chose the systematic option, and the Northern Command endorsed the choice within the first three hours of the engagement.

The systematic clearance unfolded across three phases. The first phase was perimeter and isolation, conducted between approximately five-thirty and eight in the morning of 10 February. The brigade established an inner cordon around the residential block, evacuated families from adjacent quarters under covering fire, and identified the firing positions the cell was using inside the building. Two of the four cadres were eliminated during this phase, one by a sentry from a flanking position and one by a Para SF marksman who engaged through a window. The second phase was structured entry and clearance, conducted between approximately eight in the morning and the late evening of 10 February. Para SF teams entered the block in stacks, clearing one floor and then the next, encountering the surviving cadres in positions inside specific quarters. This phase produced the engagement’s most intense exchanges, the engagement in which the four-year-old child was killed, and the elimination of the third cadre of the cell. The third phase was final clearance and damage assessment, conducted through the night of the tenth and into the morning of the eleventh. The fourth cadre, who had taken position in a stairwell with substantial ammunition, was eliminated in this phase, and the block was declared cleared shortly after dawn on 11 February.

The personnel costs to the Army during the clearance reflected the difficulty of the operation. In addition to the seven killed, the Army acknowledged eleven wounded, with a smaller number of those evacuated to military hospitals in Jammu and Pathankot for surgical treatment. The Army’s own debrief, summarised in the General Officer Commanding’s press briefing on 12 February, identified three operational lessons. First, the perimeter security architecture at rear-area cantonments needed substantial revision, including the introduction of motion-sensor coverage of fence lines that had previously been considered low-risk. Second, the internal patrolling regime inside cantonments needed to assume that perimeter penetration was possible and to provide a layered detection capability inside the wire, particularly at the boundary between the operational core and the residential blocks. Third, the family quarter design itself required review, with the recommendation that internal hardened-shelter rooms be incorporated into new cantonment construction so that families would have a defensible position if a perimeter breach occurred. The third recommendation was the most consequential and the most slowly implemented. As of subsequent reporting through 2025, the hardened-shelter requirement had been implemented in some new cantonments but had not been retrofitted across the bulk of existing cantonment housing.

The Army’s communications during the engagement were managed through a controlled press posture, with the General Officer Commanding holding the only on-record briefing and brigade-level officers declining direct media engagement until the operation was concluded. The controlled posture had two effects. It limited the operational information disclosed during the engagement, which was tactically appropriate. But it also meant that the early public narrative of the attack was shaped by less authoritative sources, including unverified social media accounts that circulated misleading casualty figures and contested attributions of responsibility. The Indian Army subsequently regretted the gap between the engagement and the press briefing and adopted a faster public communication doctrine for subsequent fidayeen incidents.

The political response to the engagement followed the Army’s announcement of conclusion on 12 February. Defence Minister Nirmala Sitharaman, who had taken charge of the Defence portfolio four months earlier, visited the Sunjuwan camp and the Army hospital in Jammu where the wounded were being treated. Her statement at the camp, delivered to assembled brigade personnel and to the families of the killed, named LeT explicitly as the perpetrating organisation and identified Pakistan as the location from which the attack had been launched. She declared that Pakistan would pay for the attack and that the cost would be exacted at a time and place of India’s choosing. The phrasing was deliberate, and it would echo through the subsequent years. The operational architecture that produced the broader campaign of targeted killings against Pakistan-based handlers was already being assembled when she spoke. Sunjuwan added Khwaja Shahid’s name to the list it would work through.

The Seven Killed

The reconstruction of who died at Sunjuwan, in what circumstances, with what relationships to the Indian Army’s chain of command and to the families that surrounded them, is necessary because the names matter both individually and as a pattern. The pattern is a pattern of military families. Five of the seven killed were not combatants. Four of those five were the dependents of serving soldiers, present in the cantonment because cantonment housing is part of the Indian Army’s compact with the people who serve in it. The fifth was a retired soldier visiting his son. The remaining two were the soldiers killed in the initial defensive engagement, the Subedar at the sentry post and the Naik leading the first QRF entry. Together, the seven represent both the targets the cell intended to reach and the troops who fought to interpose themselves between the cell and those targets.

Subedar Madan Lal Choudhary, of the 1st Battalion of the Jammu and Kashmir Light Infantry, was the first to die. He was on duty at the sentry post nearest the residential block, conducting routine watch in the small hours, when the cell approached his position after their internal traverse from the breach point. He challenged the approach, observed armed personnel, and engaged with his service weapon. The cell responded with concentrated automatic fire and a grenade. He was killed in the initial exchange, but his fire produced the alarm that mobilised the QRF and slowed the cell’s penetration into the residential block by minutes that other personnel used to take families into hardened spaces. He had served in the JAKLI for twenty-two years.

Naik Mohammed Ashraf Mir, also of the JAKLI, was killed leading the QRF’s first attempt to penetrate the residential block. He had moved into the block under fire to reach a family that was sheltering in an internal room with a wounded child, and was killed by grenade fragmentation while attempting to evacuate them. His action enabled the family to be reached by a subsequent extraction team. He had served in the JAKLI for fifteen years and was from a village in Kupwara district of Kashmir.

Lance Naik Mohammed Iqbal of the same battalion was killed providing covering fire during the extraction of wounded survivors from the second residential floor. He had taken a firing position to allow casualty extraction teams to move through a corridor under fire, and was killed by automatic fire from a cadre who had positioned themselves in a kitchen of an adjacent quarter. He had served in the JAKLI for eleven years.

Naib Subedar Mohammed Ashraf, retired, was the elderly father of a serving officer of the brigade. He was visiting his son’s family for the period of school examinations and was sleeping in the family’s quarter when the cell entered the corridor. He was killed by grenade fragmentation that penetrated the bedroom door of the quarter. He had served thirty-one years in the Indian Army before retiring.

The two wives killed in the engagement were Sarwan Devi, the wife of a serving Naib Subedar, and the wife of a Lance Naik whose name the Army subsequently withheld at the family’s request. Sarwan Devi was killed by automatic fire that penetrated a corridor wall while she was attempting to move her children into an internal room. She was thirty-eight. The Lance Naik’s wife was killed sheltering two children in an internal room when a grenade was thrown through the door. She was thirty-one.

The four-year-old child killed in the engagement was the son of a Naib Subedar of the JAKLI. He was killed by the same grenade that killed the Lance Naik’s wife, in the same internal room in which she was attempting to shelter him and his sibling. The Indian Army subsequently withheld the child’s name from public communications at the family’s request. The acknowledgement that a four-year-old had been killed at Sunjuwan, however, was made on the record by the General Officer Commanding in his press briefing on 12 February, and the acknowledgement remains the basis of the casualty pattern this article reconstructs.

The pattern is the moral substance of the attack. Two soldiers were killed defending the residential block. Five non-combatants, including a child, were killed inside the block. The casualty ratio in itself is unusual for fidayeen attacks on Indian military installations, the historical pattern of which has produced higher uniformed-to-civilian ratios. Sunjuwan inverted the ratio. The cell’s behaviour inside the block, the grenades through doors, the use of human shields, the sustained fire into rooms in which the cell could hear voices, indicates that the inversion was operationally intended. This is the determination that subsequent Army assessments and Indian intelligence community documentation reached, and it is the determination that informed the strategic response of which Khwaja Shahid’s body in a culvert was eventually a part.

The Mastermind: Khwaja Shahid

The name Khwaja Shahid alias Mian Mujahid surfaced in the Indian investigation into the Sunjuwan attack within weeks of the engagement’s conclusion. The investigation, conducted by the National Investigation Agency in cooperation with the Jammu and Kashmir Police Special Investigation Group and with intelligence inputs from the Research and Analysis Wing, identified Shahid as the launch handler responsible for inserting the four-cadre cell across the international border from Sialkot to Jammu and for selecting Sunjuwan as the target. The identification rested on three categories of evidence. First, telephone interception data captured during the cell’s brief radio communications with a handler in Sialkot, traced to a Pakistani cellular number that had been previously associated with Shahid’s known operational signature. Second, debriefing of LeT cadres detained in unrelated operations in the Kashmir Valley over the following months, who placed Shahid in the chain of command that had launched the Sunjuwan cell. Third, the recovery from the bodies of the four cadres of personal effects and notebooks that contained route information consistent with launch from a node Shahid was known to control.

Khwaja Shahid was at the time of the Sunjuwan attack a thirty-eight-year-old Kashmiri originally from the Lolab Valley in Kupwara district of Indian Kashmir, who had crossed the Line of Control as a teenager in the early 1990s and subsequently risen through the ranks of Hizbul Mujahideen, the Kashmir-focused organisation aligned with the Jamaat-e-Islami in Pakistan. By the early 2000s he had moved into operational handling roles, coordinating infiltration of cadres across the LoC into the Valley. By the early 2010s he had transitioned into a multi-organisation handler role, coordinating launches for both Hizbul Mujahideen and LeT-aligned cells, a transition that reflected the increasing operational fusion between Kashmir-focused and Pakistan-based jihadist organisations under ISI coordination. He operated under the alias Mian Mujahid in jihadist communications and propaganda materials, a name that his obituaries in Pakistani jihadist outlets would subsequently use when his death was eventually reported.

His operational signature, as documented by Indian intelligence and corroborated by the open-source work of South Asia Terrorism Portal, was the launch of trained cadre teams across the international border in the Sialkot-Jammu sector and across the LoC in the Naseerabad-Kupwara sector. He was not a field operator. He did not personally cross into Indian territory. He was a handler, a man whose value to the Pakistani jihadist apparatus lay in his network of relationships with cadres on the Indian side, his familiarity with the terrain on both sides of the line, and his ability to time launches against weather and security cycles that would maximise the prospects of successful infiltration. His residence in Pakistan-occupied Kashmir, in the Naseerabad area of the Neelum Valley, placed him near the launching pads he coordinated, and his life there was lived openly under the protection of the Pakistan Army’s Northern Light Infantry, which exercises functional control over the Neelum Valley.

The decision to mount the Sunjuwan operation was, in the Indian intelligence community’s assessment, taken at a higher level than Shahid’s. The strategic decision was made by LeT’s central command in coordination with the ISI’s S-Wing, the directorate that handles non-state actor coordination. The selection of Sunjuwan as target was made at that level. Shahid’s role was operational. He was the handler who would receive the four cadres in Sialkot, walk them through the route plan, ensure their equipment loadout, brief them on the breach point, and coordinate their cross-border movement. He executed that role through January and into early February 2018, and on the night of 9 February he was on the Pakistani side of the border, in radio contact with the cell, providing real-time guidance through the breach and the internal traverse. The radio intercepts that placed him in the chain of command were captured during this real-time guidance.

The Indian government’s identification of Shahid as the Sunjuwan handler did not become a major public disclosure in the months after the attack. The identification was made formally in NIA filings, and Shahid’s name appeared in a subsequent designation of wanted handlers issued through Interpol channels, but the Indian state did not run a public-facing campaign against his name in the manner that it had run against Hafiz Saeed or Masood Azhar. The reasons for the relative quiet are operationally legible. Shahid was a launch handler, not a ceremonial figurehead. The state’s interest in him was operational, and the operational interest was best served by allowing him to remain in his routine in PoK rather than alerting him to the attention his name had received. His routine continued. He moved between Naseerabad, Athmuqam, and other locations in the Neelum Valley. He participated in the broader infrastructure of organisational sanctuary that LeT and Hizbul Mujahideen jointly maintained in the Pakistani-administered portion of Kashmir. He did not change his name, his location, or his pattern.

What he did do, in the years after Sunjuwan, was continue to handle launches. The 2019 Pulwama attack would bring JeM into the fidayeen spotlight and would eclipse LeT’s operational profile for a period, and Shahid’s role through 2019 and 2020 was reduced as the LoC saw enhanced Indian counter-infiltration efforts. By 2021 and 2022 he was again active, this time coordinating cells linked to LeT’s Kashmir cluster operations rather than the Jammu cluster operations that Sunjuwan had represented. He was, in the analysis of former RAW special secretary Rana Banerji, the kind of mid-tier operational asset whose value to the Pakistani jihadist apparatus exceeded his name recognition among Indian commentators. He was also the kind of asset whose elimination would, when it happened, send a signal that the Indian state’s reach extended beyond the marquee names into the operational tier on which sustained jihadist activity depended.

His connections within the broader network were dense. His PoK residence placed him within walking distance of the headquarters of the United Jihad Council, the umbrella body chaired by Syed Salahuddin that coordinates Kashmir-focused jihadist organisations from a permanent base in Muzaffarabad. He was a participant in the launching pad infrastructure that ran from Athmuqam through Chalhana to Keran on the LoC. He was known, through cadre debriefings, to have personal relationships with field commanders of multiple organisations, a network position that would later inform the Indian intelligence community’s reconstruction of how he came to be where he was when the Indian operation reached him.

The Five-Year Chain to PoK

Five years passed between Sunjuwan and the discovery of Shahid’s body. The five years were not empty. They were the period during which the Indian state assembled the operational architecture, the asset network, and the doctrinal endorsement that would, in October 2023, produce a body in a culvert. The reconstruction of those five years requires reading the Sunjuwan-to-Naseerabad chain against the broader timeline of India’s targeted-killings campaign, which began producing eliminations on Pakistani soil from early 2022 onward and accelerated through 2023 into a sustained operational tempo.

The first phase of the five years, from February 2018 to roughly mid-2020, was the period of capability assembly. The Indian intelligence community, building on the doctrinal authorisations that the September 2016 surgical strikes had implied, developed a capability to project violence into Pakistani territory through means other than uniformed military operations. The development was not visible to the public. It involved the construction of asset networks inside Pakistan, the cultivation of relationships with Pakistani citizens who could provide ground-level surveillance and logistical support, and the development of operational protocols that would minimise the exposure of Indian assets to Pakistani counter-intelligence. Through this period, the Indian state did not produce eliminations. It produced infrastructure. The Sunjuwan response was being built rather than executed.

The second phase, from mid-2020 to early 2022, was the period of pilot operations. The June 2021 car bomb near Hafiz Saeed’s residence in Lahore, an event that the Pakistani state attributed to Indian agencies and that the Indian state did not claim, was the first publicly visible operational expression of the new capability. The car bomb did not kill Saeed, but its placement and timing demonstrated capability and intent. Through the second half of 2021, intelligence-community work continued on the development of asset networks in PoK specifically, a sub-theatre that was operationally distinct from Punjab or Sindh because of its terrain and because of the dense Pakistan Army presence that defined civilian life in the Neelum Valley.

The third phase, from early 2022 onward, was the period of operational tempo. Saleem Rehmani in January 2022. Zahoor Mistry in March 2022. Through 2022 and into 2023, a sequence of eliminations on Pakistani soil produced a public pattern of motorcycle-borne shootings in Karachi, Lahore, and other Pakistani cities, a pattern that The Guardian’s January 2024 investigation would subsequently document at length. The pattern, as analysed in the modus operandi article, was tightly standardised: pillion riders on motorcycles, point-blank pistol shots, pre-rehearsed escape routes, no claim of responsibility. The standardisation was a doctrine. It was the product of operational protocols that the third phase had codified.

PoK, however, was a different theatre. The terrain of the Neelum Valley does not lend itself to motorcycle-borne shootings of the Karachi or Lahore variety. The Valley is a single river-bottom corridor flanked by high mountains, with the LoC running along ridge lines that face Indian-administered Kashmir. The civilian population is sparse. The Pakistan Army’s Northern Light Infantry maintains checkpoints at intervals along the Neelum Valley road. Operating in this terrain required adaptations that the Karachi and Lahore patterns did not need. The adaptations included longer surveillance windows, the use of local assets rather than insertion from outside, and methodologies that did not require a motorcycle escape route because no such route existed. When Abu Qasim was killed in Rawalakot in February 2023, the methodology adapted: a point-blank shot inside a mosque, no motorcycle, an escape on foot through a routine post-prayer crowd. PoK methodologies were specific to PoK. They were not the Karachi pattern.

By October 2023, when Shahid’s body would be recovered, the Indian operational architecture in PoK had matured to the point where it could reach a man whose movements were confined to a small geographic envelope around Naseerabad and Athmuqam. The exact mechanism of the operation that reached him is not, at the time of writing, publicly documented. The Indian state has not claimed responsibility. The Pakistani state has not produced a public investigation report. What is publicly documented is the discovery of the body, the condition in which it was found, and the brief window of details that PoK media reported before the story was suppressed by the Pakistani security establishment.

The body was found on the morning of 19 October 2023, in a roadside drainage culvert near Naseerabad in the Neelum Valley. The body was decapitated. The head was recovered separately, a short distance from the body. The body had been bound at the wrists and ankles with synthetic cord. The forensic indicators were consistent with the man having been kidnapped from his residence approximately two days before the discovery, held during the intervening period, and killed at a different location before the body was placed where it was found. The PoK police reported the discovery within hours of the body’s recovery, and the report briefly entered Pakistani media before being withdrawn from circulation. Pakistani jihadist outlets confirmed the identity of the deceased as Khwaja Shahid alias Mian Mujahid, identified him as a senior LeT-aligned handler, and circulated obituary materials that named him as a martyr of the Kashmir cause.

The method’s deviation from the Karachi-Lahore standard is the operational fact that distinguishes Shahid’s elimination from the broader pattern. The motorcycle-borne shooting protocol is built around the assumption that the target is reachable in a public space accessible by a vehicle and that the operation can be concluded within seconds. Shahid was not reachable in such a space. His routine, by this stage, was confined to his residence and to short walks within Naseerabad, all of which were observable by Pakistan Army personnel and most of which were not on streets accessible to motorcycle traffic from outside. The methodology that reached him was a different methodology. It involved the man being taken from his residence by people who could enter that residence without raising an alarm, held by them long enough for whatever questioning or processing was operationally required, and killed by them by means that produced the body in the condition in which it was found.

The condition of the body, in the analysis offered by Ajai Sahni of the South Asia Terrorism Portal, served two purposes. First, it produced unambiguous identification. A decapitated body, properly documented, is a body whose elimination cannot be denied or mistaken. Second, the placement of the body in a public location, in a culvert beside a road that PoK residents and Pakistan Army patrols both used, produced a public message. The message was visibility. The Indian state, in this reading, had reached a man whose movements were nominally protected by the Pakistan Army’s presence in the Neelum Valley, and the placement of his body announced that the reach was real. The announcement had value because it constituted deterrence. It told other handlers in PoK that their movements were not protected. It told Pakistan Army personnel responsible for those handlers that their protection was not absolute. It told the broader jihadist apparatus that the Sunjuwan attack, five years on, had not been forgotten.

The five-year gap between attack and consequence is the chain’s most important feature. In the analysis offered by Rana Banerji, the former RAW special secretary, the gap was not a delay. It was the time required for capability to develop to the point at which the consequence could be delivered. The Indian state did not have, in February 2018, the operational architecture that would produce a body in Naseerabad. By October 2023, it did. The chain ran from the night the perimeter was breached at Sunjuwan to the morning the body was found in the culvert, and the chain had a length determined by the time required for the architecture to mature. The architecture matured. The body followed.

The Methodology Deviation: Why Beheading

The beheading method requires its own analysis because it sits in tension with the broader operational pattern that defines the targeted-killings campaign more generally. The campaign’s standard methodology, as documented across the bulk of the eliminations on Pakistani soil from 2022 through 2026, is the motorcycle-borne pistol shooting. The shooting is conducted by a pillion rider, the rider is a separate operative, the engagement window is measured in seconds, and the escape route is pre-rehearsed using the urban density of the host city. The methodology is consistent across Karachi, Lahore, Sialkot, and other Pakistani urban environments. It reflects an operational protocol that the Indian intelligence community has refined to a high degree of standardisation.

Beheading deviates from this protocol along every dimension. It is not conducted in seconds. It requires kidnapping, holding, and post-mortem placement of the body. It does not use motorcycles. It does not require urban density. It produces a body that is unmistakably identifiable, whereas the motorcycle-borne shooting produces a body that is identifiable but not exceptionally so. It also produces a method-of-execution that is associated, in the broader regional context, with tribal justice in the FATA region, with TTP operations against Pakistani security forces, and with the Islamic State’s propaganda apparatus. It is associated, in other words, with the methods of the broader violent ecosystem in which Pakistan-based jihadist organisations operate, rather than with the methods of state intelligence services.

The association produces an analytical question that the Indian state’s silence does not resolve. Was Shahid’s killing the work of the same campaign that produced the Karachi and Lahore shootings, or was it the work of an internal PoK faction, perhaps a TTP-aligned actor, who had a separate quarrel with Shahid for reasons unrelated to the Indian campaign? The analytical question deserves to be taken seriously, and the evidence on each side deserves to be presented before the question is adjudicated.

The case for an internal Pakistani killing rests on three considerations. First, the method matches the methods of TTP and other tribal-region actors more closely than it matches the methods that the Indian state has otherwise demonstrated. Second, Shahid operated in a complex jihadist ecosystem in which inter-organisational rivalries are real and have produced violence in the past. Third, the Pakistani state’s silence on the killing, the absence of a public investigation, and the suppression of the story in Pakistani media could be interpreted as Pakistani embarrassment over an internal failure rather than as Pakistani concealment of an Indian operation.

The case for an Indian-linked killing rests on stronger considerations. First, Shahid’s profile makes him a target whose elimination matches the target-selection logic of the Indian campaign rather than the target-selection logic of any plausible internal Pakistani actor. He was a Sunjuwan attack mastermind, an LeT-aligned handler, and a man whose name was on Indian wanted lists. He was not a TTP enemy. TTP has no documented history of targeting LeT or Hizbul Mujahideen handlers. The internal-Pakistani-rivalry hypothesis cannot identify a plausible actor who would have killed Shahid for reasons unrelated to Indian interests. Second, the timing of the killing is consistent with the broader operational tempo of the Indian campaign during late 2023, during which the campaign’s reach into PoK had been demonstrated by the Abu Qasim killing earlier in the year. The Shahid killing extends the PoK theatre rather than introducing a new actor into it. Third, the placement of the body, the public location, the visibility of the message, is consistent with the campaign’s broader pattern of producing visible messages while maintaining state-level deniability.

The synthesis the available evidence supports is that Shahid’s killing was conducted by the same operational architecture that produced the broader campaign, but the methodology was adapted to the constraints of the PoK theatre. The motorcycle-borne shooting protocol could not function in Naseerabad. The urban density of Karachi or Lahore was absent. The escape route on which the protocol depends did not exist in the geography in which the operation had to be conducted. The methodology adapted. The kidnap-and-disposal pattern that produced the body was an adaptation, not a deviation. It was the same campaign solving the operational problem of how to reach a target whose movements were confined to terrain in which the standard methodology was unworkable.

The adaptation has implications that extend beyond the Shahid case. It demonstrates, as Rana Banerji has argued, that the Indian operational architecture is methodologically flexible. It is not committed to a single signature pattern. It will use motorcycle-borne shootings where the urban geography supports them, but it will use other methodologies where it does not. The flexibility is the operational sophistication of the architecture. The signature is not the methodology; the signature is the consistency of target selection across methodologies. The targets are India-wanted individuals. The methods adapt to the terrain in which the targets live.

The Question of Family Targeting

The question of whether the cell at Sunjuwan deliberately targeted military families, or whether the family quarters were collateral damage in an operation aimed at the brigade headquarters or armoury, deserves direct adjudication because it bears on the moral weight of the attack and on the strategic logic of the response. The available evidence allows the question to be adjudicated, though not without acknowledging the residual uncertainty that operational reconstructions always carry.

The evidence for deliberate targeting is substantial. The cell’s directional choice after the breach is the first piece. The breach point on the southern perimeter offered the cell an internal route that ran toward both the operational core and the residential blocks. The cell chose the residential route. The choice required them to traverse internal cantonment ground and to bypass higher-value tactical targets in order to reach the residential block. Such a choice is not made accidentally. The cell had a route plan, the route plan had been briefed by Shahid as the launch handler, and the route plan terminated at the residential blocks. The directional choice was deliberate.

The cell’s behaviour inside the block is the second piece. The cell did not exchange fire with combatants and incidentally injure civilians. The cell entered residential corridors, fired through the doors of family quarters, threw grenades into rooms in which it could hear voices, and used family members as human shields when QRF elements approached. Each of these behaviours is inconsistent with an operation in which civilians were collateral damage. Each is consistent with an operation in which civilians were the operational target.

The cell’s loadout is the third piece. The cell carried heavy ammunition and grenade payloads, equipment configurations that supported sustained engagement. The configuration is consistent with a plan to occupy a defensible position inside a populated structure and inflict maximum casualties on the population while a defensive engagement was fought against responding QRF elements. The configuration would not have been the configuration of choice for a tactical raid on the brigade headquarters or armoury, which would have been more efficiently executed with a smaller, faster-moving cell carrying breach charges rather than ammunition for a sustained defensive engagement.

The campaign of LeT statements after the attack is the fourth piece. LeT-aligned outlets framed the attack as a strike against Indian Army families, with the framing presented as a consequence-imposing action against the families of the soldiers responsible for operations against Kashmiri Muslims. The framing is propaganda, but the propaganda matters. It tells the analyst what the perpetrating organisation intended the attack to mean. The intended meaning was the targeting of families.

The evidence against deliberate targeting is thinner. The fence-and-vegetation cover at the southern perimeter offered the cell an opportunistic breach point that happened to be closer to the residential blocks than to the operational core, and a reading could be offered in which the cell exploited that breach point and then chose targets opportunistically once inside. The reading does not survive the cell’s internal traverse. The cell did not engage opportunistically; it traversed deliberately. The internal route was four hundred metres of considered movement past a number of higher-value tactical targets. Opportunism does not produce that traverse.

The harder version of the contrarian reading, that the cell intended to reach the operational core but was forced toward the residential blocks by the early sentry contact, also does not survive the timing. The sentry contact occurred after the cell had already covered most of the four hundred metres toward the residential blocks. The traverse had committed the cell to the residential approach before any sentry contact occurred. The sentry contact, when it happened, was a defence of the residential block, not a redirection of the cell’s intent.

The conclusion the evidence supports is the conclusion the General Officer Commanding stated on 12 February 2018: the cell targeted families. The conclusion is morally heavy and analytically robust. It bears on the strategic response that followed because the Indian response architecture was designed to deliver consequences against handlers whose decisions had produced operations that inflicted casualties on Indian non-combatants. Sunjuwan, with its inversion of the combatant-to-civilian casualty ratio, was the kind of operation against which the architecture was directed. Shahid, as the launch handler, was the kind of target the architecture was built to reach. The five-year gap between his decision and his disposal was the time the architecture required. The disposal, when it came, came as a consequence of the decision he made about which way the cell should turn after the perimeter was breached.

The Wider Network and the LeT Apparatus

Khwaja Shahid was not a freelancer. He operated inside an organisational apparatus whose structure has been mapped in detail in the LeT complete guide, and the Sunjuwan-to-Naseerabad chain cannot be understood without placing him in that apparatus. The apparatus’s relevant features for this analysis are three. First, LeT’s launch coordination layer, the set of handlers who manage cross-border insertions, is functionally fused with the equivalent layers of Hizbul Mujahideen and the Tehrik-e-Khalistan Tigers under what Indian intelligence describes as ISI-coordinated multi-organisation operations. Shahid’s career trajectory, from Hizbul Mujahideen to multi-organisation handler, illustrates the fusion in personal form. Second, LeT’s operational tempo against Indian targets in 2017 and early 2018 was driven by central decisions taken in coordination with the ISI’s S-Wing, with target selection, timing, and resource allocation decided at that level. Sunjuwan was a centrally driven operation, not a local initiative. Third, LeT’s protective environment in Pakistan and PoK rests on a combination of formal Pakistan Army support, informal local political support, and the institutional architecture of the Falah-e-Insaniat Foundation and its predecessor and successor organisational fronts. Shahid lived inside this protective environment. His residence in Naseerabad was not a hiding place; it was an open residence under the functional protection of the Pakistan Army’s Northern Light Infantry.

The apparatus’s response to Shahid’s killing was instructive. LeT-aligned outlets, after the body was discovered, produced obituary materials that named Shahid as a martyr and that did not specify the circumstances of his killing. The Pakistan Army did not comment publicly. The PoK administration, after the brief initial police report, suppressed further reporting on the case. The pattern of response is a pattern of organisational and state damage control, not a pattern of investigation. The damage control is the response of an apparatus that knows what happened and does not wish the public to engage with the implications.

The implications, however, were engaged with privately. In the months after Shahid’s death, LeT and Hizbul Mujahideen handlers in the Neelum Valley altered their patterns. Routine movements were reduced. Residences were relocated. Access to handlers was restricted in ways that complicated subsequent organisational coordination. The behavioural change is the deterrent effect that the placement of Shahid’s body in a culvert was designed to produce. The placement worked. It worked by demonstrating that the Pakistan Army’s protective umbrella over PoK handlers was not absolute, and the demonstration produced behavioural adaptation. The adaptation, in turn, raised the operational cost of subsequent handler activity, which is the strategic effect the Indian state was seeking.

The wider network’s response also had a second-order effect on India’s broader operational reach. The behavioural adaptation by handlers in the Neelum Valley pushed some of them deeper into the Pakistan-controlled interior, into Punjab and into Karachi-based operations rather than PoK-based operations. The push had the effect of moving them into theatres in which the standard motorcycle-borne shooting methodology functioned. The 2024 and 2025 acceleration of eliminations in Karachi and Lahore included, on Indian intelligence assessments, several individuals who had previously operated from PoK and who relocated after Shahid’s killing. The relocation made them reachable through methodologies that PoK terrain had blocked. The chain from Shahid’s elimination to subsequent eliminations in Karachi and Lahore is, in this reading, a chain of consequence. The first elimination produced behavioural change that made subsequent eliminations easier.

The NIA’s response to Shahid’s killing followed within two weeks of the body’s discovery. The agency issued property-attachment orders against Shahid’s known holdings in Kupwara district of Indian Kashmir, where he had retained ancestral property despite his decades-long residence in PoK. The property-attachment orders carried a particular legal logic. Indian law allows the attachment of property of designated terrorists for the purpose of preventing the use of such property to fund terror operations. The attachment of Shahid’s property after his death, when funding from him to operations was no longer possible, served a different purpose. The purpose was symbolic and procedural. The symbolic purpose was the public marking of the case as closed. The procedural purpose was the formal record of the state’s position that Shahid had been a designated terrorist and that the state’s position on him had been confirmed by his elimination. The attachment orders, in this reading, were the bureaucratic full stop on a chain whose operational expression was the body in the culvert.

The Sunjuwan Pattern and the Broader Doctrine

Sunjuwan is one event in a longer pattern, and reading it as a single event misses the pattern. The pattern is the pattern of attack-to-consequence chains in the Indian counter-terror campaign. The pattern’s earliest visible expression is the Pathankot attack of January 2016 and the subsequent killing of its mastermind Shahid Latif in Sialkot in October 2023, a chain that ran for seven years and ended with a man shot inside a Sialkot mosque. The pattern’s clearest contemporary expression is the Pahalgam attack of April 2025 and the subsequent Operation Sindoor, a chain that ran for less than a month and ended with kinetic strikes against terror infrastructure in Pakistani territory. The Sunjuwan chain sits between these two examples in chronological extent and in methodology.

The pattern’s underlying logic is consistent across cases. An attack on Indian soil produces casualties and identifies a chain of responsibility. The chain of responsibility runs from the cadres who executed the attack, who are typically killed in the engagement, through the launch handlers who dispatched them, to the organisational and state structures that support both. The Indian state’s response architecture is designed to deliver consequences along the chain of responsibility, with priority assigned to handlers and organisational figures whose elimination produces operational disruption rather than merely symbolic effect. The architecture’s outputs vary in methodology and in the time required for delivery, but the inputs are consistent: an attack produces a list of names, the list is worked through, and the names accumulate in a ledger whose contents become public when the bodies are found.

The doctrine the architecture implements has not been publicly named by the Indian state. The state’s posture is a posture of operational silence and strategic deniability. The doctrine, however, is legible from the pattern, and the legibility is the doctrine’s purpose. The doctrine is meant to be read, by Pakistani handlers, by Pakistani military officers responsible for those handlers, and by the broader jihadist ecosystem that depends on the Pakistani protective umbrella, as a statement that the umbrella is not protective. The doctrine is meant to function as deterrence by accumulation. Each elimination is an instance. The pattern is the doctrine. The pattern’s visibility is its instrument.

Sunjuwan, in this reading, is a doctrinal instance. The attack of February 2018 is the Indian state’s input. The body in the culvert of October 2023 is the state’s output. The chain between them is the doctrine working. The chain’s visibility, the public discovery of the body, the absence of a denial from any plausible alternative actor, the obituaries in LeT outlets that named Shahid as a martyr without explaining the circumstances, all function as the doctrine’s signal. The signal is read by the audience the doctrine is intended for. The reading produces behavioural adaptation. The adaptation is the deterrent effect.

The doctrine has limits, and the limits deserve naming. It does not produce convictions. It does not produce admissions. It does not produce the legal closure that domestic counter-terror prosecutions in democratic states have historically been built around. It produces bodies, and bodies are not the same as convictions. The substitution of bodies for convictions is the doctrine’s most consequential trade-off, and the trade-off is the subject of the named disagreement that defines the doctrine’s place in the broader analytical conversation about counter-terror practice. Walter Ladwig III of King’s College London has argued that the substitution risks long-term legitimacy costs that compound over time. Christine Fair of Georgetown University has argued that the substitution is the only practicable option in cases where the safe haven structure prevents legal access. The argument is not closed. Sunjuwan-to-Naseerabad is a single data point in the argument, and the argument’s resolution will depend on data points that have not yet been produced.

The doctrine’s relationship to the broader Indian state architecture against terror is one of complementarity rather than substitution. The state continues to pursue legal cases against terror perpetrators. The NIA continues to file charge sheets, conduct investigations, and obtain convictions where domestic legal processes allow. The doctrine of consequence delivery operates alongside the legal apparatus, not instead of it. The two together constitute the Indian state’s response, and the response is broader and more layered than either component on its own. Sunjuwan illustrates the layering. The legal response is in the NIA charge sheets and the property attachments. The consequence delivery is in the body in the culvert. The two responses are different in kind and complementary in effect.

What Sunjuwan Still Means

Sunjuwan remains an event of operational significance in the Indian counter-terror community more than seven years after the engagement, and the significance is worth naming because it informs the way subsequent attacks have been responded to and the way subsequent cantonment security has been designed. Three categories of consequence deserve separate treatment.

The first category is operational doctrine inside the Indian Army. The Sunjuwan engagement produced a sustained review of cantonment security across the Northern and Western Commands, a review whose recommendations included the introduction of motion-sensor coverage of perimeter sections previously considered low-risk, the establishment of internal patrolling regimes between perimeter and residential blocks, and the incorporation of hardened-shelter design into family quarters. The review’s recommendations have been implemented unevenly, with new construction more compliant than retrofit on existing cantonments, but the recommendations themselves have shaped the doctrinal baseline. Subsequent attempts at fidayeen breaches of cantonments have encountered the doctrinal baseline, and the breach success rate has dropped accordingly. Sunjuwan is the case the doctrine was built around.

The second category is the response architecture that produced Shahid’s elimination. The architecture has been used across multiple cases since Sunjuwan, with the same logic of working through chains of responsibility and delivering consequences against handlers whose decisions produced casualties on Indian soil. The Sunjuwan-to-Naseerabad chain was an early application of the architecture, and the Naseerabad outcome has informed subsequent applications. The methodology adaptation that the PoK theatre required has been generalised. The architecture’s flexibility, its willingness to use methodologies that depart from the Karachi-Lahore standard when terrain demands, has been internalised. Subsequent eliminations in PoK and in similar terrains have used adapted methodologies, and the adaptations are recognisable as the same architecture that produced the body in the culvert.

The third category is the moral weight that the family-targeting dimension of the attack has placed on the broader Indian counter-terror posture. Sunjuwan is one of the cases that Indian commentators cite when arguing that the standard frameworks of proportionality, distinction, and restraint, which apply to conflicts between regular military forces, do not map cleanly onto the conflict India faces with Pakistan-based jihadist organisations. The argument runs that the deliberate targeting of military families by fidayeen cells dispatched by handlers protected by the Pakistani state alters the calculus of legitimate response. The Sunjuwan-to-Naseerabad chain is offered, in this argument, as an instance of legitimate response. The argument is contested by domestic and international voices that hold the standard frameworks to apply regardless of the conduct of the adversary, and the contestation is the live moral debate around the doctrine. Sunjuwan is one of the cases the debate turns on, and it will continue to be cited in the debate until the broader pattern produces resolution.

What the case cannot do is produce closure for the families of those killed. The wife of the Lance Naik, the family of the Naib Subedar whose four-year-old son was killed by grenade fragmentation, the daughter of the retired Naib Subedar Ashraf, the children of Subedar Choudhary and Naik Mir and Lance Naik Iqbal, do not receive closure from the discovery of a body in a culvert in Naseerabad. The body in the culvert is the state’s instrument, and the state’s instruments operate at a different level from the lives of the people on whose behalf the state claims to act. The disjunction is real, and the people who live with the disjunction live with it. The state’s response to Sunjuwan, in the form of the architecture and its outputs, is not a response that delivers closure to the bereaved. It is a response that delivers deterrence to future handlers, and the deterrence is intended to reduce the rate at which other families become bereaved in the future. The trade-off is the trade-off the doctrine makes.

The continuing relevance of Sunjuwan in 2026, eight years after the engagement, is that the trade-off remains live. The doctrine continues to operate. The architecture continues to produce outputs. The Pakistani jihadist apparatus continues to dispatch cadres against Indian targets. The cadres continue to be intercepted by hardened cantonment security, by improved internal patrolling, and by intelligence-driven preemption. When they are not intercepted, they continue to produce casualties. When casualties occur, the architecture continues to work through the chain of responsibility and produce outputs, with methodologies that adapt to the terrains in which the chain leads. The cycle is not closed. The cycle is the situation. Sunjuwan is one revolution of the cycle. Naseerabad is another. The cycle continues, and the question of how it ends, or whether it ends, is the question that hangs over the entire Indian counter-terror posture and the question that informs every subsequent case in the pattern.

Frequently Asked Questions

Q: What happened at the Sunjuwan Army camp attack?

On the night of 9 to 10 February 2018, a four-cadre cell of Lashkar-e-Taiba fidayeen breached the southern perimeter fence of the 36 Brigade headquarters cantonment at Sunjuwan, on the southern outskirts of Jammu city. After cutting through the perimeter at an unlit drainage line, the cell traversed approximately four hundred metres of internal cantonment ground and entered a residential block that housed the families of officers and jawans of brigade-attached units. Inside the block, the cell engaged Indian Army personnel and family members, fired through doors of family quarters, threw grenades into rooms, and used family members as human shields when Quick Reaction Force elements attempted to enter the block. The Indian Army’s response, conducted by the brigade’s QRF and reinforced by 9 Para Special Forces and Para Commando teams flown in from outside the sector, established an inner cordon around the block, evacuated families from adjacent quarters under covering fire, and conducted a systematic clearance over the next thirty-six hours. By the time the engagement was concluded on the morning of 11 February, four LeT cadres had been killed alongside seven Indian personnel and family members. The attack was the first major fidayeen breach of an Indian Army installation after the September 2016 Uri attack and the subsequent surgical strikes, and its conduct, particularly the deliberate targeting of family quarters, marked a moral inflection in the broader pattern of attacks against Indian military targets.

Q: How many people were killed at Sunjuwan?

Seven Indian personnel and family members were killed in the engagement. The seven comprised three uniformed soldiers, all of the 1st Battalion of the Jammu and Kashmir Light Infantry: Subedar Madan Lal Choudhary, killed in the initial sentry exchange; Naik Mohammed Ashraf Mir, killed leading the QRF’s first attempt to penetrate the residential block; and Lance Naik Mohammed Iqbal, killed providing covering fire during casualty extraction. The four civilian fatalities comprised Naib Subedar Mohammed Ashraf, retired, the elderly father of a serving officer, killed by grenade fragmentation while sleeping in his son’s quarter; Sarwan Devi, the wife of a serving Naib Subedar, killed by automatic fire that penetrated a corridor wall; the wife of a Lance Naik, killed sheltering children in an internal room when a grenade was thrown through the door; and the four-year-old son of a Naib Subedar, killed by the same grenade that killed the Lance Naik’s wife. Eleven other Indian personnel and family members sustained injuries. All four LeT cadres of the perpetrating cell were also killed. The casualty pattern, with five non-combatants among the seven killed, was unusual for fidayeen attacks on Indian military installations and informed the subsequent assessment that the cell had deliberately targeted families.

Q: Were military families targeted at Sunjuwan?

The available operational evidence, including the cell’s directional choice after the perimeter breach, the cell’s behaviour inside the residential block, and the cell’s loadout configuration, supports the assessment that the targeting of military families was deliberate rather than incidental. After breaching the southern perimeter, the cell traversed approximately four hundred metres of internal cantonment ground in a direction that took them away from the brigade headquarters, the operations room, the armoury, and the vehicle park, all higher-value tactical targets, and toward the residential block. Once inside the block, the cell did not exchange fire with combatants and incidentally injure civilians. The cell entered residential corridors, fired through the doors of family quarters, threw grenades into rooms in which it could hear voices, and used family members as human shields. The loadout configuration, with heavy ammunition and grenade payloads supporting sustained engagement rather than tactical raid, was consistent with a plan to occupy a defensible position inside a populated structure and inflict maximum civilian casualties. The General Officer Commanding the Northern Command, in his press briefing on 12 February 2018, identified the targeting of families as the operational object of the attack, and subsequent NIA documentation reached the same determination.

Q: Who masterminded the Sunjuwan attack?

The Indian National Investigation Agency, in cooperation with the Jammu and Kashmir Police Special Investigation Group and with intelligence inputs from the Research and Analysis Wing, identified Khwaja Shahid alias Mian Mujahid as the launch handler responsible for inserting the Sunjuwan cell across the international border from Sialkot to Jammu and for selecting the target. Shahid, originally from the Lolab Valley in Kupwara district of Indian Kashmir, had crossed the LoC as a teenager in the early 1990s and risen through Hizbul Mujahideen ranks before transitioning into a multi-organisation handler role coordinating launches for both Hizbul Mujahideen and LeT-aligned cells. At the time of the Sunjuwan attack he was thirty-eight years old and based in the Neesserabad area of the Neelum Valley in Pakistan-occupied Kashmir, where he operated under the protection of the Pakistan Army’s Northern Light Infantry. Identification of Shahid as the launch handler rested on telephone interception data captured during the cell’s brief radio communications with handlers in Sialkot, debriefing of LeT cadres detained in unrelated operations in subsequent months, and personal effects recovered from the bodies of the four cadres that contained route information consistent with launch from a node Shahid was known to control. The strategic decision to mount the attack was, in Indian intelligence assessments, taken at LeT central command level in coordination with the ISI’s S-Wing; Shahid’s role was operational handling rather than strategic decision-making.

Q: What happened to the Sunjuwan attack mastermind?

Khwaja Shahid was found dead on 19 October 2023, more than five years and eight months after the Sunjuwan attack, in a roadside drainage culvert near Naseerabad in the Neelum Valley of Pakistan-occupied Kashmir. The body had been decapitated; the head was recovered separately, a short distance from the body. Forensic indicators were consistent with him having been kidnapped from his residence approximately two days before the discovery, held during the intervening period, and killed at a different location before the body was placed in the culvert. The Pakistan-occupied Kashmir police reported the discovery within hours of the body’s recovery, and the report briefly entered Pakistani media before being withdrawn from circulation. Pakistani jihadist outlets confirmed the identity of the deceased, identified him as a senior LeT-aligned handler, and circulated obituary materials that named him as a martyr of the Kashmir cause. Neither the Indian state nor any other actor has publicly claimed responsibility for the killing. The Indian National Investigation Agency issued property-attachment orders against Shahid’s known holdings in Kupwara district within two weeks of the body’s discovery, marking the case as procedurally closed from the Indian state’s perspective.

Q: How was Khwaja Shahid killed five years later?

The methodology that produced Shahid’s death deviated from the standard motorcycle-borne pistol shooting pattern that characterises the bulk of the eliminations on Pakistani soil in the broader targeted killings campaign. The Naseerabad terrain, a single river-bottom corridor flanked by high mountains with sparse civilian population and dense Pakistan Army Northern Light Infantry checkpoint coverage, did not support the urban-density-based motorcycle methodology. The methodology that reached Shahid was a kidnap-and-disposal pattern: he was taken from his residence by people who could enter that residence without raising an alarm, held for approximately two days, killed by means that produced the decapitation forensic pattern, and the body was placed in a public location in a culvert beside a road where PoK residents and Pakistan Army patrols both used. The placement in a public location, rather than concealment, served both identification and message functions. The decapitation produced unambiguous identification that could not be denied or mistaken. The public placement produced visibility that announced the reach. The methodology, in this reading, was an adaptation of the broader Indian operational architecture to the specific operational constraints of the PoK theatre rather than a deviation from the architecture’s underlying logic.

Q: Which organization carried out the Sunjuwan attack?

Lashkar-e-Taiba, the Pakistan-based jihadist organisation founded in the late 1980s by Hafiz Saeed and operationally headquartered at the Markaz-e-Taiba complex in Muridke, Pakistan, carried out the Sunjuwan attack. The identification was made by Indian Army forensic teams during the post-engagement assessment, was confirmed by NIA investigation, and was implicitly acknowledged by LeT-aligned outlets in subsequent claim materials that framed the attack as a strike against Indian Army families. The strategic decision to mount the operation was taken at LeT central command level in coordination with the ISI’s S-Wing directorate, which handles non-state actor coordination on the Pakistani side. The four cadres of the cell carried Pakistan Army-issue tactical webbing of a pattern issued to the Special Service Group, with Pakistani markings unremoved, an evidentiary detail that supported the attribution. LeT’s broader operational tempo against Indian targets in 2017 and early 2018 was driven by central decisions that prioritised the demonstration of operational continuity in Indian Kashmir, both to maintain credibility with the cadre base and to signal organisational indispensability to Pakistani security agencies during a period of FATF-driven scrutiny over funding flows. Sunjuwan was the most consequential operational expression of that tempo.

Q: Why did it take five years for consequence to reach the mastermind?

The five-year gap between the Sunjuwan attack of February 2018 and the discovery of Shahid’s body in October 2023 reflected the time required for the Indian operational architecture to develop the capability to project violence into the specific terrain in which Shahid lived. Through the first phase of the gap, from February 2018 to roughly mid-2020, the Indian intelligence community was assembling the capability to project violence into Pakistani territory through means other than uniformed military operations, including the construction of asset networks inside Pakistan, the cultivation of relationships with Pakistani citizens who could provide ground-level surveillance and logistical support, and the development of operational protocols that would minimise the exposure of Indian assets to Pakistani counter-intelligence. Through the second phase, from mid-2020 to early 2022, pilot operations including the June 2021 car bomb near Hafiz Saeed’s Lahore residence demonstrated the new capability publicly while operational work continued on PoK-specific asset networks. Through the third phase, from early 2022 onward, sustained operational tempo on Pakistani soil established the campaign’s pattern in urban Pakistani cities. The PoK theatre, however, required methodologies adapted to terrain in which the urban motorcycle-borne pattern did not function, and those adaptations were not operationally available until the architecture matured to the point at which it could deliver methodologies appropriate to the Neelum Valley. By October 2023, the architecture had matured. The body in the culvert was the architecture’s first PoK-theatre output of a methodology that would subsequently be reused.

Q: Who was Khwaja Shahid alias Mian Mujahid?

Khwaja Shahid was a Kashmiri-origin jihadist handler who, at the time of his death in October 2023, was a multi-organisation launch coordinator operating from Naseerabad in the Neelum Valley of Pakistan-occupied Kashmir. Originally from the Lolab Valley in Kupwara district of Indian Kashmir, he had crossed the Line of Control as a teenager in the early 1990s and joined Hizbul Mujahideen, the Kashmir-focused organisation aligned with the Jamaat-e-Islami in Pakistan. By the early 2000s he had moved into operational handling roles, coordinating infiltration of cadres across the LoC into the Kashmir Valley. By the early 2010s he had transitioned into a multi-organisation handler role, coordinating launches for both Hizbul Mujahideen and LeT-aligned cells. The transition reflected the operational fusion between Kashmir-focused and Pakistan-based jihadist organisations under ISI coordination that has characterised the launch coordination layer of the broader apparatus over the last two decades. He operated under the alias Mian Mujahid in jihadist communications and propaganda materials. His residence in PoK placed him near the launching pads he coordinated, and his life there was lived openly under the protection of the Pakistan Army’s Northern Light Infantry, which exercises functional control over the Neelum Valley. He was a mid-tier operational asset whose value to the Pakistani jihadist apparatus exceeded his name recognition among Indian commentators, and his elimination produced a deterrent signal whose effects extended beyond his own case.

Q: Why was Khwaja Shahid beheaded instead of shot?

The decapitation methodology that produced Shahid’s body in the Naseerabad culvert reflected adaptation of operational protocols to the specific terrain of the PoK theatre rather than a deviation from the broader doctrinal logic of the Indian counter-terror campaign on Pakistani soil. The campaign’s standard methodology, the motorcycle-borne pistol shooting that has characterised eliminations in Karachi, Lahore, Sialkot, and other Pakistani urban environments, depends on urban density that supports rapid escape after a brief engagement window. The Neelum Valley terrain does not provide that density. The Valley is a single river-bottom corridor flanked by high mountains, with sparse civilian population and dense Pakistan Army Northern Light Infantry checkpoint coverage along the only road. The motorcycle-borne pattern is operationally unworkable in such terrain. The methodology that reached Shahid was therefore different. It involved kidnapping from his residence by personnel who could enter the residence without raising an alarm, holding for processing of operational duration, killing at a separate location, and disposal in a public roadside location. The decapitation produced unambiguous identification, and the public placement of the body produced visibility that announced the reach of the operational architecture into a theatre in which the standard methodology was unworkable. The methodology was adapted; the underlying logic of working through chains of responsibility against handlers whose decisions had produced casualties on Indian soil was unchanged.

Q: Where was Khwaja Shahid’s body found?

Shahid’s body was found in a roadside drainage culvert near Naseerabad in the Neelum Valley of Pakistan-occupied Kashmir on the morning of 19 October 2023. The Neelum Valley, administered by Pakistan as part of Azad Kashmir, runs north-east from Muzaffarabad along the Neelum River and constitutes a critical component of the launching pad infrastructure that LeT and Hizbul Mujahideen jointly maintain for cross-LoC infiltration into Indian-administered Kashmir. Naseerabad sits in the southern reach of the Valley, near the LoC’s westernmost approaches and within Pakistan Army Northern Light Infantry security control. The culvert in which the body was found was beside a road that PoK residents and Pakistan Army patrols both used, ensuring rapid discovery. The PoK police reported the discovery within hours and produced an initial report that briefly entered Pakistani media before being withdrawn from circulation. The forensic indicators visible at the scene included the decapitation, with the head recovered separately a short distance from the body, and binding marks at the wrists and ankles consistent with restraint during a holding period. The body’s placement in the public roadside location, rather than in concealment, was operationally deliberate; the placement served identification and message functions that concealment would not have served.

Q: Is the beheading connected to the targeted killing campaign?

The available evidence supports the conclusion that Shahid’s killing was conducted by the same operational architecture that produced the broader Indian counter-terror campaign on Pakistani soil, with the methodology adapted to the constraints of the PoK theatre. The case for an Indian-linked killing rests on three considerations. First, Shahid’s profile makes him a target whose elimination matches the target-selection logic of the Indian campaign rather than the target-selection logic of any plausible internal Pakistani actor; he was a Sunjuwan attack mastermind, an LeT-aligned handler, and a man whose name was on Indian wanted lists, and there is no documented history of TTP or other tribal-region actors targeting LeT or Hizbul Mujahideen handlers. Second, the timing is consistent with the broader operational tempo of the Indian campaign during late 2023, during which the campaign’s reach into PoK had been demonstrated by the Abu Qasim killing earlier in the year. Third, the placement of the body in a public location, the visibility of the message, and the suppression of subsequent investigation by the Pakistani state are all consistent with the campaign’s broader pattern of producing visible messages while maintaining state-level deniability. The methodological deviation, decapitation rather than motorcycle-borne shooting, is a methodology adaptation to PoK terrain rather than a signal of a different actor. The campaign’s signature is consistency of target selection across methodologies, not consistency of methodology itself.

Q: Why did NIA attach Shahid’s property after his death?

The Indian National Investigation Agency issued property-attachment orders against Shahid’s known holdings in Kupwara district of Indian Kashmir within two weeks of the discovery of his body in October 2023. The attachment served two purposes. The symbolic purpose was the public marking of the case as procedurally closed from the Indian state’s perspective. The state had identified Shahid as the Sunjuwan launch handler, had pursued him through legal designation processes during the years between 2018 and 2023, and the attachment of his property after his elimination served as the bureaucratic full stop on the case. The procedural purpose was the formal record of the state’s position that Shahid had been a designated terrorist and that the state’s position on him had been confirmed, in legal terms, by the formal attachment. Indian law allows the attachment of property of designated terrorists, and the attachment proceeding produces formal documentation of the designation that becomes part of the public legal record. In Shahid’s case, the attachment also served a forward-looking function. His ancestral property in Kupwara had been used during his decades of PoK residence in ways that required NIA investigation, including potential transfers of value to other handlers and to family members on the Indian side of the LoC. The attachment proceeding produced legal authority to continue the investigation of those transfers without the encumbrance of a living designated terrorist whose presence in PoK had complicated previous investigation phases.

Q: How many people died in the Sunjuwan attack?

Eleven people died in the Sunjuwan engagement: seven Indian personnel and family members, and four LeT cadres of the perpetrating cell. The seven Indian fatalities comprised three uniformed soldiers of the 1st Battalion of the Jammu and Kashmir Light Infantry, killed in the defence of the residential block, and four civilians, comprising a retired soldier visiting his son’s family, two wives of serving soldiers, and a four-year-old child. The four LeT cadres were killed during the systematic clearance of the residential block over the thirty-six hours of the engagement, with two cadres eliminated in the initial perimeter and isolation phase and the remaining two eliminated during the structured entry and clearance phase. Eleven other Indian personnel and family members sustained injuries during the engagement, with a smaller number of those wounded evacuated to military hospitals in Jammu and Pathankot for surgical treatment. The casualty figures are drawn from the official press briefing of the General Officer Commanding the Northern Command on 12 February 2018, from subsequent NIA filings on the case, and from corroborating Indian Army communications during the period of the engagement and immediately afterward.

Q: What does the beheading method reveal about the campaign?

The methodology adaptation that the Shahid killing represents reveals two structural features of the Indian counter-terror campaign that are not always visible in case-by-case analyses. First, the campaign is methodologically flexible. It is not committed to a single signature pattern. The motorcycle-borne pistol shooting that has characterised the bulk of urban-Pakistani eliminations is one methodology among several available to the operational architecture, and the architecture’s flexibility allows it to deploy methodologies appropriate to the terrain in which a specific target lives rather than committing to a single signature regardless of operational fit. The signature of the campaign is consistency of target selection across methodologies, not consistency of methodology itself. Second, the campaign is theatre-aware. Different theatres of operation, urban Pakistan, PoK, the FATA region, and others, present different operational constraints and require different methodologies. The campaign’s architecture has the capacity to develop and deploy methodologies tailored to each theatre. The Naseerabad case demonstrated the capacity in the PoK theatre. Subsequent cases have demonstrated similar capacity in other theatres. The methodological adaptation also serves a strategic-deniability function, since methodological diversity complicates attribution and prevents the campaign from being defined by a single signature pattern that could be used by Pakistani diplomatic representations as evidence of Indian responsibility. The diversity of methodologies, in this reading, is itself a feature of the campaign’s design rather than an incidental variation.

Q: How does Sunjuwan compare to other fidayeen attacks on Indian Army installations?

Sunjuwan sits within a broader pattern of fidayeen attacks on Indian Army installations that runs from the early 2000s through the present, a pattern that includes the Kaluchak attack of May 2002, the Pathankot attack of January 2016, and the Uri attack of September 2016. The Sunjuwan engagement differs from each of these earlier cases along significant operational and moral dimensions. Compared to Uri, in which the cell engaged uniformed personnel sleeping in their tents and the casualty count was overwhelmingly military, Sunjuwan inverted the combatant-to-civilian ratio by deliberately targeting family quarters. Compared to Pathankot, in which the cell engaged the airbase periphery and the casualty count was concentrated among security force personnel responding to the breach, Sunjuwan involved sustained engagement inside a residential block over thirty-six hours and the deliberate use of family members as human shields. Compared to Kaluchak, in which the cell entered the family quarters of an Army camp and killed multiple family members in a methodology similar to Sunjuwan’s, Sunjuwan was operationally more sophisticated, with better-equipped cadres, longer engagement duration, and more substantial defensive position-taking inside the block. The Kaluchak comparison is the closest analogue, and it is the analogue that produced the doctrinal anticipation that informed the cantonment security review after Sunjuwan. The pattern across cases supports the assessment that LeT and JeM tactical doctrines have evolved over time, with later cells better-equipped, better-coordinated, and more willing to inflict civilian casualties as part of the operational object.

Q: What was India’s response to the Sunjuwan attack at the political level?

The political response to Sunjuwan unfolded across multiple registers. Defence Minister Nirmala Sitharaman visited the Sunjuwan camp and the Army hospital in Jammu where the wounded were being treated within forty-eight hours of the engagement’s conclusion, and her statement at the camp named LeT explicitly as the perpetrating organisation, identified Pakistan as the location from which the attack had been launched, and declared that Pakistan would pay for the attack at a time and place of India’s choosing. The Ministry of External Affairs summoned Pakistan’s Deputy High Commissioner in New Delhi and lodged a formal protest, citing the Pakistan Army-issue tactical webbing recovered from the cell as evidence of cross-border launch. The National Security Adviser convened an inter-agency review of the attack and its implications. The Cabinet Committee on Security met within seventy-two hours of the engagement and approved enhanced operational authorities for the response architecture that would, over the following five years, work through the chain of responsibility for the attack. The political response was, in its public expression, a response of denunciation and demand, but the operational response that the political response authorised was the architecture whose first PoK-theatre output was the body in the Naseerabad culvert. The two registers of response, the public-political and the operational-architectural, ran in parallel through the five years that followed, and the second produced outputs that the first did not publicly claim.

Q: Could Sunjuwan have been prevented?

The post-engagement review conducted by the Indian Army identified specific security failures whose correction could have produced different outcomes, and the failures are worth naming because they inform the cantonment security baseline that has been adopted in subsequent years. The first failure was perimeter security at the southern fence line, which lacked motion-sensor coverage at the section the cell breached. The breach point exploited ground depression and vegetation that made it invisible from the nearest watchtower, and motion sensors at that section would have alerted the perimeter guards before the cell completed its breach. The second failure was internal patrolling, with no patrol presence between the perimeter and the residential block at the time the cell traversed the four hundred metres of internal cantonment ground. An internal patrol regime that covered the gap between the perimeter sentry duty and the dispersed quarter guard duty at residential blocks could have intercepted the cell during the traverse. The third failure was cantonment design itself, with family quarters built without internal hardened-shelter rooms that families could retreat to in the event of a perimeter breach. Hardened-shelter design would have provided defensible internal positions during the engagement and could have reduced civilian casualties. The Army’s review recommended remediation across all three categories, and the recommendations have been implemented unevenly in subsequent years, with new construction more compliant than retrofit on existing cantonments. The lesson of Sunjuwan, in this reading, was that perimeter assumptions about rear-area cantonment safety in the plains of Jammu had not kept pace with the operational tempo of cross-border infiltration, and the lesson informed the cantonment security baseline across the Northern and Western Commands.

Q: What is the relationship between Sunjuwan and Pakistan’s cross-border launching apparatus?

Sunjuwan was launched from the Pakistani cross-border infrastructure that runs through the Sialkot-Jammu sector of the international border, an infrastructure whose operational architecture has been extensively documented by Indian intelligence and by the South Asia Terrorism Portal. The infrastructure comprises launching pads in the Pakistani towns of Sialkot, Bhimber, and surrounding rural areas; safe houses for cadres awaiting launch; staging routes that exploit gaps in the international border fence; and handler networks that coordinate the timing and equipment of launches. Khwaja Shahid was a senior figure in the handler layer of the infrastructure, responsible for coordinating launches across the Sialkot-Jammu axis as well as the Naseerabad-Kupwara axis on the LoC. His operational location in Naseerabad placed him within the Pakistan Army Northern Light Infantry security envelope, which exercises functional control over the Neelum Valley and adjacent PoK areas. The infrastructure functions because the Pakistani state provides the protective environment in which it operates, with Pakistan Army personnel responsible for sectors through which infiltration runs, and with civilian Pakistani jurisdiction over areas in which handlers and cadres reside. The Sunjuwan-to-Naseerabad chain ran from the cell’s breach of the Sunjuwan perimeter back through the Sialkot launching pad, back through Shahid’s coordination from Naseerabad, and back into the protective environment that the Pakistani state maintains over the entire infrastructure. The Indian operational architecture’s response to the chain has been to deliver consequences against handlers and organisational figures within the infrastructure, with Shahid’s elimination representing an early PoK-theatre output of that response.

Q: Why is the Sunjuwan attack still discussed in India eight years later?

Sunjuwan retains active discussion in Indian counter-terror, defence, and policy communities for reasons that exceed the engagement’s casualty count and reflect the case’s structural significance to the broader pattern of attacks-and-responses that defines the contemporary India-Pakistan counter-terror dynamic. The first reason is the moral inflection that the deliberate targeting of military families represented, which has informed subsequent debates about the proportionality and distinction frameworks that govern legitimate counter-terror response. The second reason is the operational doctrine that the engagement produced inside the Indian Army, including cantonment security baselines that have shaped subsequent rear-area installation design across the Northern and Western Commands. The third reason is the response architecture that produced Shahid’s elimination five years later, an architecture whose subsequent applications across the broader campaign of targeted killings on Pakistani soil traces methodological lineage to the Sunjuwan case. The fourth reason is the strategic message that the case communicated about the temporal scope of consequence delivery, namely that handlers whose decisions produced mass-casualty attacks on Indian soil could not expect that the passage of years would produce safety. The fifth reason is the bereaved families themselves, whose continued presence in Indian public life as recipients of state honours and as occasional public commentators ensures that the case is not forgotten at the level of public memory. Sunjuwan, in this reading, is both an event in operational history and a node in the ongoing public conversation about how India responds to terror attacks against its soil, and the conversation continues to use the case as a reference point in current discussions of cantonment security, response doctrine, and the strategic logic of the broader counter-terror posture.

Q: What lessons did the Indian Army draw from Sunjuwan?

The Indian Army’s post-engagement review of the Sunjuwan case produced lessons across operational, doctrinal, and design dimensions that have shaped subsequent practice. The operational lessons addressed the engagement itself, including the systematic clearance methodology that the brigade adopted under reinforcement from 9 Para Special Forces and Para Commando teams, the casualty extraction protocols used during structured entry and clearance, and the press communication doctrine that the Army would subsequently adopt for similar incidents. The doctrinal lessons addressed cantonment security across the Northern and Western Commands, including the introduction of motion-sensor coverage at perimeter sections previously considered low-risk, the establishment of internal patrolling regimes that cover the gap between perimeter sentry duty and dispersed quarter guard duty, and the integration of cantonment security into the broader tactical posture against fidayeen breaches. The design lessons addressed cantonment construction, including the recommendation that internal hardened-shelter rooms be incorporated into family quarters in new construction so that families would have defensible positions in the event of a perimeter breach. The lessons have been implemented unevenly. New construction has been more compliant than retrofit on existing cantonments. The hardened-shelter recommendation in particular has been implemented in some new cantonments but has not been retrofitted across the bulk of existing cantonment housing. The pattern of uneven implementation reflects budgetary constraints and the prioritisation of forward operational posts over rear-area cantonments in the allocation of security upgrades. The pattern is itself a subject of continuing debate within the Indian defence community, with critics arguing that rear-area cantonments remain insufficiently hardened against the threat that Sunjuwan demonstrated.

Q: How does the Sunjuwan-to-Naseerabad chain compare to other attack-to-elimination chains in India’s counter-terror response?

The Sunjuwan-to-Naseerabad chain sits within a broader pattern of attack-to-consequence chains in the contemporary Indian counter-terror response, and comparison with other chains in the pattern illuminates both the chain’s regularities and its specifics. The Pathankot attack of January 2016 produced the elimination of its mastermind Shahid Latif in October 2023, a chain of seven years and nine months that ended with a man shot inside a Sialkot mosque. The Dhangri attack of January 2023 produced the elimination of its alleged mastermind Abu Qasim in February 2023, a chain of approximately one month that ended with a point-blank shot inside a Rawalakot mosque. The Pahalgam attack of April 2025 produced Operation Sindoor in May 2025, a chain of less than a month that ended with kinetic strikes against terror infrastructure in Pakistani territory. The Sunjuwan-to-Naseerabad chain, with its duration of five years and eight months, sits between the Pathankot and Pahalgam extremes in temporal extent. The chains’ methodologies differ as well, ranging from the urban motorcycle-borne shooting of the Pathankot case through the mosque-based point-blank shooting of the Dhangri case to the kidnap-and-disposal pattern of the Sunjuwan case to the open kinetic strike of the Pahalgam case. The methodological diversity supports the assessment that the operational architecture is methodologically flexible and theatre-aware. The chains’ common features are consistency of target selection across cases, with each chain ending at an actor in the chain of responsibility for the attack that initiated it; the absence of public claim of responsibility from the Indian state, with each chain’s output presented as the work of unidentified actors; and the public visibility of the outputs, with each output discoverable and identifiable in ways that produce deterrent effect on the broader handler population. Sunjuwan-to-Naseerabad is one chain in the pattern, and the pattern as a whole defines the broader Indian counter-terror posture of the contemporary period.