Most targeted eliminations in Pakistan follow a recognizable signature: motorcycle-borne gunmen approach their target on foot or at a known location, fire at close range, and vanish into congested streets within seconds. Khwaja Shahid, known by his operational alias Mian Mujahid, broke that pattern in every conceivable dimension. He was not shot on a street corner or inside a mosque during prayers. He was kidnapped from the Neelum Valley of Pakistan-Occupied Kashmir, held for days while Pakistan’s Inter-Services Intelligence and army scrambled to locate him, tortured extensively, beheaded, and dumped near the Line of Control alongside the body of another unidentified individual. His killing, confirmed in early November 2023, remains the single most violent deviation from the standard modus operandi that defines the broader campaign of covert eliminations on Pakistani soil, and it raises questions that no other case in the series forces the analyst to confront.

Shahid was not a minor operative whose death could be dismissed as a local feud or a criminal settling of scores. He was identified by Indian security forces as one of the masterminds behind the February 2018 terror attack on the Sunjuwan Military Station in Jammu, a predawn assault that killed seven people, including five soldiers from the Jammu and Kashmir Light Infantry and one civilian, while wounding twenty others. The attack targeted not just combatants but the families who lived inside the military station, and the choice to strike a brigade headquarters housing women and children marked Sunjuwan as one of the most provocative terror operations since the 2016 Uri attack. That Shahid, one of the men who allegedly planned that assault, was found beheaded near the very border he had helped terrorists cross five years earlier carries a symmetry that no analytical framework can fully resolve: was this justice, vengeance, or something else entirely?

The answer depends on what one believes the beheading represents. If it belongs to the same campaign of targeted eliminations that has killed over twenty India-wanted terrorists in Pakistan since 2021, then the method deviation demands explanation. The campaign’s consistency is its calling card; the motorcycle-and-pistol signature is what separates it from the background noise of Pakistan’s endemic violence. A beheading is not consistent. It is loud, theatrical, and physically demanding in a way that precision shootings are not. If, on the other hand, the beheading was the work of a different actor, perhaps an internal faction within Pakistan-Occupied Kashmir or a tribal justice mechanism, then Shahid’s case must be separated from the pattern entirely. This article argues that the target-selection logic connects Shahid’s elimination firmly to the broader campaign, even as the method forces a reckoning with the possibility that the campaign adapts its operational approach to terrain and circumstance in ways the standard signature does not reveal.

The Killing

The sequence of events that ended Khwaja Shahid’s life unfolded across several days in late October and early November 2023, and the timeline itself is analytically significant. Reports of his kidnapping surfaced on November 4 and 5, 2023, when Pakistani media and social media accounts began circulating the news that a Lashkar-e-Taiba commander from the Neelum Valley had been abducted by unknown assailants. The abduction itself was reportedly carried out by unidentified men who seized Shahid from his area of residence in the Neelum Valley, a narrow, mountainous river valley running parallel to the Line of Control in Pakistan-Occupied Kashmir. The valley’s geography matters: it is not Karachi, with its congested streets and easy motorcycle escape routes. It is not Lahore, where a shooter can disappear into millions of pedestrians. The Neelum Valley is remote, sparsely populated by comparison, flanked by steep mountain terrain, and dotted with Pakistan Army checkpoints and forward positions. Operating there is fundamentally different from operating in Punjab or Sindh.

Shahid’s abduction sent what multiple Indian and Pakistani media reports described as shockwaves through the ISI and the Pakistan Army. The choice of the word “shockwaves” in the Times of India report is revealing: it implies that the ISI considered Shahid to be under its protection and that the kidnapping represented a breach of the security perimeter the intelligence agency believed it maintained over its assets in the region. The ISI and Pakistan Army reportedly launched efforts to locate Shahid, but these efforts failed. His beheaded body was discovered near the Line of Control in the Athmuqam sector of Pakistan-Occupied Kashmir, reportedly alongside the body of another unidentified individual. Both bodies were taken to a Pakistan Army base camp in the Neelum Valley.

The condition of Shahid’s body added another layer to the analytical picture. Multiple reports stated that his body bore signs of severe torture before the beheading. This is not the hallmark of a precision operation designed for speed and deniability. A shooting takes seconds. Torture and beheading take hours, require a secure location where the victim can be held without detection, and leave behind far more forensic evidence than a spent cartridge casing on a street. The operational requirements for this type of killing are categorically different from the requirements for the motorcycle shootings documented across the campaign’s timeline. Whoever killed Shahid had the time, the space, and the physical security to hold him for days, interrogate or torture him, execute him by decapitation, and transport his body to a location near the LoC without being intercepted by the Pakistan Army or ISI despite what appears to have been an active search.

No organization claimed responsibility for the killing. This silence is consistent with the broader pattern of targeted eliminations in Pakistan, where no group has ever stepped forward to take credit for any of the killings attributed to the campaign. The silence serves the same strategic function across all cases: it denies Pakistan’s government a named antagonist against whom to direct diplomatic or military retaliation. A claimed killing is an act of war or terrorism, depending on one’s perspective. An unclaimed killing is an unsolved crime, and unsolved crimes do not produce United Nations resolutions or trigger Article 5 consultations.

The forensic dimension of the killing also deserves attention. A beheading, unlike a shooting, leaves behind significant biological evidence: the implement used for decapitation, potential DNA from the perpetrators on the body or at the holding site, trace evidence from the location where the victim was held during captivity, and the logistical artifacts of a multi-day operation (food supplies, bedding, restraints, communication equipment). Whether Pakistani investigators processed this evidence and what it revealed is not publicly known. The absence of any public investigative finding, including an identification of the perpetrators or even a preliminary suspect profile, follows the broader pattern of Pakistani investigations into these killings: initial media attention, followed by silence, followed by the case disappearing from public discourse without resolution. This investigative pattern may reflect genuine inability to solve the cases, political decisions to suppress findings that would be embarrassing to the state, or a calculated choice not to pursue investigations that might expose uncomfortable truths about the permeability of Pakistan’s security architecture.

The timing of Shahid’s killing placed it within what intelligence analysts and Indian media would later describe as the November 2023 cluster, a two-week window during which three India-wanted terrorists were eliminated in rapid succession across geographically dispersed locations in Pakistan. Shahid’s body was found around November 5. Akram Khan, an LeT terrorist in Khyber Pakhtunkhwa’s Bajaur, was shot dead on November 9. Raheem Ullah Tariq, a close associate of Masood Azhar within Jaish-e-Mohammed, was shot dead in Karachi on November 13. Three eliminations in fourteen days, across three different regions of Pakistan, using at least two different methods (beheading for Shahid, shooting for the other two), targeting operatives from two different organizations. The cluster is itself an analytical artifact that demands its own treatment, but for the purposes of this profile, the relevant point is that Shahid’s killing was not an isolated incident. It occurred within a compressed operational window that suggests coordination, planning, and the capacity to execute multiple operations near-simultaneously.

Who Was Khwaja Shahid

Khwaja Shahid, operating under the alias Mian Mujahid, was a Lashkar-e-Taiba commander and a resident of the Neelum Valley in Pakistan-Occupied Kashmir. The Neelum Valley is significant to his biography not merely as a place of residence but as a geographic corridor that has been central to the infiltration of terrorists across the Line of Control into Indian-administered Jammu and Kashmir for decades. The valley runs northeast from Muzaffarabad, the capital of Pakistan-Occupied Kashmir, toward the LoC, and its dense forests, high-altitude passes, and relatively sparse Pakistani military presence along certain stretches have historically made it one of the primary transit routes for cross-border terrorism.

Shahid’s organizational affiliation with Lashkar-e-Taiba places him within the most lethal and internationally recognized terror network operating from Pakistani soil. LeT, founded in the early 1990s as the armed wing of Markaz-ud-Dawa-wal-Irshad, grew under Hafiz Saeed’s leadership into an organization responsible for some of the deadliest terrorist attacks in Indian history, most notoriously the November 2008 Mumbai attacks that killed 166 people over three days. The organization’s structure is hierarchical but geographically distributed, with regional commanders responsible for specific operational theaters. Shahid’s position within this structure was that of a regional commander operating in the PoK sector, responsible for facilitating cross-border infiltration and coordinating operations targeting Indian military installations in Jammu and Kashmir.

The distinction between Shahid’s organizational home in LeT and the Sunjuwan attack’s attribution to Jaish-e-Mohammed in some accounts requires careful parsing. The Indian security establishment identified Shahid as one of the masterminds of the Sunjuwan attack, and Indian media consistently reported his LeT affiliation. Separately, the three attackers who physically carried out the assault on the Sunjuwan Military Station were identified as Pakistani nationals linked to Jaish-e-Mohammed, and the Indian Army identified Mufti Waqas, a JeM commander killed in Awantipora on March 5, 2018, as the attack’s operational mastermind. The apparent contradiction dissolves when one understands how Pakistan-based terror organizations cooperate in practice. LeT and JeM, despite theological differences (LeT is Ahl-e-Hadith; JeM is Deobandi), share infrastructure, intelligence, logistics networks, and, crucially, ISI handlers. An operation masterminded at the strategic planning level by an LeT commander using JeM foot soldiers is not unusual; it reflects the ISI’s practice of deploying multiple organizations as interchangeable instruments. Shahid’s role was reportedly in the planning and infiltration-facilitation phase, the upstream work of identifying the target, mapping the route, and arranging the logistics that enabled the three JeM attackers to reach the Sunjuwan Military Station in the predawn hours of February 10, 2018.

Shahid’s career within LeT’s PoK apparatus would have required capabilities that go well beyond pulling a trigger. Facilitating cross-border infiltration from the Neelum Valley into Indian-administered Kashmir demands intimate knowledge of the terrain, including seasonal variations in snow cover, river crossings, and forest density that affect which routes are passable at which times of year. It requires established relationships with local guides, safe house operators, and logistics providers on both sides of the LoC. It requires knowledge of Indian Army patrol patterns, sensor placements, and the electronic surveillance grid that India has progressively deployed along the border since the early 2000s. Commanders in this role function as the connective tissue between the terror organization’s strategic leadership in Punjab (Lahore, Muridke, Bahawalpur) and the operational front line along the LoC. They translate leadership directives into actionable infiltration plans, and when those plans result in attacks like Sunjuwan, they bear direct responsibility for the carnage that follows.

The Neelum Valley’s role as both Shahid’s home and his operational theater also explains why he was not eliminated using the standard motorcycle-and-pistol method. The valley is not an urban environment. There are no congested bazaars to disappear into, no anonymous apartment blocks to use as safe houses, and no motorcycle-friendly roads that allow rapid escape into unmonitored territory. An operator attempting the standard method in the Neelum Valley would face checkpoints, mountain terrain, limited escape routes, and a Pakistan Army presence that, while not sufficient to prevent a kidnapping, would almost certainly detect and intercept a motorcycle fleeing a shooting. The terrain demanded a different approach, and the approach that was used, kidnapping followed by captivity, interrogation, and execution at a secure location, may represent the campaign’s adaptation to an environment that the standard signature cannot penetrate.

The Attacks Khwaja Shahid Enabled

The Sunjuwan Military Station sits in the city of Jammu, functioning as the headquarters of the 36th Brigade of the Indian Army and housing not only military personnel but their families, including women and children who lived in family quarters within the station’s perimeter. The choice to attack this installation was not random. Brigade headquarters are among the most sensitive military targets in any theater, and the presence of families within the compound transformed the attack from a purely military operation into one with inescapable civilian dimensions. Indian parliamentarian Asaduddin Owaisi would later highlight the demographics of the casualties, noting that five of the seven killed were Kashmiri Muslims serving in the Indian Army, a fact that complicated any attempt to frame the attack along simple communal lines.

The assault began at approximately 4:10 AM Indian Standard Time on February 10, 2018, a Saturday, when three heavily armed terrorists infiltrated the military station. The timing was not coincidental; February 10 marked the anniversary of the execution of Afzal Guru, convicted for his role in the 2001 Indian Parliament attack, and terror groups operating in Kashmir have historically used anniversary dates to time their most provocative operations. The symbolic weight of the date amplified the attack’s psychological impact beyond its immediate tactical outcome.

The three attackers wore Indian Army combat fatigues, a deception tactic that delayed recognition of the threat in the critical first seconds of the assault. They carried AK-56 rifles, a variant of the AK-47 widely available in the Pakistan-Afghanistan weapons pipeline, along with under-barrel grenade launchers and a substantial supply of ammunition including grenades. The weapons loadout indicated preparation for a prolonged engagement rather than a quick strike-and-flee operation. The attackers intended to hold ground, maximize casualties, and sustain combat for as long as possible.

The predawn timing exploited the period of lowest alertness in any military installation. Soldiers were asleep. Families were in their quarters. The guard rotation was at its thinnest. When the firing began, the initial confusion was compounded by the attackers’ Indian Army uniforms, which created uncertainty among defenders about whether they were facing an external assault or an internal incident. By the time the nature of the attack was confirmed and a coordinated response organized, the attackers had penetrated deep enough into the installation to reach the family quarters.

The casualties tell the story of what the attackers encountered and chose to engage. Subedar Madan Lal Choudhary, Subedar Mohammad Ashraf Mir, Havildar Habibullah Qurashi, Naik Manzoor Ahmed, and Lance Naik Mohammad Iqbal, all serving in the 1st Battalion of the Jammu and Kashmir Light Infantry, were killed. Lance Naik Mohammad Iqbal’s father, a civilian visiting his son at the station, was also killed. Twenty people were wounded, including fourteen soldiers, five women, and one child. The wounding of women and children confirmed that the attackers had fired in or near the family quarters, a fact that cannot be explained away as collateral damage given the physical layout of the installation. The family quarters were a distinct area within the station. Reaching them required movement through the compound. The attackers moved toward families, not away from them.

The Indian Army’s response evolved into a sustained counter-assault that lasted approximately twenty-four hours. All three attackers were eventually killed. The prolonged duration of the engagement reflected both the attackers’ preparation, they had carried enough ammunition to sustain a day-long firefight, and the Army’s need to clear the installation methodically, room by room, to protect the families still sheltering inside. The operational challenge of conducting a clearance operation in a military station housing hundreds of families while under active fire from entrenched, suicidally committed attackers is among the most demanding scenarios any security force can face.

The aftermath rippled outward from Sunjuwan in multiple directions. Thousands of local residents gathered in the hometowns of the slain soldiers across Kupwara, Tral, and Anantnag to mourn. Schools in the Jammu region were shut. A high alert was sounded across Jammu and Kashmir. Anti-Pakistan slogans were raised in the Jammu and Kashmir Assembly. The Indian Army declared it was “above religion” in response to attempts to communalize the sacrifices of the predominantly Muslim soldiers who had died defending their station. The Indian security establishment began the process of identifying the attack’s masterminds, a process that would lead, through intelligence channels whose specifics remain classified, to Khwaja Shahid’s name.

The Sunjuwan attack occupied a specific position in the escalatory trajectory of Pakistan-sponsored terrorism against India. It followed the Pathankot airbase attack of January 2016, which had targeted India’s most sensitive military aviation infrastructure, and the Uri Army camp attack of September 2016, which had killed nineteen soldiers and triggered India’s first acknowledged surgical strikes across the LoC. Sunjuwan continued the pattern of targeting Indian military installations within Jammu and Kashmir, but its targeting of family quarters represented an escalation in the willingness to inflict civilian casualties within a military context. Each successive attack raised the threshold of Indian tolerance, and each attack generated intelligence leads that would eventually feed into the campaign of targeted eliminations that reached Shahid five years later.

The trajectory from Uri to Sunjuwan illustrates how each attack compressed the space for restraint. After Uri, India responded with surgical strikes, a limited, conventional military action targeted at terrorist launch pads across the LoC. The strikes were acknowledged publicly, a departure from India’s traditional ambiguity about cross-border operations, and they established a precedent: India would use military force in response to major terrorist attacks. Sunjuwan arrived less than eighteen months later, testing whether that precedent would hold or whether India’s response capability had been exhausted by the Uri experience. The decision not to respond to Sunjuwan with another round of surgical strikes did not indicate retreat; it indicated a recalibration. The overt military response had been demonstrated. Something else was being developed. The campaign that eventually reached Shahid represents that “something else”: a sustained, deniable, methodical alternative to periodic military spasms that requires no ceasefire negotiation, produces no international crisis, and imposes a continuous rather than episodic cost on Pakistan’s terror infrastructure.

The intelligence investigation following the Sunjuwan attack traced the planning chain backward from the three dead attackers to their handlers and facilitators. The attackers themselves were identified as Pakistani nationals: Kari Mushtaq, Mohammad Khalid Khan, and Mohammad Adil. Their weapons, equipment, and the combat fatigues they wore pointed to a supply chain originating in Pakistan. The infiltration route they used to reach Sunjuwan ran through the Neelum Valley and across the LoC, precisely the corridor that Shahid managed as an LeT regional commander. The forensic and intelligence trail from the attackers’ equipment and entry point to the facilitators who arranged their crossing of the LoC is a chain that, while not publicly detailed in its entirety, connects the Sunjuwan crime scene to Shahid’s operational theater with the logic of geographic and organizational responsibility. He controlled the corridor. They used the corridor. The connection is structural, not circumstantial.

The five-year gap between the Sunjuwan attack and Shahid’s elimination is itself analytically significant. Five years is long enough to suggest that the identification of Shahid as a mastermind did not immediately produce an operational response. The campaign of targeted eliminations did not begin in earnest until 2022, and the acceleration through 2023 suggests either a buildup phase during which intelligence was gathered and assets were positioned, or a policy decision that was made well after the attacks themselves. Shahid was not killed in the heat of the moment. He was killed years after the fact, which transforms his elimination from an act of reactive retaliation into something more deliberate: a statement that accountability has no expiration date, that the passage of time does not convert a safe haven into a sanctuary.

Network Connections

Shahid’s position within Lashkar-e-Taiba’s command structure placed him at the intersection of several networks that collectively form the infrastructure of cross-border terrorism in the Jammu and Kashmir theater. Understanding these connections requires mapping both the organizational hierarchy above him and the operational networks he managed below.

At the apex of the organizational chain sits Hafiz Muhammad Saeed, the founder and spiritual leader of LeT and its charitable front, Jamaat-ud-Dawa. Saeed, convicted by Pakistani courts and sentenced to multiple prison terms totaling decades, remains the ideological center of gravity for the entire LeT ecosystem. Below Saeed, the organization’s operational command is distributed among regional commanders, military commanders responsible for specific operational theaters, and logistics chiefs who manage the supply chains of weapons, funds, and personnel that sustain cross-border operations. Zaki-ur-Rehman Lakhvi, the operational commander of the 2008 Mumbai attacks, represented the highest tier of military command. Amir Hamza, the LeT co-founder who survived an attack in Lahore in 2026, occupied the organizational-founding tier.

Shahid operated at the regional commander level, a tier below the organization’s strategic leadership but directly above the foot soldiers and facilitators who carry out specific operations. His operational theater, the Neelum Valley and its associated infiltration corridors into Indian-administered Kashmir, was one of several geographic sectors that LeT maintained along the LoC. Each sector had its own commander, its own network of safe houses, its own guides, and its own communication channels back to the central leadership. The decentralized nature of this structure meant that the loss of any single sector commander would degrade but not destroy the infiltration capability in that sector, because the underlying infrastructure of safe houses, guide networks, and local relationships would survive the commander’s elimination. However, the commander’s death would disrupt the coordination function: the ability to translate strategic directives from Lahore or Muridke into specific, timed infiltration operations through specific mountain passes at specific seasons.

Shahid’s network connections extended beyond LeT’s formal hierarchy into the murkier territory of inter-organizational cooperation under ISI auspices. The Sunjuwan attack illustrated this cooperation: Shahid, an LeT commander, allegedly planned and facilitated an operation executed by JeM attackers. This type of cross-organizational operation is not an aberration; it is a design feature of how the ISI manages its stable of militant groups. The ISI maintains relationships with multiple organizations precisely because each offers different capabilities: LeT provides geographic knowledge of the LoC corridor and established infiltration networks; JeM provides the ideologically committed fidayeen attackers willing to carry out suicide operations; Hizbul Mujahideen provides local Kashmiri networks on the Indian side. By mixing and matching these capabilities, the ISI can assemble operations that no single organization could execute alone.

The ISI connection is central to understanding both Shahid’s operational career and the significance of his death. Reports of his kidnapping stated that the news sent shockwaves through the ISI, a detail that implies Shahid was considered an ISI asset under the agency’s protection. The Neelum Valley, with its proximity to the LoC and its strategic importance as an infiltration corridor, is territory where the Pakistan Army and ISI maintain a significant presence. The fact that Shahid could be kidnapped from this area, held for days, and killed without being recovered by the ISI or the Pakistan Army constitutes a profound intelligence failure for Pakistan, one that demonstrates the reach and operational security of whoever carried out the operation.

Shahid’s connections to other eliminated targets in the campaign can be traced through the organizational and geographic networks he inhabited. Abu Qasim, the LeT commander shot at point-blank range inside a mosque in Rawalakot, PoK, in September 2023, operated in the same Pakistan-Occupied Kashmir theater as Shahid. Muhammad Riaz, killed in Pakistan-administered Kashmir in September 2023, was another LeT commander in the PoK sector. The geographic clustering of these eliminations in Pakistan-Occupied Kashmir during the September to November 2023 period suggests a focused campaign against LeT’s LoC-adjacent infrastructure, systematically removing the commanders who facilitate infiltration from PoK into Indian-administered territory. Shahid’s elimination was not an isolated event; it was part of a targeted dismantling of the infiltration command layer in the most operationally significant geographic sector of the entire conflict.

The connection to Shahid Latif, the JeM commander who masterminded the 2016 Pathankot airbase attack and was shot dead inside a mosque in Sialkot in October 2023, illuminates the cross-organizational dimension. Latif and Khwaja Shahid occupied analogous positions within their respective organizations: both were mid-tier commanders responsible for specific high-profile attacks, both were sheltered by Pakistan’s security apparatus after those attacks, and both were eliminated within weeks of each other in late 2023. The parallel suggests that the campaign’s target-selection logic operates at the organizational-function level, not the organizational-affiliation level. The question is not “which organization does this person belong to?” but “what function does this person perform, and does eliminating them degrade the threat?”

The network analysis can be extended further by examining Shahid’s probable connections to the broader PoK-based terror infrastructure. The Neelum Valley is not the only infiltration corridor along the LoC; multiple routes exist across the 740-kilometer Line of Control, each managed by regional commanders who may report to different organizations but who collectively form a permeable membrane through which Pakistan projects armed capability into Indian territory. Shahid’s operational peers would have included LeT sector commanders in the Poonch-Rajouri corridor, the Kupwara corridor, and the Gurez-Mushkoh corridor, each managing their own networks of guides, safe houses, and logistics chains. The elimination of one sector commander does not shut down cross-border infiltration, but it degrades the specific capability in that sector and forces the organization to either promote a less experienced replacement, divert another commander from a different sector (weakening that sector’s capability), or temporarily suspend operations through the affected corridor.

The cascading effects of Shahid’s elimination can be traced through two mechanisms. The first is organizational disruption: Shahid’s knowledge of his sector’s infrastructure, including safe house locations, guide identities, route options, and communication protocols, dies with him. His replacement must rebuild this institutional knowledge, a process that takes months and during which the sector is operationally degraded. The second is psychological disruption: Shahid was kidnapped and beheaded despite being in a Pakistan Army-adjacent zone under apparent ISI protection. Every other LeT commander in PoK now knows that the protective umbrella has a hole in it, and that hole is large enough for an operational team to kidnap, hold for days, and behead a senior commander. The psychological impact on the remaining commanders’ willingness to continue operating in exposed positions cannot be quantified, but it is reasonable to infer that at least some commanders have modified their behavior, reduced their operational profiles, or relocated from their established positions in response to the demonstrated threat. Each of these behavioral modifications imposes a cost on LeT’s operational capability, even without additional eliminations.

Sardar Hussain Arain, the JuD operative responsible for the madrassa network who was shot dead in Nawabshah, represents a different type of network connection: the organizational-infrastructure link. Arain’s role in managing the Jamaat-ud-Dawa madrassa network connected him to the recruitment and radicalization pipeline that produces the foot soldiers organizations like LeT deploy through corridors managed by commanders like Shahid. The relationship between the recruitment infrastructure (Arain’s domain) and the infiltration infrastructure (Shahid’s domain) is sequential: recruits are radicalized through the madrassa network, trained in LeT camps, and then funneled to sector commanders like Shahid for cross-border deployment. Eliminating both the recruiter and the deployer attacks the terror pipeline at two separate points simultaneously, compounding the degradation effect.

The network connections also illuminate a dimension of the campaign that is often underappreciated in media coverage: the intelligence value of each elimination beyond its immediate tactical impact. When a commander like Shahid is kidnapped and held for several days before execution, the possibility exists that the captivity period was used for interrogation. The intelligence extracted from a regional commander with intimate knowledge of LeT’s PoK infrastructure, including safe house locations, guide identities, communication protocols, upcoming operation plans, and ISI handler contacts, would be strategically invaluable. Whether interrogation occurred in Shahid’s case is unknown, but the extended captivity period distinguishes his case from the instant-kill shootings where no such intelligence extraction is possible. If the campaign does extract intelligence from certain captives before execution, each killing becomes not only a subtraction from the enemy’s ranks but an addition to the campaign’s own intelligence picture, a dual benefit that compounds with each successive operation. This operational logic, if it applies, would explain why certain high-value targets in sensitive positions are subjected to the more complex and risky kidnapping methodology rather than the simpler and safer shooting: the intelligence they carry in their heads is worth the additional operational investment and risk.

The Hunt

The intelligence preparation required to locate, track, and ultimately kidnap Khwaja Shahid in the Neelum Valley represents arguably the most complex operational challenge documented in any single case within the broader campaign. Urban assassinations, while dangerous, benefit from the anonymity and fluidity that cities provide. The Neelum Valley offers none of these advantages. It is a defined geographic space with limited entry and exit points, significant Pakistan Army presence, and a population small enough that outsiders are noticed. Whatever entity conducted this operation required capabilities that go substantially beyond what the standard motorcycle shooting requires.

The first capability is intelligence on Shahid’s identity, location, and daily patterns. Shahid had been identified by Indian security forces as a Sunjuwan mastermind, but identifying someone is not the same as locating them in a remote valley in Pakistan-Occupied Kashmir. The gap between identification and location would have required either signals intelligence (intercepted communications revealing his location), human intelligence (an informant within LeT’s PoK structure or within the local community), or a combination of both. Given the ISI’s protective relationship with high-value militant assets in PoK, penetrating that security perimeter to establish Shahid’s precise location would have required either long-term infiltration of his network or the recruitment of someone with direct access to him.

The second capability is operational presence in the Neelum Valley. The kidnapping required a team physically present in the area, capable of seizing Shahid, transporting him to a secure location, and holding him for days without detection. In an urban environment, a rented apartment can serve as a temporary holding site. In the Neelum Valley, the options are fewer: a house in a village where neighbors would notice unusual activity, a structure in the forested hills above the valley floor, or a location near the LoC where terrain provides natural concealment. The team had to be present in the area long enough to conduct the operation but not so long that their presence attracted attention from the Pakistan Army units stationed nearby.

The third capability is the ability to hold a captive for an extended period while the ISI and Pakistan Army were actively searching. Reports indicate that Shahid was abducted around November 2 or 3, and his body was found around November 5 or 6, suggesting a captivity period of roughly three days. During those three days, the ISI and Pakistan Army knew he was missing and were attempting to locate him. The team holding Shahid maintained operational security throughout this search, which required either a location that the Pakistani security forces did not think to check or the ability to move Shahid through the terrain without being detected by military patrols and checkpoints.

The fourth capability is the willingness and ability to conduct a beheading. Unlike a shooting, which can be performed by any reasonably trained individual with a firearm, beheading is a method that carries specific cultural, psychological, and operational connotations. In the Pakistan-Afghanistan theater, beheadings are most commonly associated with the Tehrik-i-Taliban Pakistan and tribal justice mechanisms in the Pashtun tribal belt. They are not associated with the precision-oriented, deniability-focused operations that characterize the broader targeted elimination campaign. The use of this method in Shahid’s case may reflect one of several possibilities: the operatives employed in the Neelum Valley were drawn from a different background than those used in urban shootings; the method was chosen to send a specific message to other LeT commanders in the PoK corridor; or the circumstances of the operation, including the extended captivity period, evolved the outcome from a planned execution into something more visceral.

The fifth capability is extraction. After the killing, the team had to either escape the Neelum Valley or disappear into the local population. The body’s discovery near the LoC suggests either that the killing occurred near the border or that the body was transported there, both options requiring movement through terrain where the Pakistan Army maintains forward positions. The proximity to the LoC is itself analytically significant: it may suggest that the operators crossed the border before or after the operation, using the same infiltration corridors that LeT had long exploited in the opposite direction. If this interpretation is correct, the operation represents a tactical irony: the network’s own infrastructure was turned against its commander.

The overall intelligence profile of the Shahid operation points to an entity with strategic patience (the ability to wait for the right conditions), local knowledge (familiarity with the Neelum Valley’s terrain and population patterns), infiltration capability (the ability to insert a team into a Pakistan Army-adjacent area), holding capability (a secure location for multi-day detention), and extraction capability (the ability to leave the area undetected after the killing). This profile is consistent with a sophisticated intelligence agency conducting a covert operation in denied territory, though it does not exclude the possibility of a local proxy force operating under external direction with substantial logistical and intelligence support.

The operational contrast between the Shahid kidnapping and the standard motorcycle shootings illuminates the breadth of the campaign’s tactical repertoire. Consider the killing of Ziaur Rahman in Karachi, a textbook example of the standard method: two motorcycle-borne gunmen approached Rahman during his evening walk, fired multiple rounds, and disappeared into Karachi’s traffic within moments. The entire operation, from approach to escape, lasted less than thirty seconds. Rahman’s killing required intelligence on his walking routine, a two-person team with a motorcycle and a handgun, and knowledge of the escape route. Shahid’s killing required intelligence on his location in a mountain valley, a multi-person team capable of conducting a kidnapping against a trained LeT commander, a secure holding location invisible to searching Pakistani security forces, the logistics to sustain a multi-day detention, the willingness to conduct a beheading, and an extraction route through territory patrolled by the Pakistan Army. The operational complexity differs by an order of magnitude, yet both operations achieved the same strategic outcome: the permanent removal of an India-designated terrorist from the operational landscape.

This disparity in operational complexity raises the question of resource allocation within the campaign. If the standard motorcycle shooting requires a small team and minimal infrastructure, while the Neelum Valley kidnapping required a substantial team and days of sustained operational presence, then the decision to target Shahid implied a willingness to invest significantly greater resources in his elimination than in the elimination of urban targets. That investment decision, whether made by a single intelligence agency or by a coordinating authority directing multiple operational arms, reflects a judgment that Shahid’s value as a target justified the increased risk and resource expenditure. His position as a Sunjuwan mastermind and LeT’s PoK infiltration commander made him a high-priority target whose elimination would degrade a specific capability (cross-border infiltration from the Neelum corridor) that lower-tier urban operatives could not replicate.

Pakistan’s Response

Pakistan’s official response to Khwaja Shahid’s kidnapping and killing operated on two parallel tracks that collectively reveal the contradictions embedded in the state’s relationship with designated terrorists living under its protection. The first track was the security response: the ISI and Pakistan Army’s attempt to locate Shahid after his abduction. The second track was the political and diplomatic response, which was, characteristically, muted to the point of near-silence.

The security response was notable for its speed and its failure. Multiple reports indicated that the ISI treated Shahid’s kidnapping as a serious breach, triggering search operations in the Neelum Valley to locate and recover him. The fact that the ISI responded with urgency confirms, by implication, that it considered Shahid a protected asset whose safety fell within the agency’s responsibility. This is not the response of a government that views designated terrorists as criminals to be apprehended; it is the response of a handler who has lost a managed asset. The search failed. The ISI could not locate Shahid before his captors killed him, and the discovery of his beheaded body near the LoC represented a public failure of the intelligence agency’s protective capability in its own backyard.

The political response followed the pattern established in previous cases. Pakistan’s government did not issue a formal public statement attributing the killing to any specific actor or intelligence agency. There was no diplomatic protest of the kind that eventually emerged regarding the killings of Muhammad Riaz and Shahid Latif, which Pakistani Foreign Secretary Mumtaz Zahra Baloch would formally attribute to Indian intelligence in January 2024. Shahid’s case was conspicuously absent from these formal accusations, which focused on the two cases where Pakistani investigators had apparently gathered the most evidence of Indian involvement. The omission may reflect the fact that the beheading’s methodology was sufficiently different from the standard pattern that Pakistani investigators were less confident in attributing it to the same campaign, or it may reflect the political difficulty of publicly acknowledging that a designated terrorist (one identified by India as a Sunjuwan mastermind) was living under ISI protection in Pakistan-Occupied Kashmir.

The broader context of Pakistan’s response to the elimination campaign illuminates the structural bind in which Islamabad finds itself. Publicly acknowledging the killings means admitting that India-designated terrorists are living on Pakistani soil, which validates India’s longstanding accusation that Pakistan shelters terrorism. Protesting the killings means demanding international sympathy for the murdered men, which requires explaining why those men were living freely in Pakistan when they were wanted for attacks that killed Indian soldiers and civilians. Investigating the killings means potentially uncovering the operational methods being used against Pakistan, which means admitting that foreign intelligence operations are being conducted with impunity inside Pakistani territory. Each possible response creates problems that are arguably worse than silence. Pakistan’s choice of near-silence on Shahid’s case, and selective acknowledgment of only certain killings in the formal diplomatic record, reflects a calculated determination to address only those cases where the evidence is strongest and the victim’s profile is least embarrassing.

The Pakistani media’s treatment of Shahid’s killing was more forthcoming than the government’s response but still reflected the uncomfortable realities of covering the death of a man whom India considered a terror mastermind. Reports identified Shahid by his LeT affiliation and acknowledged his connection to the Sunjuwan attack. The coverage positioned his death within the series of killings of India-wanted terrorists on Pakistani soil, drawing the connection that the government avoided making explicitly. Pakistani media also reported the ISI’s failed search, a detail that exposed the intelligence agency’s protective role while simultaneously highlighting its failure to fulfill that role in this case.

The military establishment’s response took the form of heightened alert in the PoK sector following Shahid’s killing and the broader cluster of eliminations in the September-November 2023 period. The Pakistan Army reportedly increased security around known militant figures in the region, a measure that tacitly acknowledged both the identities of the individuals being protected and the threat they faced. This response, while operationally logical, created the absurd spectacle of a national army deploying resources to protect individuals who are designated terrorists under international and Indian law, individuals whose activities have included planning attacks on military installations that killed soldiers from another nation’s army. The spectacle is precisely the kind of contradiction that Pakistan’s relationship with terror organizations continuously produces and that the targeted elimination campaign continuously exploits.

The diplomatic dimension of Pakistan’s response merits further analysis because of what it reveals about the hierarchy of victims in Pakistan’s narrative strategy. When Pakistan’s Foreign Secretary presented formal accusations of Indian involvement in targeted killings in January 2024, the cases highlighted were Muhammad Riaz and Shahid Latif. Both were framed as victims of Indian aggression, with their terrorist designations by India treated as contested allegations rather than established facts. Shahid’s case was not prominently featured in these diplomatic representations, and the omission is instructive. Shahid’s connection to the Sunjuwan attack, with its imagery of soldiers and their families killed in a predawn assault, made him a problematic victim for Pakistan to champion on the international stage. Defending the sovereignty violation requires defending the victim’s right to live unmolested, and defending Khwaja Shahid’s right to live unmolested requires explaining to the international community why a man who masterminded an attack on sleeping soldiers and their families was residing freely under ISI protection in Pakistan-Occupied Kashmir.

The Pakistani media landscape surrounding Shahid’s killing illustrated the tension between the state’s narrative requirements and the factual record. Some Pakistani outlets reported the killing straightforwardly, identifying Shahid as an LeT commander and noting his connection to the Sunjuwan attack. Others framed the killing as part of an Indian assassination campaign that constituted a violation of Pakistani sovereignty, a framing that positioned Pakistan as the aggrieved party without grappling with the question of why the aggrieved party was sheltering the planners of cross-border terrorism. A third category of coverage focused on the operational failure, using the ISI’s inability to prevent the kidnapping as evidence of institutional degradation within Pakistan’s security apparatus. Each of these framings served a different audience and a different political purpose, but none of them resolved the fundamental contradiction at the heart of Pakistan’s position: you cannot simultaneously deny sheltering terrorists and protest when those same terrorists are killed on your soil.

What This Elimination Reveals

Khwaja Shahid’s killing is the case that breaks the pattern and, in breaking it, reveals the pattern’s underlying logic more clearly than any case that conforms to it. The standard modus operandi documented across the broader campaign has six consistent elements: motorcycle-borne assailants, close-range firearms, predictable-location targeting (mosques, shops, streets), rapid escape, a single execution event (the target is approached and killed within seconds), and no claim of responsibility. Shahid’s case deviates from five of these six elements. He was kidnapped rather than approached for immediate killing. He was held for days rather than dispatched on the spot. He was beheaded rather than shot. His body was left near the LoC rather than at the point of attack. The only element that remains consistent is the sixth: no claim of responsibility.

A systematic deviation analysis across the six dimensions reveals both the divergence and the convergence. On target identification, the cases are identical: Shahid, like every other target in the campaign, was an India-designated terrorist whose elimination serves India’s counter-terrorism objectives. There is no ambiguity about whether Shahid was a “correct” target from the campaign’s perspective; he was a named mastermind of a specific attack that killed Indian soldiers. On target tracking, the cases diverge: the standard method involves locating a target’s predictable routine (prayer schedule, daily walk, shop opening) and intercepting them at that point, while Shahid’s case involved kidnapping, which requires a different and more intensive form of surveillance and a different operational approach to interception. On execution method, the divergence is total: shooting versus beheading, precision versus prolonged violence, speed versus duration. On escape and disposal, the standard method involves the attacker fleeing the scene while the body remains at the point of killing, while Shahid’s case involved the body being transported to a different location. On claim of responsibility, the cases converge: both the standard shootings and the beheading produce the same wall of silence.

The critical analytical question is whether this deviation matrix points toward the same campaign with a different method or a different actor entirely. Three possibilities deserve examination.

The first possibility is that the beheading represents a terrain adaptation. The argument is straightforward: the standard motorcycle-and-pistol method works in urban environments but is impractical in the Neelum Valley’s mountainous terrain. The campaign adapted its approach to the geographic constraints, employing kidnapping and prolonged captivity because the alternative, a rapid-fire assassination on a remote mountain road, would have been difficult to execute given the limited escape routes and Pakistan Army checkpoints. Under this interpretation, the beheading is a tactical variation, not a strategic departure, and the underlying campaign logic (identify target, track target, eliminate target, deny responsibility) remains intact. This interpretation is supported by the target-selection logic: Shahid’s profile (Sunjuwan mastermind, LeT commander, PoK-based infiltration facilitator) is entirely consistent with the broader campaign’s targeting criteria. The method changed because the terrain demanded it, but the doctrine held.

The second possibility is that the beheading was carried out by a different actor exploiting the same environment. The Neelum Valley borders both the LoC and the broader tribal dynamics of Pakistan-Occupied Kashmir, where internal feuds, criminal rivalries, and factional conflicts produce their own violence. Beheadings are associated with TTP methods and tribal justice mechanisms, not with the precision-shooting campaign. Under this interpretation, Shahid’s killing was the work of a local PoK faction, perhaps one with grievances against LeT or against Shahid personally, and its proximity in time to the broader November 2023 cluster was coincidental. This interpretation is weakened by the target profile: Shahid was not a tribal or TTP figure, and there is no reported history of LeT commanders being targeted by local factions in PoK. TTP’s targets are typically Pakistani security forces and state officials, not LeT commanders. The target-selection logic does not fit any known PoK faction’s operational pattern.

The third possibility is a hybrid: the killing was carried out by local proxies operating under external direction. Under this interpretation, the campaign’s controllers, lacking their own operational infrastructure in the Neelum Valley, recruited or directed local assets to carry out the operation using methods that reflected those assets’ operational culture rather than the campaign’s standard signature. The beheading, in this reading, was not a tactical choice by the campaign’s architects but a reflection of the proxy force’s own methods, which the campaign’s controllers either accepted or could not fully control. This interpretation has the virtue of explaining both the target-selection consistency (the controllers chose the target) and the method deviation (the proxies chose the method), but it raises questions about operational control and deniability that the standard method avoids.

This article argues for a modified version of the first possibility, supplemented by elements of the third. The target-selection logic, the timing within the November 2023 cluster, and the no-claim-of-responsibility pattern all connect Shahid’s killing to the broader campaign. The method deviation reflects a genuine adaptation to terrain, not a coincidental overlap with a different actor’s violence. The beheading may have resulted from the operational realities of conducting a multi-day captivity operation in a remote mountain valley, where the extended engagement with the target, including possible interrogation for intelligence purposes, produced an outcome more violent than the surgical precision of the urban shootings. Whether the proxies involved in the physical execution brought their own methodological preferences to the operation is a question that the available evidence cannot resolve but that the analytical framework must acknowledge.

The broader implication of this analysis extends beyond the individual case. If the campaign can adapt its methods to terrain, a standard shooting in Karachi, a mosque assassination in Sialkot, a kidnapping and beheading in PoK, then the safe-haven calculus changes for every Pakistan-sheltered terrorist regardless of where they are located. The lesson of Shahid’s case is not that the Neelum Valley is more dangerous than Karachi; it is that the campaign’s reach is not limited to the environments where its standard method works. The method is flexible. The doctrine is not: identify, track, eliminate, deny. Everything else is operational detail.

The implications for Pakistan’s safe-haven architecture are profound and specific. Pakistan has historically maintained a geographic strategy for managing its militant assets. Active operational commanders are positioned near the theaters where they are needed: LoC-adjacent commanders in PoK, Karachi-based logistics managers in Sindh, leadership figures in the relative security of Lahore and Rawalpindi. This geographic distribution serves multiple functions: it positions assets near their operational theaters, it distributes risk so that a single strike cannot eliminate an organization’s entire command structure, and it exploits the assumption that different environments require different counter-threat capabilities from any adversary.

Shahid’s case disrupts this geographic strategy by demonstrating that the campaign can project capability into each type of environment. The urban killings in Karachi demonstrated penetration of Pakistan’s largest city. The Shahid Latif killing in Sialkot demonstrated penetration of a Punjab garrison city. The Abu Qasim killing in Rawalakot demonstrated penetration of PoK’s administrative center. Shahid’s kidnapping in the Neelum Valley demonstrated penetration of PoK’s most remote and militarily sensitive corridor. Each new environment opens represents an expansion of the campaign’s operational map, and each expansion forces Pakistan to disperse its protective resources further, creating gaps that the campaign can exploit.

The method-flexibility thesis that Shahid’s case supports also carries implications for how analysts should assess future eliminations. If the campaign is capable of employing radically different methods in different environments, then future cases that deviate from the motorcycle-and-pistol pattern should not automatically be excluded from the campaign’s portfolio. A car accident in Lahore, a fall from a building in Islamabad, a poisoning in Rawalpindi, none of these match the standard signature, but Shahid’s case establishes the precedent that methodological deviation does not preclude campaign membership. The constant across cases is not the method but the target profile: India-designated terrorists whose elimination serves India’s counter-terrorism objectives, killed by unidentified perpetrators who claim no responsibility.

The Sunjuwan Attack and the Question of Targeting Families

The Sunjuwan attack raises a question that the broader analytical community has not fully confronted: does the deliberate targeting of military families represent a qualitative escalation in Pakistan-sponsored terrorism, and does that escalation bear on the type of response it generates?

The physical layout of the Sunjuwan Military Station placed family quarters, with women and children, within the compound alongside operational military infrastructure. The attackers entered the compound and moved through it in a direction that brought them into contact with family quarters. Five women and one child were among the twenty wounded. The attackers’ weapons loadout, including grenades and under-barrel grenade launchers, was indiscriminate by nature, designed to cause maximum casualties in enclosed spaces regardless of whether those spaces contained combatants or their dependents.

Harsh Pant of the Observer Research Foundation has argued that attacks targeting military families represent a specific category of provocation distinct from attacks on military installations alone. When terrorists target soldiers, the calculus is military. When they target soldiers’ families, including children sleeping in quarters at 4 AM, the calculus becomes something that transcends military logic and enters the domain of existential threat perception. India’s response to the Sunjuwan attack was operationally contained: the attackers were killed, the area was secured, intelligence investigations identified the masterminds. But the emotional and institutional memory of an attack on families embeds itself in the security establishment’s institutional culture in ways that create permission structures for responses that would otherwise be considered disproportionate.

Ajai Shukla, the defense journalist who has covered Indian military operations extensively, has written on the question of camp security protocols and the systemic vulnerabilities that the Sunjuwan breach exposed. Military stations in Jammu and Kashmir house thousands of families, and the security perimeter of each station must balance operational security against the practical needs of daily life: children going to school, families visiting markets, relatives coming for visits. Hardening every military station to the point of imperviousness would require either relocating all families outside the conflict zone or converting every military station into a sealed fortress, both of which are logistically impractical and would damage the morale of soldiers deployed far from home. The Sunjuwan attack exploited this structural vulnerability, and the fact that the vulnerability persists despite the attack’s exposure of it means that similar attacks remain possible. The shadow war’s targeting of attack masterminds like Shahid can be understood, in part, as a deterrence mechanism aimed at the planning layer: an implicit warning that those who plan attacks on military families will face consequences that extend beyond the immediate operational environment and into the places they consider safe.

The five-year chain from the Sunjuwan attack in February 2018 to Shahid’s beheading in November 2023 traverses a period during which India’s counter-terrorism posture transformed from reactive to offensive. In February 2018, India’s response to the attack was domestic: kill the attackers, investigate the masterminds, harden the security perimeter. By November 2023, the response to the same category of threat had extended to the physical elimination of the planners on foreign soil, a transformation in strategic doctrine that the Sunjuwan-to-Shahid chain illustrates with unusual clarity.

The transformation was not instantaneous, and its intermediate steps are documented elsewhere in this series. After Sunjuwan, the next major inflection point was the Pulwama attack of February 2019, which killed forty CRPF personnel in a convoy bombing and triggered the Balakot airstrike. Balakot represented an escalation beyond the 2016 surgical strikes: it targeted a JeM training facility deep inside Pakistani territory (in Khyber Pakhtunkhwa, not in PoK), crossing a geographic threshold that the surgical strikes had deliberately avoided. Between Balakot and the shadow war, a doctrinal bridge was being constructed. The strikes demonstrated the willingness to use force inside Pakistan. The shadow war demonstrated the willingness to sustain covert operations inside Pakistan indefinitely. Sunjuwan sits at the beginning of this bridge: an attack that contributed to the institutional fury and strategic frustration that eventually produced the campaign that reached Shahid.

The family-targeting dimension of Sunjuwan also connects to the broader question of red lines in the India-Pakistan conflict. Analysts have long debated whether there exists an implicit hierarchy of provocation, a spectrum of attacks ranked by how close they come to triggering a major Indian military response. At the lower end of this spectrum are attacks on police posts and border checkpoints, routine events that produce casualties but do not generate strategic consequences. At the upper end are attacks on civilians in India’s heartland, such as the 2008 Mumbai attacks, which produced international pressure and came close to triggering a conventional military response. Attacks on military installations occupy an intermediate position: they are more provocative than border incidents but less provocative than civilian attacks in metropolitan areas. Sunjuwan complicated this hierarchy by blurring the line between military and civilian targeting. An attack on a military station that also kills soldiers’ families introduces a civilian dimension to a military target, and that blurred categorization pushes the attack higher on the provocation spectrum than its purely military characteristics would suggest.

India’s strategic community has never formally articulated where on this spectrum the threshold for decisive retaliation lies, and the ambiguity is itself a strategic choice. Specifying the threshold would invite calibrated attacks designed to fall just below it. Maintaining ambiguity preserves the flexibility to respond or not respond based on the specific circumstances of each incident. The shadow war can be understood as a response that exists below the threshold of formal military action but above the threshold of inaction: a sustained, covert program that imposes costs without triggering the escalation dynamics that conventional military responses carry between two nuclear-armed states.

The MO Deviation and What It Means for the Campaign

The significance of Shahid’s case for the broader analytical understanding of the targeted elimination campaign lies not in the beheading itself but in what the beheading reveals about the campaign’s operational architecture. If the campaign were a rigid, centrally controlled operation with a single team using a standardized method, a deviation of this magnitude would be difficult to explain. The motorcycle-and-pistol signature would be the only method used, because the central command would not authorize alternatives. The fact that a radically different method was used in a radically different environment suggests one of two things: either the campaign’s operational architecture is flexible enough to incorporate multiple methods and multiple teams, or the campaign is not a single operation at all but a coordinated set of operations conducted by different entities under a common targeting directive.

Both interpretations have implications for Pakistan’s ability to protect its militant assets. If the campaign can deploy different teams with different methods in different environments, then no single defensive posture can prevent future operations. Increasing security around urban mosques (where Shahid Latif was killed in Sialkot) does not protect against kidnappings in mountain valleys. Deploying motorcycle checkpoints in Karachi (where Zahoor Mistry was shot by motorcycle-borne assailants) does not prevent infiltrations along the LoC. The campaign’s methodological diversity, if Shahid’s case is indeed part of the campaign, means that Pakistan’s defensive resources must be spread across every environment where targeted terrorists reside, from megacities to mountain valleys, from Punjab’s plains to PoK’s forests.

The beheading also carries a specific psychological weight that a shooting does not. Being shot is fast. Being kidnapped, held, tortured, and beheaded is not. The message delivered by the two methods is qualitatively different. A shooting says: “We can reach you.” A kidnapping and beheading says: “We can take you, hold you while your protectors search for you, do what we want to you, and leave you where we want to leave you.” The second message is more frightening because it implies a greater degree of control over the operational environment. The ISI could not find Shahid. The Pakistan Army could not rescue him. The men who held him operated with impunity in territory that Pakistan considers its own. For other LeT commanders in the PoK corridor, the message is not subtle.

The discovery of a second, unidentified body alongside Shahid’s near the LoC adds another dimension to the analysis that remains unresolved. Who was the second individual? Were they an associate of Shahid, kidnapped at the same time or separately? Were they a member of the team that carried out the operation, killed to prevent identification? Were they an unrelated individual whose body happened to be in the same location? The presence of the second body suggests that the operation was larger than a single-target kidnapping, but the lack of identification prevents further analysis. If the second individual was another militant, the operation may have targeted multiple members of LeT’s PoK infrastructure simultaneously.

The November 2023 Cluster in Context

Shahid’s killing cannot be fully understood in isolation from the operational tempo that surrounded it. The two weeks from November 1 to November 14, 2023 represent the densest confirmed cluster of targeted eliminations in the campaign’s documented history. Three confirmed killings in fourteen days, across three different regions of Pakistan, using at least two different methods, targeting operatives from at least two different terror organizations. The cluster preceded a period of continued eliminations through 2024 and into 2025, but its compressed intensity has not been replicated in any subsequent two-week window.

The geographic dispersion of the November cluster, PoK for Shahid, Khyber Pakhtunkhwa’s Bajaur district for Akram Khan, and Karachi for Raheem Ullah Tariq, rules out the possibility that a single team moved sequentially from one target to the next. Three eliminations in three widely separated regions within fourteen days requires either three independent teams operating on parallel timelines or a command structure with the logistical capacity to activate multiple operations simultaneously. Either interpretation implies an operational architecture far more sophisticated than a lone intelligence cell with a motorcycle and a pistol.

The organizational targeting within the cluster also reveals strategic intent. Shahid (LeT, PoK sector), Akram Khan (LeT, KPK sector), and Tariq (JeM, Karachi) span two organizations and three geographic theaters. The cluster was not focused on dismantling a single node within a single organization; it struck across the organizational and geographic spectrum simultaneously. This breadth suggests that the targeting directive operates at a level above individual organizations, selecting targets based on their position on India’s threat matrix rather than their affiliation with any specific group.

The cluster’s timing is also significant when placed within the broader campaign calendar. October 2023 had already seen the killings of Shahid Latif in Sialkot and Mufti Qaiser Farooq in Karachi. September 2023 had seen the killings of Abu Qasim in Rawalakot and Ziaur Rahman in Karachi. The October-November 2023 window thus produced at least seven confirmed eliminations in approximately sixty days, an operational tempo that had no precedent in the campaign’s history. This acceleration suggests that late 2023 represented either a planned surge, in which multiple operations that had been prepared over months were deliberately executed in a compressed timeline to maximize disruption across multiple networks simultaneously, or a convergence of operational readiness across multiple independent teams that happened to reach their respective targets within the same period.

The distinction between coordinated surge and convergent readiness matters for understanding the campaign’s command architecture. A coordinated surge implies centralized command: a single authority directing multiple teams to execute within the same window, perhaps timed to a specific intelligence assessment that the window of opportunity was closing (targets were about to relocate, security was about to increase, political conditions were about to shift). Convergent readiness implies decentralized execution within a centralized targeting framework: multiple teams operating independently toward their individual targets, with each team executing when its own preparations were complete rather than according to a synchronized timeline. Both models are consistent with the available evidence, and distinguishing between them would require operational details that are unlikely to enter the public domain.

Shahid’s case within the cluster is analytically distinctive because of its methodological outlier status. The other cluster members, Akram Khan and Tariq, were killed by the standard motorcycle-and-pistol method in their respective cities. Shahid alone was subjected to kidnapping and beheading. If the cluster was coordinated, this methodological variation was planned: the central command authorized different methods for different environments. If the cluster was convergent, the variation may simply reflect the different operational cultures of the teams assigned to different geographic sectors, with the PoK team employing methods suited to its terrain and capabilities while the KPK and Karachi teams used the standard approach.

The Terrain of Pakistan-Occupied Kashmir

Understanding why Shahid was killed in the manner he was requires understanding the terrain in which he lived and operated. Pakistan-Occupied Kashmir, and the Neelum Valley specifically, is not Pakistan proper. It occupies a distinct geographic, political, and military space within Pakistan’s administrative structure, one that creates both opportunities and constraints for any entity operating within it.

The Neelum Valley is a 200-kilometer stretch of the Neelum River (known as the Kishanganga in India), running from its confluence with the Jhelum River near Muzaffarabad northeast toward the LoC. The valley floor sits at approximately 1,500 meters elevation, but the surrounding mountains rise to over 4,000 meters, creating a dramatic, enclosed landscape of steep forested slopes, narrow roads carved into mountainsides, and river crossings that can be impassable during the spring snowmelt. The road network is limited; a single major road runs the length of the valley, with secondary tracks branching to smaller settlements. Vehicle movement is visible and trackable. Pedestrian movement through the forests offers concealment but is slow and physically demanding.

The Pakistan Army maintains a substantial presence in the Neelum Valley, both because of its proximity to the LoC and because of its historical role as an infiltration corridor. Forward posts, supply depots, and communication infrastructure are distributed along the valley. The army’s presence creates a layered security environment that is, in theory, difficult for unauthorized armed groups to penetrate. In practice, however, the valley’s length, the forested terrain, and the mountainous topography create gaps in surveillance coverage that a small, well-prepared team could exploit.

The population of the Neelum Valley is predominantly ethnic Kashmiri, with cultural and familial ties that extend across the LoC into Indian-administered Kashmir. These cross-border ties have historically been exploited by both intelligence agencies and militant organizations: LeT uses local guides with knowledge of the mountain passes; Indian intelligence, if the broader campaign’s allegations are credited, presumably relies on its own network of contacts with knowledge of the same terrain. The valley’s population is also subject to the political dynamics of Pakistan-Occupied Kashmir, where resentment against Pakistani administrative control, inadequate infrastructure investment, and the presence of militant groups whose activities bring unwanted attention from across the LoC all create potential fault lines that can be exploited by external actors.

For an intelligence operation targeting Shahid, the Neelum Valley presented a paradox. On one hand, the limited infrastructure, small population, and Pakistan Army presence made covert operations inherently risky. On the other hand, the same factors that made LeT feel secure in the valley, its remoteness, its perceived distance from urban centers where most eliminations have occurred, may have produced complacency. Shahid may not have maintained the same level of personal security in his home territory that he would have in Karachi or Lahore, where the campaign’s presence was well established by late 2023. The valley that was supposed to be his safe haven became the site of his most vulnerable exposure.

The geographic dimension of Shahid’s case connects to a broader pattern within the campaign’s evolution that Walter Ladwig III of King’s College London has analyzed in his work on India’s evolving coercive options against Pakistan. Ladwig has argued that India’s strategic posture has progressively expanded the geographic scope of its counter-terrorism operations, from defensive actions within Indian territory (killing infiltrating terrorists at the LoC) through cross-border operations (the 2016 surgical strikes targeted launch pads on the Pakistani side of the LoC) to deep-penetration operations (targeted killings in Pakistani cities hundreds of kilometers from the border). The Shahid case fits within this geographic expansion but adds a new wrinkle: it targets not a deep-penetration urban environment but the border-adjacent zone itself, the PoK corridor that has been the launchpad for decades of cross-border terrorism. Striking within this zone has a specific strategic significance that differs from striking in Karachi or Lahore. It says: “We can reach you not only in your cities but in the very corridor you use to attack us.”

Toby Dalton of Carnegie has explored the escalation dynamics of covert action between nuclear states, and the Shahid case provides a specific data point for his analysis. Dalton’s framework considers how covert operations between nuclear-armed adversaries manage the tension between operational effectiveness and escalation risk. Operations in Pakistani cities carry one level of escalation risk: they are deniable, geographically distant from military concentrations, and can be framed as criminal activity. Operations in PoK, adjacent to the LoC where two nuclear-armed armies face each other across fortified positions, carry a qualitatively higher risk. A covert operation gone wrong in the Neelum Valley could produce a confrontation between Indian and Pakistani military units at the LoC, with escalation pathways that do not exist in an urban setting. The decision to conduct the Shahid operation in this environment implies either a confidence that the escalation risk was manageable or a judgment that the operational value of removing an infiltration commander from the LoC corridor justified the elevated risk.

Five Years, Seven Lives, and the Logic of Delayed Consequence

The temporal dimension of Shahid’s case deserves dedicated analysis because it illuminates a feature of the targeted elimination campaign that the rapid-turnaround cases do not. When Abu Qasim was killed in September 2023 and the Dhangri attack he allegedly masterminded occurred in January 2023, the gap was eight months. When Shahid Latif was killed in October 2023 and the Pathankot attack he planned occurred in January 2016, the gap was seven years. Shahid’s case falls between these: five years between the Sunjuwan attack and his elimination. The variable time gap between an attack and its consequence raises the question of what determines when a mastermind becomes a target.

Three factors plausibly explain the timing. First, intelligence accumulation: identifying Shahid as a Sunjuwan mastermind may have occurred relatively quickly, but locating him in the Neelum Valley and developing the operational plan to reach him took years. The campaign could not target someone it could not find, and finding a LeT commander in a remote mountain valley under ISI protection is a categorically different challenge than finding an operative walking in a Karachi market. Second, campaign prioritization: the elimination campaign appears to have followed an escalating priority logic, beginning with lower-tier operatives (Saleem Rehmani in January 2022, Zahoor Mistry in March 2022) and gradually moving to higher-value targets as the operational capability was proven and expanded. Shahid, as a regional commander and attack mastermind, occupied a higher priority tier that was not reached until the campaign’s acceleration phase in late 2023. Third, policy decision: the political authorization for the type of operation required to reach Shahid in the Neelum Valley, an operation far more complex and risky than an urban shooting, may not have been granted until the campaign’s success in urban environments built confidence in the decision-making chain.

The five-year gap also speaks to the institutional memory of the campaign’s architects. Armies forget. Bureaucracies rotate personnel. Political leaderships change. But someone, somewhere, maintained a file on Khwaja Shahid for five years, updated the intelligence on his location as it became available, assessed the operational feasibility of reaching him, and ultimately authorized and executed the operation. That institutional persistence is itself a capability, one that transforms the campaign from a series of opportunistic strikes into a methodical program with a long memory and a longer reach.

The seven lives lost at Sunjuwan, five soldiers, one civilian, and one additional military family member whose existence shaped the attack’s emotional resonance, are the moral foundation on which the delayed consequence rests. Whether one views the elimination as justice, deterrence, or something less noble, the human dimension of the five-year chain is inescapable: a father killed while visiting his son at a military station; soldiers from the Jammu and Kashmir Light Infantry, the local regiment defending their own land, cut down in their barracks; women and children wounded by grenades in the predawn darkness. Five years later, the man who allegedly helped plan that carnage was found beheaded near the border he had used as a highway for terror. The chain from cause to consequence is not neat, not clean, and not entirely explicable within any single analytical framework. It is, however, consistent with the House Thesis that animates this series: every attack generates a response; every response exposes a target; every target, when eliminated, reveals the network that produced it and the state that protected it.

The deterrence function of the five-year chain deserves separate consideration from its retributive function. Deterrence operates on the calculation of future actors, not past ones. Shahid cannot be deterred; he is dead. But every active LeT and JeM commander who is planning or facilitating attacks against India now exists within a threat environment where the Shahid precedent applies: it does not matter where you hide. It does not matter whether your location is urban or rural, accessible or remote. It does not matter how much time passes between your attack and the day the consequences arrive. The chain will reach you. The question for these commanders is whether they believe the precedent will be enforced consistently, and the operational tempo of 2023, with its concentrated cluster of eliminations across multiple regions and organizations, provides an emphatic answer.

The chain also challenges the assumption, common in international relations theory, that covert operations lose their deterrent value if they are deniable. Classical deterrence theory holds that a threat must be credible, communicated, and attributable to deter. The shadow war is none of these in the formal sense: India has not claimed responsibility, has not communicated a deterrent threat, and has not attributed any specific killing to its intelligence agencies. Yet the pattern itself communicates. The consistency of targeting (India-designated terrorists, exclusively), the absence of any plausible alternative perpetrator in most cases, and the operational sophistication of the killings collectively constitute an implicit message that is understood by the relevant audience even without formal attribution. Shahid’s beheading, precisely because of its brutality, communicates more forcefully than a deniable shooting: the consequences of planning attacks against India are not merely lethal but potentially horrific, and no safe haven is safe enough.

Frequently Asked Questions

Q: Who was Khwaja Shahid aka Mian Mujahid?

Khwaja Shahid, who operated under the alias Mian Mujahid, was a Lashkar-e-Taiba commander from the Neelum Valley in Pakistan-Occupied Kashmir. Indian security forces identified him as one of the masterminds behind the February 2018 terrorist attack on the Sunjuwan Military Station in Jammu, which killed seven people, including five Indian Army soldiers and one civilian, while wounding twenty others including women and children. Shahid functioned as a regional commander responsible for facilitating cross-border infiltration from PoK into Indian-administered Jammu and Kashmir. His role in the Sunjuwan attack was reportedly in the planning and logistics phase, arranging the infiltration route and coordination that enabled the three attackers to reach the military station.

Q: How was Khwaja Shahid killed?

Shahid was kidnapped by unidentified assailants from his area of residence in the Neelum Valley of Pakistan-Occupied Kashmir in early November 2023. He was held captive for approximately three days, during which the Pakistani ISI and Army launched unsuccessful search operations to locate him. His beheaded body, bearing signs of severe torture, was found near the Line of Control in the Athmuqam sector of PoK, alongside the body of another unidentified individual. No organization claimed responsibility for the kidnapping or killing.

Q: What happened in the Sunjuwan Army camp attack?

On February 10, 2018, at approximately 4:10 AM, three heavily armed terrorists wearing Indian Army combat fatigues infiltrated the Sunjuwan Military Station in Jammu, which served as the headquarters of the 36th Brigade. The attackers carried AK-56 rifles, under-barrel grenade launchers, and substantial ammunition. They engaged soldiers and penetrated toward the family quarters within the compound. The resulting firefight lasted approximately twenty-four hours before all three attackers were eliminated. Seven people were killed: five Indian Army soldiers from the 1st Battalion of the Jammu and Kashmir Light Infantry, one civilian (the father of one of the soldiers), and the attack coincided with the death anniversary of Afzal Guru.

Q: Was the Sunjuwan attack carried out by LeT or JeM?

The physical attackers were identified as Pakistani nationals linked to Jaish-e-Mohammed, and the Indian Army identified a JeM commander named Mufti Waqas, killed in Awantipora on March 5, 2018, as the attack’s operational mastermind. However, Khwaja Shahid, an LeT commander, was separately identified as one of the masterminds responsible for planning and facilitating the attack. This cross-organizational overlap reflects how Pakistan-based terror groups cooperate under ISI coordination, with different organizations providing different capabilities (LeT providing infiltration logistics, JeM providing the committed attackers) for joint operations.

Q: Why was Shahid beheaded instead of shot like other targeted terrorists?

The beheading represents the most significant methodological deviation from the standard modus operandi observed in the broader campaign of targeted killings in Pakistan. The standard method involves motorcycle-borne gunmen using firearms at close range in urban settings. Shahid’s location in the remote Neelum Valley of PoK made the standard method impractical: the terrain lacks the urban infrastructure (congested streets, anonymous crowds, motorcycle-friendly roads) that enables the standard approach. The beheading may represent an adaptation to terrain constraints, the use of local proxies whose methods differ from the urban teams, or a deliberate choice to send a specific message.

Q: Was the ISI searching for Shahid after his kidnapping?

Multiple Indian and Pakistani media reports indicated that Shahid’s kidnapping sent shockwaves through the ISI, which launched search operations to locate him. The ISI’s urgent response confirmed that it considered Shahid a protected asset. Despite these efforts, the ISI was unable to locate Shahid during his approximately three-day captivity, and he was found dead. The failure to recover Shahid represented a significant intelligence failure for Pakistan and demonstrated the operational capability of whoever conducted the kidnapping.

Q: What was the November 2023 killing cluster?

In the first two weeks of November 2023, three India-wanted terrorists were eliminated in rapid succession across Pakistan: Khwaja Shahid was found beheaded in PoK around November 5, Akram Khan (LeT) was shot dead in Khyber Pakhtunkhwa’s Bajaur district on November 9, and Raheem Ullah Tariq (JeM) was shot dead in Karachi on November 13. The geographic dispersion of these killings across three regions, using at least two different methods, suggests either multiple independent teams or a command structure capable of activating several operations simultaneously.

Q: Why did it take five years for Shahid to face consequences?

The five-year gap between the February 2018 Sunjuwan attack and Shahid’s November 2023 killing reflects several factors: the time required to accumulate actionable intelligence on his precise location in the remote Neelum Valley, the campaign’s apparent escalation from lower-tier to higher-value targets over time, and the complexity of planning an operation in PoK’s mountainous terrain compared to urban environments. The delay also reflects the institutional persistence required to maintain a targeting file across years while awaiting the right operational conditions.

Q: Were military families deliberately targeted at Sunjuwan?

The physical layout of the Sunjuwan Military Station placed family quarters within the compound. The attackers moved through the compound in a direction that brought them into contact with these quarters, and five women and one child were among the twenty wounded. While the attackers also engaged soldiers, the presence of casualties among women and children in the family quarters indicates that the attackers either deliberately targeted family areas or fired indiscriminately in their direction. The weapons used, including grenades and grenade launchers, are inherently indiscriminate in enclosed spaces and would cause casualties regardless of the intended target.

Q: What does Shahid’s killing reveal about the campaign’s reach?

Shahid’s killing demonstrates that the targeted elimination campaign can operate in environments far removed from the urban settings where most documented killings have occurred. The Neelum Valley’s mountainous terrain, limited road network, sparse population, and Pakistan Army presence create an operational environment categorically different from Karachi or Lahore. The ability to conduct a multi-day kidnapping operation in this environment, despite an active ISI search, suggests capabilities including local intelligence networks, secure holding locations, and extraction routes that extend the campaign’s reach into territory previously considered beyond its scope.

Q: Who was the second body found alongside Shahid?

The identity of the second individual found alongside Shahid’s body near the LoC has not been publicly established. Reports described the second body as that of an “unidentified terrorist.” Whether this individual was another LeT operative kidnapped alongside or separately from Shahid, a member of the team that carried out the operation, or an unrelated individual remains unclear. The presence of a second body suggests the operation may have targeted more than one individual, but the lack of identification prevents definitive analysis.

Q: How did the Sunjuwan attack connect to other Pakistan-sponsored attacks on India?

The Sunjuwan attack fits within an escalatory sequence of Pakistan-sponsored terrorist operations targeting Indian military installations in Jammu and Kashmir. It followed the January 2016 Pathankot airbase attack, which targeted India’s military aviation infrastructure, and the September 2016 Uri Army camp attack, which killed nineteen soldiers and triggered India’s first surgical strikes across the LoC. Each attack raised the threshold of Indian tolerance and generated intelligence leads that fed into subsequent counter-terrorism operations, including the campaign of targeted eliminations that eventually reached Shahid.

Q: What organization does Shahid’s killing most resemble operationally?

The kidnapping-and-beheading methodology is most commonly associated in the Pakistan-Afghanistan theater with Tehrik-i-Taliban Pakistan and tribal justice mechanisms. However, Shahid was not a TTP target or a tribal figure; he was an LeT commander wanted by India for a specific terror attack. The target-selection logic is inconsistent with TTP operations, which focus on Pakistani security forces and state officials. The method may reflect the use of local proxies whose operational culture differs from the urban teams responsible for the standard motorcycle shootings, or it may represent an adaptation to terrain that required a fundamentally different approach.

Q: What was Shahid’s role within LeT’s command structure?

Shahid occupied a regional commander position within LeT’s PoK apparatus, responsible for a geographic sector along the Neelum Valley and its associated infiltration corridors into Indian-administered Kashmir. This role placed him above foot soldiers and local facilitators but below the organization’s strategic leadership in Punjab. He was responsible for translating strategic directives from LeT’s central command into specific infiltration operations, including the coordination of routes, guides, safe houses, and timing for cross-border movements of armed personnel.

Q: How does Shahid’s case compare to other mosque killings in the campaign?

Shahid’s case is the inverse of the mosque killings documented elsewhere in the campaign. Cases like Abu Qasim (shot at point-blank range inside a mosque in Rawalakot) and Shahid Latif (shot inside a mosque in Sialkot) follow the standard pattern of identifying a target’s predictable routine and intercepting them at that point. Shahid’s case involved kidnapping rather than interception, extended captivity rather than immediate execution, and beheading rather than shooting. The comparison illuminates the methodological range of the campaign: while most operations follow the mosque or predictable-routine pattern, the campaign can deploy fundamentally different approaches when the environment demands it.

Q: Did Pakistan officially accuse India of killing Shahid?

Pakistan did not formally and publicly attribute Shahid’s killing to Indian intelligence in the manner that it later attributed the killings of Muhammad Riaz and Shahid Latif. The formal diplomatic accusations presented by Pakistani Foreign Secretary Mumtaz Zahra Baloch in January 2024 focused on cases where Pakistani investigators had gathered specific evidence. Shahid’s case, with its radically different methodology, may have presented attribution challenges, or his profile as an India-designated terror mastermind may have made his case politically difficult to highlight on the international stage.

Q: What was the significance of Shahid’s body being found near the LoC?

The proximity of Shahid’s body to the Line of Control carries potential analytical significance. The LoC is the de facto border between Indian-administered and Pakistan-administered Kashmir, and its proximity to the dump site may suggest that the operators crossed the border before or after the operation, potentially using the same infiltration corridors that LeT had historically exploited in the opposite direction. Alternatively, the LoC’s proximity may have been chosen for its symbolic resonance: leaving the body of an infiltration facilitator near the very border he helped terrorists cross.

Q: Could Shahid’s killing have been an internal PoK faction feud?

While internal factional violence exists in Pakistan-Occupied Kashmir, no known PoK faction has a history of targeting LeT commanders. The target profile is inconsistent with local criminal or factional violence: Shahid was selected not for local reasons but because of his role in a specific attack against India. The no-claim-of-responsibility pattern further distinguishes the killing from factional violence, where perpetrators typically want their grievance known. The available evidence more strongly supports a connection to the broader targeted elimination campaign than to an internal PoK dispute, even though the method of killing is atypical for that campaign.

Q: How many people has the targeted elimination campaign killed?

The Guardian’s April 2024 investigation referenced “almost 20 killings since 2020” attributed to unknown gunmen in Pakistan targeting India-wanted individuals. Indian media compilations have listed over twenty confirmed cases. The exact number is contested because attribution is not always clear: some killings in Pakistan may be unrelated to the campaign and instead reflect domestic violence, criminal activity, or TTP operations. The campaign’s signature elements, including targeting of India-designated terrorists, motorcycle-borne assailants, no claim of responsibility, and the absence of any alternative credible motive, help analysts distinguish campaign-related killings from background violence.

Q: What impact did the Sunjuwan attack have on Indian counter-terrorism policy?

The Sunjuwan attack contributed to the progressive hardening of India’s counter-terrorism posture that culminated in the shadow war doctrine. Each major attack on Indian soil or Indian military installations, from the 2001 Parliament attack through 26/11, Uri, Pathankot, Sunjuwan, Pulwama, and Pahalgam, pushed India further along the spectrum from defensive intelligence gathering toward offensive counter-terrorism operations. Sunjuwan’s targeting of military families added an emotional dimension that reinforced institutional support for more aggressive responses. The attack-to-elimination chain that connects Sunjuwan to Shahid’s beheading five years later is one thread in a broader transformation of Indian strategic doctrine from restraint to what some analysts describe as proactive deterrence.