On a September evening in Rawalakot, Pakistan-Occupied Kashmir, Riyaz Ahmad knelt inside al-Qudus mosque for prayers. He had performed this ritual hundreds of times, in this same building, surrounded by fellow congregants who knew him as Abu Qasim, a senior Lashkar-e-Taiba operative responsible for coordinating militant infiltration across the Line of Control into the Indian districts of Poonch and Rajouri. Nine months earlier, gunmen he allegedly directed had entered three houses in a Hindu-majority village called Dhangri and opened fire on families as they settled in for the first evening of the new year, killing four people outright and setting an IED that would kill two children the following morning. A seventh victim died of injuries days later. The chain from Dhangri to al-Qudus mosque is the attack-to-elimination sequence in its most distilled form: a terror attack generated a target, intelligence agencies identified and located the target, and unknown gunmen executed the target inside a place of worship in territory Pakistan considers its own.

Abu Qasim’s killing is the single most operationally precise elimination documented in India’s shadow war against terror. The attackers knew which mosque he attended, which prayer time brought him reliably to that location, and where he positioned himself within the congregation. They entered during prayers and shot him in the head at point-blank range. The precision required to execute this operation inside Pakistan-Occupied Kashmir, where the Pakistan Army maintains a dense security presence and outsiders are immediately conspicuous, reveals a depth of surveillance capability that goes beyond anything demonstrated in the Karachi or Lahore eliminations. Karachi offers urban anonymity; Lahore offers crowd cover. Rawalakot, a town of perhaps 50,000 people nestled in the hills less than thirty kilometers from the Line of Control, offers neither. Operating here required either deeply embedded local assets or an infiltration and exfiltration capability sophisticated enough to function in territory controlled by the Pakistan Army’s 23rd Division.

The Dhangri-to-Rawalakot chain also carries the weight of a moral argument that the campaign as a whole embodies. Seven people died in Dhangri on New Year’s Day 2023, including a four-year-old boy named Vihan Sharma and a sixteen-year-old girl named Samiksha Sharma, killed by an IED blast the morning after the initial gunfire. Nine months later, the man Indian intelligence identified as the architect of that attack was dead on the floor of a mosque. The speed of this particular chain, among the fastest documented in the complete timeline, suggests that the Dhangri massacre produced an immediate and specific operational response. Whether that response constitutes justice, deterrence, or extrajudicial killing depends on where one stands on the legal and ethical questions that surround this entire campaign. What it demonstrates beyond debate is operational capability of an extraordinary order.

The Killing

Riyaz Ahmad, known within Lashkar-e-Taiba by the operational alias Abu Qasim, was shot dead inside al-Qudus mosque in the Rawalakot area of Pakistan-Occupied Kashmir in September 2023. Reports from PoK sourced through Pakistani media confirmed that unidentified gunmen entered the mosque during prayer time and shot him in the head at close range. The attackers departed the scene before anyone in the congregation could react or identify them.

Rawalakot sits roughly twenty-five kilometers from the Line of Control in the Poonch sector, a town that has served for decades as a staging ground for militant infiltration into Indian Kashmir. The town is the administrative headquarters of the Poonch district in PoK (not to be confused with the Poonch district on the Indian side of the Line of Control), and its geographic position makes it one of the most sensitive security zones in the region. The Pakistan Army maintains a substantial garrison presence. Civilian movement is monitored. The town has a university, a bazaar, residential neighborhoods, and the ordinary infrastructure of a small administrative center, all of it overlaid with the military and militant infrastructure that has characterized PoK towns since the first Kashmir war in 1947.

The choice of a mosque as the killing ground was not random. Mosques offer three operational advantages that no other location can match. First, attendance is predictable: a practicing Muslim who attends a particular mosque will appear at that mosque five times daily, at times determined by the position of the sun, which means the schedule is publicly known and cannot be varied. Second, the target’s posture during prayer is physically vulnerable, facing the qibla wall with head bowed in prostration or kneeling in the rows. Third, the social dynamics of a congregation create cover: the other worshippers are focused on prayer, their attention directed away from the entrance, and an additional person entering the mosque does not trigger alarm because mosques are, by their nature, open to all.

The Abu Qasim killing was the second documented elimination in Pakistan-Occupied Kashmir, following the kidnapping and beheading of Khwaja Shahid near the Line of Control. Shahid’s killing, attributed to the same broader campaign, used a dramatically different method: he was abducted, and his headless body was found days later. The contrast between the Shahid beheading and the Abu Qasim mosque shooting raises analytical questions about whether PoK operations are conducted by the same teams using different methods for different operational circumstances, or by entirely different operational units. The beheading suggests the involvement of a team that could hold a captive for an extended period, which requires infrastructure. The mosque shooting suggests the involvement of a team that could enter and exit a populated area rapidly, which requires local knowledge and mobility. Both required intimate familiarity with the target’s movements in a security-saturated environment.

Pakistani media reports from PoK provided limited detail on the killing itself. No suspects were named. No organization claimed responsibility. PoK police registered a case but produced no publicly reported progress in identifying the assailants. The anonymity of the operation fits the pattern documented across dozens of similar killings in Karachi, Lahore, Rawalpindi, and other Pakistani cities: unknown gunmen arrive, execute the target with precision, and vanish. The only distinction in the Abu Qasim case is that it occurred in PoK, a territory where the Pakistan Army exercises direct control and where the operational challenge of entering, killing, and leaving undetected is substantially greater than in any Pakistani urban center.

The timing of the killing, roughly nine months after the Dhangri village massacre, compresses the attack-to-elimination chain into a span that suggests rapid target identification and location. By comparison, Zahoor Mistry, the IC-814 hijacker, lived under a false identity in Karachi for years before being located and killed. Shahid Latif operated openly in Sialkot for seven years after the Pathankot attack before masked gunmen shot him inside a mosque. The Dhangri-to-Rawalakot chain of nine months is the fastest documented major-attack-to-elimination sequence in the series, suggesting either that Abu Qasim was already under surveillance when the Dhangri attack occurred or that the attack generated an intelligence priority that produced rapid results.

Abu Qasim was the fourth senior Lashkar-e-Taiba commander killed by unknown gunmen in 2023. His death came in a year that saw the campaign accelerate dramatically, with the operational tempo increasing from isolated incidents to clusters. The sheer number of eliminations in 2023 strained Pakistan’s ability to deny a pattern. One killing is an incident. Two is a coincidence. Four senior commanders from the same organization, killed in different cities by similar methods within the same calendar year, is a campaign.

The geographic setting of the killing demands closer examination because it defines everything about the operation’s difficulty and significance. Rawalakot lies in a valley surrounded by pine-forested hills at an elevation of approximately 1,500 meters above sea level. The Poonch River flows through the area. The road network is limited, with the main route connecting Rawalakot to Islamabad via Rawalpindi running roughly 150 kilometers through mountainous terrain. Approaching or departing Rawalakot by road means passing through a series of checkpoints maintained by the Pakistan Army and by the local police force that operates under PoK’s administrative structure. These checkpoints are not merely procedural: the Pakistan Army uses them to monitor the movement of people and goods in a territory that sits on the front line of the Kashmir dispute. Any vehicle carrying unfamiliar passengers would attract scrutiny. Any individual whose identity documents did not reflect residency in the Poonch district of PoK would face questions.

The town itself functions as both a civilian administrative center and a military staging zone. The University of Poonch is located here. Markets serve the local population. Residential neighborhoods house families with no connection to militancy. This civilian overlay coexists with an infrastructure of safe houses, transit points, and communication hubs that have facilitated militant movements for decades. The Pakistan Army’s 23rd Division, responsible for the PoK sector, maintains a garrison presence that includes not just troops but an intelligence apparatus tasked with monitoring threats to Pakistan’s control over the territory. In theory, this security architecture should make Rawalakot one of the most difficult locations in the world for an unauthorized armed operation. In practice, the Abu Qasim killing demonstrated that the architecture failed, either through penetration, complicity, or a gap that the operational team identified and exploited.

The weapon used in the killing was a firearm discharged at point-blank range, consistent with the close-quarters method employed in other mosque killings across the series. The physical dynamics of such a killing are worth understanding because they constrain the operational planning. A point-blank headshot inside a mosque during prayer requires the shooter to be within arm’s length of the target. The shooter must have entered the mosque, possibly removing shoes at the entrance as custom requires, and moved to a position directly adjacent to or behind the target. In a small congregation where regulars recognize each other, an unfamiliar face near a senior LeT operative might have triggered alarm. The operation’s success implies that either the shooter was someone Ahmad would not have perceived as a threat, potentially a local asset recruited specifically for this purpose, or that the shooter entered during a moment when the congregation’s attention was fully absorbed in prayer and proximity to others was normal rather than suspicious.

The escape from the mosque and from Rawalakot represents perhaps the most demanding phase of the operation. A gunshot inside a mosque would have been heard instantly by every person in the building. Screaming, panic, and the congregation’s attempt to identify and apprehend the shooter would have begun within seconds. The shooter needed to reach an exit, move through whatever crowd had gathered outside, reach transportation, and depart the immediate area before security forces could establish a cordon. In a town where the Pakistan Army maintains a garrison, the window between the shot and the first military response was measured in minutes, not hours. The successful extraction suggests pre-positioned transportation, a predetermined route that avoided the main checkpoints, and possibly a safe house within the area where the team could shelter until the initial search intensity diminished.

Who Was Abu Qasim

Riyaz Ahmad was born in the Jammu region of the Indian state of Jammu and Kashmir. The precise date and circumstances of his birth are not documented in open-source reporting, but the biographical outline that Indian security officials and Pakistani media reports have assembled places his early years in the foothills of the Pir Panjal range, an area that has produced militants for multiple organizations since the eruption of the Kashmir insurgency in 1989. Rajouri and Poonch, the twin border districts that would later become his primary operational theater, sit in this same geographic corridor, connected to PoK by mountain passes that have been used for infiltration since before the first ceasefire line was drawn.

Ahmad crossed into Pakistan-Occupied Kashmir in 1999, a year that looms large in the history of India-Pakistan terrorism. It was the year of the Kargil conflict, when Pakistani soldiers and militants infiltrated across the Line of Control and occupied mountain peaks in the Kargil sector of Ladakh, triggering a two-month war that ended with Pakistan’s withdrawal. It was also the year of the IC-814 hijacking, when Jaish-e-Mohammed-linked terrorists seized an Indian Airlines plane and forced India to release Masood Azhar, Ahmed Omar Saeed Sheikh, and Mushtaq Ahmed Zargar in exchange for the hostages. The year 1999 marked a turning point in the Kashmir conflict: the infiltration pipelines were running at peak capacity, multiple organizations were recruiting from both sides of the Line of Control, and the Pakistan Army’s support infrastructure for militant movements into Indian Kashmir was fully operational.

After crossing the LoC, Ahmad established himself within Lashkar-e-Taiba’s operational structure in PoK. His trajectory followed a path common among Kashmiri militants of that era: initial contact with a recruiter, facilitation across the border, training at one of LeT’s camps, and assignment to an operational role. What distinguished Ahmad from many peers was the speed and completeness of his integration into LeT’s command structure. Rather than remaining a foot soldier or a field operative assigned to specific missions, he rose to a position of regional authority. Indian security officials described him as instrumental in reviving terrorism in the Poonch and Rajouri districts, a characterization that places him not merely as a participant in terror operations but as the coordinator who directed them.

The training infrastructure that Ahmad passed through after crossing the border is well documented through multiple sources, including the testimony of captured LeT operatives, the investigations that followed the 26/11 Mumbai attacks, and the research of analysts who have studied the organization’s recruitment pipeline. LeT maintained training camps in PoK and in the Muridke complex, offering a curriculum that ranged from basic weapons handling and physical fitness to advanced guerrilla warfare tactics, IED construction, and communications security. Ahmad’s eventual rise to a command position suggests that he excelled in this training and demonstrated the organizational skills that command requires: the ability to manage logistics, coordinate multiple moving parts, and maintain security discipline across a network of operatives spread across a large geographic area.

The radicalization pathway that led Ahmad from the Jammu region across the LoC into LeT’s embrace is representative of a broader pattern that has fed militants into Pakistani organizations for three decades. Young men from the border districts of Jammu and Kashmir, particularly from areas adjacent to the LoC where cross-border contact is relatively easy, were recruited through a combination of ideological appeal, material incentive, and community pressure. The ideological component drew on grievances related to Indian military presence in Kashmir, the perception of Hindu-Muslim conflict in mixed-demographic areas, and the global jihadist narrative that LeT and similar organizations promoted through their media and madrassa networks. The material component offered training, weapons, purpose, and in some cases financial support for the recruit’s family. The community component operated through kinship networks and mosque-based social circles where radicalized individuals recruited peers. Ahmad’s departure from Jammu in 1999 was not an individual decision made in isolation; it was the product of a recruitment ecosystem that LeT and allied organizations had spent years building in the border districts.

The significance of Ahmad’s Jammu origins, rather than Kashmir Valley origins, should not be overlooked. The Kashmir insurgency’s center of gravity has historically been the Valley itself, particularly the districts of Srinagar, Baramulla, Shopian, and Pulwama. The Jammu region, while geographically adjacent, has a different demographic composition (Hindu-majority overall, with Muslim-majority pockets in districts like Rajouri, Poonch, Doda, and Kishtwar) and a different security dynamic. Militants operating in or originating from the Jammu region brought local knowledge that Kashmir Valley recruits did not possess: they understood the terrain of the Pir Panjal, the social dynamics of Hindu-Muslim coexistence in the border villages, and the specific vulnerabilities of minority settlements in the foothills. Ahmad’s Jammu background made him particularly suited to command operations in the Rajouri-Poonch sector, where his local knowledge of the terrain and demographics on the Indian side of the LoC complemented his organizational position on the Pakistani side.

His operational base was primarily the LeT headquarters complex at Muridke, a sprawling campus outside Lahore that serves as the organization’s administrative, educational, and logistical hub. Muridke is the heart of Lashkar-e-Taiba’s institutional infrastructure: the campus houses madrassas, a hospital, offices, residential quarters, and the organizational leadership. Operating from Muridke placed Ahmad within the LeT inner circle, with direct access to the senior command and to the logistical resources that the organization’s sprawling charitable front, Jamaat-ud-Dawa, provides.

In the period preceding his death, Ahmad had relocated from Muridke to Rawalakot. This relocation is analytically significant. Muridke offered proximity to LeT’s central command but limited access to the LoC and the infiltration corridors that fed militants into Poonch and Rajouri. Rawalakot offered the opposite: it placed Ahmad close to the operational theater where his planning and coordination work had the most immediate impact, at the cost of increased personal exposure. The move from a heavily guarded organizational headquarters to a smaller town closer to the border may have reflected an operational need to tighten command and control over infiltration activities. It may also have reflected overconfidence: a belief that PoK, under the Pakistan Army’s security umbrella, was safe from the kind of targeted killings that had already claimed LeT operatives in Karachi and other Pakistani cities.

Ahmad’s relationship with Sajjad Jaat, the chief commander of Lashkar-e-Taiba’s operational wing, placed him in the organization’s inner command tier. Jaat controls LeT’s cross-border operations, the military wing that plans and executes terror attacks in Indian territory. Ahmad’s close association with Jaat meant that he was not merely a regional operative but a trusted member of the operational command responsible for LeT’s most sensitive activities: the planning of attacks, the management of infiltration routes, and the coordination of logistics across the LoC.

Beyond operational planning, Ahmad managed financial aspects of LeT’s activities. Terror finance is the nervous system of any militant organization; without money, camps cannot be maintained, families of militants cannot be supported, weapons cannot be procured, and operatives cannot be moved. Ahmad’s financial role positioned him at the intersection of LeT’s operational and administrative wings, handling the flow of funds that sustained the infrastructure of violence. This dual role, as both operational planner and financial manager, made him a high-value target by any analytical measure. His elimination removed not just a commander who planned attacks but a logistician who understood how the organization’s money moved.

The combination of regional authority in the Poonch-Rajouri corridor, direct ties to LeT’s chief commander, operational planning capability, and financial management responsibility made Abu Qasim one of the most consequential mid-tier operatives in Lashkar-e-Taiba’s structure. He was not a co-founder like Amir Hamza, who was shot but survived in Lahore, nor a supreme leader like Hafiz Saeed, who sits in a Pakistani prison under a sentence that most analysts consider protective custody. Ahmad occupied the operational layer between strategic leadership and field execution, the layer that actually translates organizational intent into specific attacks on specific targets. The elimination of operatives at this layer does more immediate damage to an organization’s operational capability than the elimination of either the leadership (which is replaced through succession) or the foot soldiers (who are replaced through recruitment).

The Attacks Abu Qasim Enabled

The attack most directly attributed to Abu Qasim is the Dhangri village massacre, a twin terror assault on a Hindu-majority village in the Rajouri district of Jammu and Kashmir that unfolded across the evening of January 1 and the morning of January 2, 2023. The attack killed seven civilians and injured thirteen others, making it the deadliest terror assault in the Jammu division in years and the first major attack on a minority-community village since the relative calm that had prevailed in the region for nearly a decade.

Dhangri sits roughly eight kilometers from the Rajouri district headquarters. It is a small, predominantly Hindu village in a Muslim-majority district, a demographic profile that makes it representative of the scattered minority-community settlements that dot the foothills of the Pir Panjal range. These settlements have been targeted before: the Bal Jarallan massacre in February 1999 killed seven people at a wedding ceremony; attacks in Swari village in 1997, Kotedhara in 1998, Nirojal in 2002, Patrara in 2003, and Pangla in other years carved a record of sectarian violence against the Hindu minority in Rajouri. The Dhangri attack was not an isolated incident but the latest chapter in a pattern of deliberate targeting that stretches back to the peak years of the Kashmir insurgency.

On the evening of January 1, 2023, at approximately 7:00 p.m., two armed men entered Dhangri village. The gunmen approached at least three houses belonging to Hindu families and opened fire with rifles. The attack was indiscriminate in its execution but sectarian in its target selection: every household hit was Hindu, every victim was Hindu, and the attackers moved through the village with what witnesses described as deliberate intent, firing into homes where families had gathered on the first evening of the new year. Four people were killed in the initial gunfire: Satish Kumar, aged forty-five; Deepak Kumar, aged twenty-three; Pritam Lal, aged fifty-seven; and Shishu Pal, aged thirty-two. Multiple others sustained injuries, some critical.

One villager, Bal Krishan, a member of the local Village Defence Committee, fired back at the attackers with a weapon that had been distributed to VDC members to protect against precisely this kind of assault. Krishan’s intervention forced the gunmen to withdraw, preventing what might have been an even higher death toll. The Village Defence Committees, established in the mid-1990s during the height of the insurgency, arm civilians in vulnerable minority settlements and train them in basic defensive response. Krishan’s actions demonstrated both the committees’ value and their limitations: he disrupted the attack but could not prevent it or capture the assailants.

What made the Dhangri attack exceptional in its cruelty was the second phase. The attackers had planted an improvised explosive device near the home of Pritam Lal, one of the January 1 victims. The IED was concealed beneath a bag and went undetected during the security sweep that followed the initial attack, a lapse that later drew sharp criticism of the responding agencies. At approximately 9:00 a.m. on January 2, the device detonated. The blast killed two children: Vihan Sharma, aged four, and Samiksha Sharma, aged sixteen. The two were cousins. Five additional people were injured. The double-tap nature of the attack, gunfire followed by a pre-placed IED designed to detonate among those who gathered at the scene, revealed tactical sophistication and a willingness to target first responders and mourners. It also revealed planning: the IED had been placed during or immediately after the January 1 assault, meaning the attackers knew they would need to create a secondary event and had prepared for it in advance.

A seventh victim, Prince Sharma, who was in his early twenties and the younger brother of Deepak Kumar, died at Government Medical College Hospital in Jammu on January 8, having succumbed to injuries sustained in the initial gunfire. Prince and Deepak Sharma were siblings; Vihan and Samiksha Sharma were cousins. At least two pairs of family members died in the twin attacks, a concentration of grief that devastated individual families and terrified the broader community. The village refused to cremate the bodies for days, keeping them in the main square as a protest and demanding that the administration’s top representative visit Dhangri. The incident triggered deployment of eighteen additional companies of the Central Reserve Police Force to the Rajouri and Poonch districts.

Indian intelligence and security agencies identified Riyaz Ahmad, operating as Abu Qasim, as one of the chief conspirators behind the Dhangri attack. This attribution rested on his documented role as the LeT commander responsible for the Rajouri-Poonch sector, his operational authority over infiltration and attack planning in the twin border districts, and specific intelligence connecting him to the planning chain. It is important to note that Pakistani sources did not confirm this attribution, and no completed judicial investigation produced public evidence linking Ahmad to the attack by name. The attribution comes from Indian security assessments, which carry analytical weight given Ahmad’s known position but should be understood as an intelligence assessment rather than a proven legal finding.

Beyond the Dhangri attack, Ahmad’s role in reviving terrorism in Poonch and Rajouri implicates him in the broader pattern of violence that returned to these districts after years of relative quiet. The twin border districts had been considered largely terrorism-free for nearly a decade before a surge of incidents beginning in the early 2020s shattered that calm. Encounters in forested areas, IED recoveries, and infiltration attempts increased, particularly in the mountainous terrain that connects PoK’s Rawalakot and Haveli districts to Indian-administered Poonch and Rajouri. Ahmad’s role as the coordinator of LeT’s cross-LoC operations from his base in Rawalakot placed him at the center of this resurgence. He was not an individual gunman who crossed the border to execute a single attack; he was the regional commander who directed the entire operational pipeline, from recruitment through training, logistics, infiltration, and attack execution.

The Rajouri-Poonch sector’s geography explains why a single commander could exert this level of influence. The sector is defined by the Pir Panjal range, a series of mountain ridges that separate the Kashmir Valley from the Jammu plains. The LoC in this sector runs through dense forests and mountain passes, many of them unmonitored except by periodic patrols. The terrain is ideally suited for infiltration: small groups of two or three militants can cross on foot during summer months when the snow melts and the passes become navigable. From PoK’s side, Rawalakot is the last significant town before the mountain crossings. From the Indian side, the first settlements the infiltrators encounter are the villages of Poonch and Rajouri districts, including villages like Dhangri. Ahmad’s position in Rawalakot gave him direct oversight of the final stage of the infiltration pipeline: the last briefing, the selection of crossing points, and the communication link back to PoK that militants would use after entering Indian territory.

The year 2023 proved exceptionally violent in the Rajouri-Poonch sector. Beyond the Dhangri attack, the district saw multiple encounters between security forces and militants. An encounter at Kesari Hill in Kotranka in May cost five Indian Army paratroopers their lives. Another encounter at Baaji Maal in Kalakote in November killed five more soldiers, including two officers. Militants were eliminated in encounters at Gunda Khawas, Narla Bambal, and Behrote Gali throughout the year. Eleven Indian soldiers lost their lives in Rajouri district alone during 2023, alongside eight militants killed in encounters. This operational tempo, the highest in the district in over a decade, correlates directly with Abu Qasim’s period of maximum operational influence from his Rawalakot base. His elimination in September 2023 came in the middle of this surge, and whether the subsequent encounters represented the tail end of operations he had already set in motion or ongoing activity by the network he had built is an analytical question that the operational record does not fully resolve.

The dual timeline of the Dhangri attack and the Abu Qasim elimination, reconstructed in parallel, makes the attack-to-consequence chain visible as a structural mirror. On the Dhangri side: January 1, 2023, approximately 7:00 p.m., two armed militants enter the village from the surrounding hills. They approach residential structures belonging to Hindu families. The firing begins at three separate houses. Satish Kumar, forty-five, is killed at his home. Deepak Kumar, twenty-three, and his younger brother Prince Sharma die from gunshot wounds, though Prince’s death comes days later in a Jammu hospital. Pritam Lal, fifty-seven, is killed. Shishu Pal, thirty-two, is killed. Bal Krishan, a Village Defence Committee member armed with a weapon distributed for exactly this purpose, fires back and forces the attackers to withdraw. The militants retreat but leave behind an IED concealed beneath a bag near Pritam Lal’s house. January 2, approximately 9:00 a.m., the device detonates among people who had gathered near the attack site. Vihan Sharma, four years old, dies at the scene. Samiksha Sharma, sixteen, his cousin, dies from blast injuries. The security forces that descended on Dhangri after the January 1 shooting had swept the area but failed to detect the explosive device, a lapse that drew immediate criticism and deepened the community’s sense of betrayal.

On the Rawalakot side: September 2023, the specific date not publicly confirmed to the day in open-source reports. Unknown gunmen enter al-Qudus mosque in the Rawalakot area of Pakistan-Occupied Kashmir. The mosque sits in a community where Abu Qasim has been living since his recent relocation from Muridke. He is among the congregation, performing prayers. The gunmen identify him, approach, and shoot him in the head at point-blank range. He dies on the floor of the mosque. The attackers depart. No one is apprehended. No group claims responsibility. PoK police register a case that produces no publicly reported progress.

The mirror structure of these two timelines encapsulates the shadow war’s central logic more clearly than any analytical abstraction. In Dhangri, militants directed by Abu Qasim entered a civilian space, a village, and killed seven people including children. In Rawalakot, unknown gunmen entered a civilian space, a mosque, and killed Abu Qasim. The symmetry is not coincidental; it is the operational expression of a doctrine that treats every attack as the first link in a chain that will reach back to the attacker’s principal. The Dhangri victims were ordinary civilians whose only offense was living in a Hindu-majority village in a district where LeT wanted to project terror. Abu Qasim was a military commander whose offense was directing that terror. The chain connecting them is the arc of consequence that the shadow war traces in blood.

The broader pattern of violence in the Rajouri-Poonch sector during Abu Qasim’s period of influence deserves deeper examination because it reveals the scale of his operational footprint. The twin border districts stretch across more than 2,600 square kilometers of mountainous terrain, with the Pir Panjal range creating natural barriers between the Kashmir Valley to the north and the Jammu plains to the south. The terrain is divided into six sub-divisions, each with its own security dynamics. The districts share borders with Shopian and Kulgam in south Kashmir through the upper mountain ranges, creating a corridor through which militants can transit between the Kashmir Valley and the Jammu region. Ahmad’s command of the LeT pipeline feeding militants into this corridor gave him influence over operations affecting multiple sub-divisions simultaneously.

The attacks Ahmad directed or facilitated were not limited to high-profile massacres like Dhangri. The revival of terrorism in Poonch and Rajouri involved a spectrum of activities: infiltration attempts detected by border patrols, arms caches recovered by security forces, recruitment of local youth as hybrid terrorists who could conduct attacks without crossing the border, and the establishment of overground worker networks that provided logistics and intelligence. Each of these activities required coordination from the PoK side, and Ahmad’s position in Rawalakot placed him at the nerve center of that coordination. The eleven Indian soldiers who died in Rajouri encounters during 2023 were casualties of an operational pipeline that Ahmad had built and was actively managing when the first shots were fired in Dhangri.

The Village Defence Committee system that Bal Krishan invoked when he fired back at the Dhangri attackers represents an aspect of the conflict that directly intersects with Ahmad’s operational planning. VDCs were established during the height of the insurgency to give vulnerable minority settlements a minimal defensive capability. The committees arm and train civilian volunteers, typically men from the village itself, to respond to militant incursions. Ahmad, as the planner of operations targeting these communities, would have known about the VDC presence in Dhangri. The fact that the attack proceeded despite this knowledge, and that the militants included an IED as a secondary device presumably designed to catch security forces or VDC members who responded to the initial shooting, suggests tactical planning that accounted for and attempted to exploit the defensive measures. The IED detonated not among armed responders but among civilians, including children, who had gathered near the attack scene the following morning. Whether this was the intended target or a timing failure that produced different casualties than planned is unknown, but the tactical layering of immediate gunfire followed by a delayed explosive device reflects a level of planning sophistication that points to a commander with experience rather than ad hoc fighters acting on impulse.

Network Connections

Abu Qasim’s position within Lashkar-e-Taiba connected him vertically to the organization’s supreme command and horizontally to its operational infrastructure across multiple theaters. Understanding his network connections requires mapping the organizational layers he touched and the individuals he worked with at each layer.

At the apex of his command chain sat Hafiz Muhammad Saeed, the founder and ideological leader of Lashkar-e-Taiba and its charitable front Jamaat-ud-Dawa. Saeed was sentenced to prison by a Pakistani anti-terrorism court in connection with terror financing charges, a prosecution widely understood as a cosmetic response to international pressure from the Financial Action Task Force rather than a genuine attempt to dismantle the organization he built. From prison, Saeed’s influence over LeT’s strategic direction continues through intermediaries. Ahmad’s years of operating from Muridke, LeT’s headquarters campus, would have placed him in regular contact with Saeed’s inner circle and within the decision-making structures that set organizational priorities.

The more operationally relevant connection was to Sajjad Jaat, Lashkar-e-Taiba’s chief commander. Jaat runs LeT’s military operations, the wing of the organization responsible for planning and executing attacks in Indian territory. Ahmad’s relationship with Jaat was described by Indian security officials as close, implying not merely an organizational reporting line but a working partnership in which Ahmad functioned as Jaat’s regional delegate for the Poonch-Rajouri sector. This relationship gave Ahmad authority to plan and authorize operations within his sector, subject to the strategic guidance of LeT’s central command. The degree of autonomy that regional commanders exercise within LeT is debated among analysts. Stephen Tankel, who has produced the most comprehensive English-language study of LeT’s organizational structure, argues that the organization maintains relatively tight central control over major operations while allowing regional commanders flexibility in tactical execution. If Tankel’s analysis applies to Ahmad’s case, then the Dhangri attack would have required at minimum approval from the central command, even if the tactical details were left to Ahmad’s judgment.

Ahmad’s horizontal connections extended to the network of LeT operatives who have been systematically targeted across Pakistan. He operated within the same organizational ecosystem as Mufti Qaiser Farooq, the Hafiz Saeed aide killed near a Karachi religious institution, and Ziaur Rahman, the LeT operative gunned down on his evening walk in the same city. While these operatives served in different geographic zones, they shared organizational affiliation, command structures, and communication networks. Each elimination in the LeT network potentially exposed connections to others. Intelligence agencies that penetrated the network around one target gained access to communication patterns, meeting locations, and operational planning that could lead to additional targets. The cascade effect of network penetration is one of the defining features of the shadow war: each killing is both an end point and a starting point.

Within the Rajouri-Poonch sector, Ahmad commanded a local network of operatives, guides, couriers, and support personnel who facilitated the movement of militants and materiel across the LoC. This network included individuals on both sides of the border. On the PoK side, safe houses in Rawalakot and surrounding villages sheltered militants in transit, stored weapons and communications equipment, and served as briefing locations where infiltrating groups received their final instructions before crossing the mountains. On the Indian side, overground workers, local contacts who provide shelter, food, reconnaissance, and intelligence to infiltrating militants, maintained the other end of the pipeline. The Dhangri attack’s execution by militants who had clearly received specific targeting information about the village’s demographics, layout, and VDC presence suggests that this overground network was functioning effectively enough to provide detailed pre-attack intelligence.

Ahmad’s dual role in operational planning and financial management gave him visibility into LeT’s funding mechanisms. Terror financing for organizations like LeT flows through multiple channels: donations from sympathizers in Pakistan and the Gulf states, revenue from Jamaat-ud-Dawa’s network of charitable institutions, proceeds from legitimate businesses that serve as fronts, and, according to Indian and international intelligence assessments, funds channeled through Pakistan’s Inter-Services Intelligence directorate. Ahmad’s management of financial flows meant he understood which channels funded which operations, how money moved from donors to field operatives, and what the organization’s financial vulnerabilities were. This financial knowledge made his elimination particularly costly for LeT: replacing a commander is a matter of succession planning, but replacing the institutional knowledge of how money moves through an organization requires time and carries the risk of exposure during the transition.

The connection between Ahmad and the broader landscape of eliminated LeT operatives reveals a pattern of progressive network degradation. When the first LeT operatives were killed by unknown gunmen, the remaining leadership could adjust by changing routines, relocating, and tightening operational security. As the number of eliminations increased, the network’s capacity to adapt diminished. Each killed operative represented not just a loss of personnel but a loss of institutional knowledge, a disruption of established communication patterns, and a psychological blow to the survivors. Ahmad’s killing in PoK intensified this psychological pressure because it demonstrated that even the organization’s most secure territory was no longer beyond reach. If LeT commanders could be shot dead during prayers in a PoK mosque, then no location in Pakistan offered genuine safety.

The relationship between Ahmad’s network and Pakistan’s Inter-Services Intelligence directorate is the most analytically significant and most difficult to document of his connections. ISI’s relationship with Lashkar-e-Taiba is one of the most extensively documented state-terror nexuses in modern history. Multiple international investigations, including the trial of Ajmal Kasab after the 26/11 Mumbai attacks, the testimony of David Coleman Headley before American and Indian courts, and the findings of the Financial Action Task Force, have established that ISI provided funding, training, logistical support, and operational guidance to LeT over a period spanning decades. Ahmad’s position as a senior LeT commander operating from Muridke and then from Rawalakot places him within this nexus. His operational planning for cross-LoC infiltration could not have functioned without at least the acquiescence of the Pakistan Army units that control the LoC frontier and the checkpoints that govern movement in the border zones. The guides who lead militants through mountain passes operate in terrain that the Pakistan Army surveys. The safe houses that shelter militants in transit sit in towns where the Army maintains garrisons. The weapons that militants carry across the LoC pass through territory that the Army secures. At every point in the infiltration pipeline that Ahmad managed, the Pakistan Army’s security infrastructure is present, and at no point has that infrastructure been documented to have interdicted militants transiting from PoK into Indian Kashmir as a systematic practice.

This structural complicity, the difference between actively directing operations and passively allowing them to proceed, is central to understanding Ahmad’s network position. He did not operate in a vacuum; he operated within an ecosystem where the state’s security apparatus created the permissive conditions for his activities. The safe haven that Rawalakot provided was not an accident of geography but a product of policy: the Pakistan Army chose not to interdict the infiltration infrastructure because that infrastructure served Pakistan’s strategic interests in Kashmir. Ahmad was, in this framework, both an independent actor making operational decisions and a functionary operating within a system that the state maintained. His elimination removed the actor but did not dismantle the system. The infiltration corridors still exist. The mountain passes are still unmonitored during summer. The safe houses can be restaffed. The guides who know the terrain can be reassigned to a new commander. The system that produced Abu Qasim will, unless structurally altered, produce his successor.

Ahmad’s network also extended downward to the militants he recruited, trained, and dispatched. These individuals, often young men from both sides of the LoC who were radicalized through LeT’s madrassa network or through direct recruitment by local operatives, represent the human material of the infiltration pipeline. Ahmad’s role was not to recruit them personally but to manage the pipeline through which they passed: assigning them to training camps, coordinating their transit through PoK, briefing them on their infiltration routes, and maintaining communication with them after they crossed into Indian territory. The militants who carried out the Dhangri attack were the end product of this pipeline. They arrived in a Hindu-majority village with specific instructions, weapons, and an IED. Someone had briefed them on the target, the approach route, the escape plan, and the secondary device. Ahmad’s command authority over the Rajouri sector makes him the most plausible source of that operational direction.

The destruction of this particular node in the network, the regional commander who coordinated the pipeline’s final stage, creates a specific kind of organizational disruption. LeT’s structure is hierarchical but not rigidly so; regional commanders exercise operational autonomy within strategic guidelines set by the central command. When a regional commander is killed, the local network he managed does not automatically connect to his replacement. Relationships with guides, safe house operators, overground workers on the Indian side, and local intelligence sources are often personal rather than institutional. They depend on trust built over time, on knowledge of specific individuals’ reliability, and on communication protocols that the commander established. A new commander arriving from Muridke or from another sector would need to rebuild these relationships, a process measured in months rather than days. During that rebuilding period, the pipeline’s efficiency degrades, infiltration attempts are more likely to fail, and the operational tempo in the Poonch-Rajouri sector diminishes. Ahmad’s elimination aimed to create precisely this window of degraded capability.

The Hunt

Open-source reporting provides limited detail on how Abu Qasim was located, surveilled, and targeted. The operational specifics of the intelligence preparation that preceded his killing remain classified or unreported, as is the case for every elimination in the shadow war. What can be reconstructed from the available evidence and from comparative analysis with other cases in the series is the probable intelligence process that led to the killing.

The starting point was target identification. Indian intelligence had identified Riyaz Ahmad as a senior LeT operative responsible for the Poonch-Rajouri sector well before the Dhangri attack. His role in reviving terrorism in the twin border districts had been documented through multiple sources: intercepted communications, reports from captured or surrendered militants who had operated under his direction, and intelligence shared between Indian agencies monitoring the LoC. When the Dhangri attack occurred on New Year’s Day 2023, the attribution to Ahmad was not a cold start; it built on existing intelligence about his position, his operational role, and his command authority in the sector where the attack took place.

Target location presented a different challenge. Ahmad had been operating from Muridke, LeT’s fortified headquarters outside Lahore, for much of his career. Muridke is effectively impenetrable for covert operations: it is a guarded campus with controlled access, and any attack there would require penetrating multiple security layers maintained by both LeT and the sympathetic elements of Pakistan’s security establishment. Ahmad’s relocation to Rawalakot changed the calculus. Rawalakot, while still in PoK and under Pakistan Army security, is an ordinary town rather than a military installation. Ahmad would have been living in regular housing, attending a local mosque, moving through local markets, a pattern of daily life that is inherently more observable than life behind the walls of Muridke.

The critical intelligence requirement was establishing Ahmad’s prayer schedule and mosque affiliation. Happymon Jacob, the JNU scholar who has studied the security dynamics of the LoC environment, has noted that PoK towns like Rawalakot function as communities where everyone’s presence and movements are locally known. A newcomer relocating from Muridke would have been noticed. His attendance at al-Qudus mosque would have become a matter of community knowledge within weeks. The intelligence challenge was not identifying which mosque he attended, it was placing an asset or surveillance capability close enough to confirm his routine and transmit that confirmation to an operational team.

The surveillance phase required patience. Mosque attendance, while predictable in timing, varies in specific prayer sessions. Ahmad may have attended all five daily prayers at the same mosque, or he may have attended some prayers at home and only certain congregational prayers at al-Qudus. The attackers’ successful execution during a specific prayer time suggests they had confirmed not just his general mosque affiliation but his specific attendance pattern for the session at which they struck. This level of intelligence granularity typically requires weeks of observation by local assets who can monitor the target without arousing suspicion.

Myra MacDonald, the author of “Defeat is an Orphan” and a respected analyst of India-Pakistan proxy warfare, has written about the LoC as a corridor of intelligence as well as of infiltration. Information flows across the Line of Control in both directions: militants move from PoK into Indian Kashmir, but intelligence also flows from Indian Kashmir back into PoK. The networks that move militants through the mountains can, with the right recruitment or coercion of individual members, be reversed to move intelligence in the opposite direction. A guide who leads militants across the passes into Poonch knows the terrain, the checkpoints, and the people on the PoK side. That same guide, turned by Indian intelligence, becomes a source of information about who is in Rawalakot, what they are doing, and where they can be found.

The operational team that executed the killing would have needed three capabilities: the ability to reach al-Qudus mosque undetected, the ability to identify Ahmad within the congregation, and the ability to extract from Rawalakot after the shooting. Each of these requirements presents distinct challenges in the PoK environment. Reaching the mosque undetected required either local residency (operatives who lived in Rawalakot and would not be questioned) or infiltration from outside (operatives who entered the town and reached the mosque without passing through checkpoints that would flag unknown individuals). Identifying Ahmad within the congregation required either a physical description detailed enough for a visual match or a local confederate who could confirm his position. Extracting after the shooting required predetermined escape routes, transportation, and safe houses or border-crossing points.

The comparative evidence from other PoK operations is instructive. The Khwaja Shahid killing used a dramatically different method: kidnapping and beheading rather than a targeted shooting. This difference may indicate that different operational conditions in different parts of PoK produce different tactical choices. A mosque shooting in Rawalakot is a rapid, high-visibility operation that requires minimal time on the ground. A kidnapping and beheading near the LoC is a slow, labor-intensive operation that requires the ability to hold a captive. The two methods may reflect the operational teams’ assessment of which approach was feasible given the specific security conditions they faced. In Rawalakot, the population density and Army presence may have made a prolonged operation (kidnapping) impractical, favoring a rapid strike. Near the LoC, the lower population density may have allowed a more deliberate approach.

The intelligence preparation for the Abu Qasim killing, whatever its specific methods, demonstrates a surveillance penetration of PoK that no previous public evidence had established. The Karachi and Lahore killings occurred in large cities where operational anonymity is readily available. The PoK killings, in Rawalakot and along the LoC, occurred in controlled territory where outsiders are noticed and the Pakistan Army provides the security framework. Conducting a targeted killing in this environment required either turning local assets who could provide information and support from within the community, or deploying a team capable of operating undetected in a territory that is essentially under military governance.

The question of how the intelligence cycle for the Abu Qasim operation was initiated is analytically important because it illuminates the relationship between the Dhangri attack and the response. Two models are possible. In the first model, Ahmad was already a known and tracked target before the Dhangri attack occurred. His role as LeT’s Poonch-Rajouri commander would have made him a figure of interest to Indian intelligence regardless of any specific attack. Under this model, the Dhangri massacre may have accelerated an existing intelligence collection effort rather than initiating one from scratch. The nine-month timeline between Dhangri and the killing is consistent with this interpretation: a target whose location was already approximately known could have been precisely fixed within months once additional intelligence resources were allocated.

In the second model, the Dhangri attack served as the trigger that placed Ahmad on the priority target list. Under this interpretation, Indian intelligence identified Ahmad as the chief conspirator through post-attack analysis, communications intercepts, or information from captured militants, and then built the targeting intelligence from a relatively cold start. A nine-month timeline from identification to elimination, in a hostile foreign territory, would represent an extremely rapid intelligence cycle. For comparison, the targeted killing of Zahoor Mistry involved years of intelligence collection to locate a man living under a false identity in Karachi. The Pathankot-to-Shahid Latif chain stretched over seven years. If the Abu Qasim operation was genuinely built from a cold start after Dhangri, it would represent the most efficient intelligence-to-action pipeline documented in the entire campaign.

The truth likely sits between these two models. Ahmad was probably known to Indian intelligence before Dhangri, given his seniority and his role in the Poonch-Rajouri sector. The Dhangri attack likely elevated him from a known figure to a priority target, focusing resources on confirming his location and patterns. The combination of prior awareness and post-attack urgency could explain the nine-month timeline: faster than a cold start but slower than a well-prepared standing operation.

The human intelligence dimension of the operation deserves particular attention because it is probably the most critical factor in the killing’s success. Technical intelligence, intercepted communications, satellite imagery, electronic monitoring, can identify a target’s general location and communication patterns. Human intelligence, information provided by individuals with direct access to the target’s environment, can identify his specific mosque, his specific seat in the congregation, and the specific prayer time when he is reliably present. The precision of the Abu Qasim killing suggests that human intelligence played the decisive role. Someone who knew Abu Qasim’s daily routine provided that information to the operational planners. Whether that source was a recruited local asset, a disaffected member of Ahmad’s own network, or an individual who crossed the LoC carrying the information, the source existed and delivered actionable intelligence of extraordinary specificity.

The risks of the operation were significant and would have been carefully weighed during the planning phase. A failed attempt, in which the attackers were detected, captured, or killed before reaching the target, would have been catastrophically damaging. Captured operatives in PoK would have been paraded before Pakistani media as proof of Indian aggression. Their identities, equipment, and communications would have been analyzed to map the intelligence network that supported them. Failed operations would have triggered a security crackdown in PoK that would have made subsequent operations far more difficult. The decision to proceed with the al-Qudus mosque operation indicates that the intelligence was assessed as reliable enough and the operational plan sound enough to justify these risks. In the intelligence profession, the willingness to accept risk is proportional to the confidence in the information and the value of the target. The Abu Qasim operation’s execution suggests high confidence on both counts.

Pakistan’s Response

Pakistan’s official response to the Abu Qasim killing followed the pattern established by its response to earlier targeted killings across the country. PoK police registered a case, which is the standard procedural step. Investigations into similar killings in Karachi, Lahore, and other cities have produced no publicly reported arrests, no prosecutions, and no identified suspects. The Abu Qasim case was no different. The killing was reported in Pakistani media, acknowledged by PoK authorities as having occurred, and effectively shelved.

The absence of investigative progress is itself an analytical data point. Pakistan’s intelligence apparatus, led by the Inter-Services Intelligence directorate, is among the most capable in the region. ISI has successfully tracked, identified, and neutralized targets within Pakistan when it has the institutional will to do so, as demonstrated by its cooperation with the CIA in capturing high-value al-Qaeda targets during the early years of the War on Terror. The consistent failure to produce any suspects in the targeted killings of LeT, JeM, and Hizbul Mujahideen operatives suggests one of three possibilities: ISI is genuinely unable to identify the perpetrators, ISI knows who is responsible but is unwilling or unable to act, or ISI is complicit at some level in the operations. Each of these possibilities carries different implications for understanding Pakistan’s role in the shadow war.

The first possibility, genuine inability, is the least plausible. A targeted killing inside a mosque in a small PoK town, where community dynamics are intimate and outsiders are noticed, should produce leads. Someone saw unfamiliar faces. Someone heard something. Community members who attended the same mosque could describe who was present during the prayer when Ahmad was shot. The absence of any reported investigative progress suggests that the information exists but is not being pursued.

The second possibility, unwillingness to act despite knowledge, aligns with the broader pattern of Pakistan’s relationship with the organizations whose members are being killed. Pakistan has maintained Lashkar-e-Taiba and Jaish-e-Mohammed as strategic assets for decades, using them as instruments of proxy warfare in Kashmir while periodically subjecting them to cosmetic crackdowns when international pressure demands it. The targeted killings create a contradiction for Pakistan’s security establishment: the victims are assets that Pakistan has invested in building, but the perpetrators appear to enjoy a level of operational freedom within Pakistan that would be difficult to sustain without at least passive tolerance from elements of the security apparatus. Pakistan cannot simultaneously investigate the killings vigorously and maintain the strategic ambiguity that currently allows it to avoid directly confronting either the killers or their alleged sponsors.

The third possibility, active complicity, is the most explosive. It implies that elements within Pakistan’s own security establishment are cooperating with an external intelligence agency (presumably India’s Research and Analysis Wing) to facilitate the elimination of assets that other elements of the same establishment have spent years cultivating. Rana Banerji, the former RAW special secretary who has written extensively on the Rajouri-Poonch sector security dynamics, has noted that the Pakistan Army’s internal factions do not always share the same strategic objectives regarding militant groups. The Army’s conventional military leadership has sometimes viewed militant proxies as strategic liabilities rather than assets, particularly when those proxies provoke Indian military responses that the conventional forces must then deter or absorb. It is conceivable, though not proven, that some elements within the Pakistani security establishment view the targeted elimination of certain militants as serving Pakistan’s broader strategic interest, even as other elements view the same killings as an assault on Pakistan’s sovereignty.

Pakistan’s public response has been to blame India and to frame the killings as violations of Pakistani sovereignty. This framing is consistent regardless of which specific militant is killed. Pakistan has raised the targeted killings in diplomatic forums and in bilateral communications with India, alleging RAW involvement. India has consistently denied responsibility. The diplomatic performance is itself ritualized: Pakistan protests, India denies, and the killings continue. The ritual suggests that both sides have calculated the costs and benefits of the current dynamic and reached an implicit equilibrium in which the killings are tolerated within certain boundaries that neither side makes explicit.

In PoK specifically, the Abu Qasim killing created additional security concerns for the Pakistan Army’s garrison. If an operative could be shot dead in a mosque in Rawalakot, then the security architecture that the Pakistan Army provides in PoK had been penetrated. This penetration undermined the fundamental promise that PoK offers to militant organizations: that it is safe territory, beyond the reach of Indian intelligence operations, where militants can live, train, and plan without fear of the kind of targeted strikes that characterize the broader campaign. The Abu Qasim killing, together with the earlier Khwaja Shahid killing, demonstrated that this promise was no longer reliable. For the remaining senior militants operating in PoK, the message was unambiguous: the territory that was supposed to protect you has become another hunting ground.

The institutional consequences within Pakistan’s security apparatus likely extended beyond the immediate investigation, or lack thereof. The Pakistan Army’s 23rd Division, responsible for the PoK sector that includes Rawalakot, would have conducted an internal review of how an armed operation was carried out in territory under its direct security control. PoK is not civilian-governed territory in any meaningful sense; the Pakistan Army exercises final authority over security matters, and the local administration operates within the framework the military defines. An assassination conducted within this framework implicates the military’s competence directly. Either the security perimeter around Rawalakot was inadequate to prevent armed infiltration, or the security forces failed to detect hostile surveillance of a high-value asset over a period of weeks, or someone within the security architecture provided information or facilitated access. Each explanation is uncomfortable for the Pakistan Army’s institutional self-image as the guarantor of PoK’s security.

The political dynamics within PoK itself are often overlooked in analyses that focus on the India-Pakistan dimension. PoK has its own administration, its own legislative assembly, and a population that lives under security arrangements imposed by Islamabad. The Abu Qasim killing occurred in a territory where local residents have long complained about the suffocating security presence while simultaneously depending on that presence for stability. A mosque killing in Rawalakot would have sent ripples through the local population: if a senior militant commander could be shot during prayers, what guarantee did ordinary citizens have that violence would not expand to include bystanders? The operational precision of the killing, in which only the intended target was harmed, would have offered some reassurance that the violence was targeted rather than indiscriminate. The fact that the killing occurred inside a mosque, a communal sacred space, would have generated the opposite reaction: a sense that no space in Rawalakot was truly safe.

The lack of any public accounting, no arrests, no identified suspects, no explanation of how the security perimeter was breached, is consistent with a pattern observed across the entire shadow war. Pakistan has not produced a single arrest in connection with the targeted killings of LeT, JeM, Hizbul Mujahideen, or Khalistani operatives across its territory. This blanket investigative failure, spanning multiple cities, multiple organizations, and multiple years, is itself evidence of a policy decision. Pakistan’s security establishment has apparently concluded that investigating these killings vigorously would produce more problems than it would solve. Identifying the perpetrators might confirm Indian involvement, which would create diplomatic pressure for a response that Pakistan is not prepared to deliver. Alternatively, investigation might reveal complicity within Pakistan’s own security apparatus, which would be even more damaging. The path of least institutional resistance is precisely what has been chosen: register the case, express outrage, and let the investigation die quietly.

The implications for Pakistan’s international credibility on counter-terrorism are substantial and cumulative. Each uninvestigated killing adds to the body of evidence suggesting that Pakistan either cannot or will not exercise sovereign control over its own territory. The Financial Action Task Force, which had placed Pakistan on its grey list for years over terror financing failures, would find in the uninvestigated targeted killings additional evidence that Pakistan’s security governance is dysfunctional. International partners who have pressured Pakistan to act against terror groups operating on its soil can point to the Abu Qasim case as evidence of a deeper problem: Pakistan cannot simultaneously claim to host these groups as a sovereign prerogative and claim to be unable to investigate their leaders’ assassinations. The contradiction is not merely analytical; it is strategic. Each unresolved killing erodes the narrative that Pakistan manages its security territory competently, and it reinforces the narrative that others have concluded Pakistan will not act, and have therefore acted on Pakistan’s territory themselves.

What This Elimination Reveals

The Abu Qasim killing is, in analytical terms, the purest expression of the shadow war’s central logic. The House Thesis that runs through this entire series holds that every attack generates a target and every target, when eliminated, reveals the network that produced them, the state that protected them, and the doctrine that hunted them. The Dhangri-to-Rawalakot chain embodies this proposition with textbook clarity.

The attack generated the target: the Dhangri massacre on January 1-2, 2023, killed seven people, including two children. Indian intelligence identified Abu Qasim as the chief conspirator. The identification elevated him from a regional operative of known importance to a priority target whose elimination carried both operational and symbolic significance.

The target was eliminated: nine months after Dhangri, Abu Qasim was shot in the head at point-blank range during prayers inside al-Qudus mosque in Rawalakot, PoK. The speed of the attack-to-elimination chain suggests either pre-existing surveillance or a rapid intelligence mobilization in response to the Dhangri attack.

The elimination revealed the network: Abu Qasim’s killing exposed the vulnerability of LeT’s PoK infrastructure. An operative who had relocated from Muridke to Rawalakot, who attended a local mosque, who maintained connections to LeT’s chief commander Sajjad Jaat, and who managed financial flows for the organization was found, fixed, and finished in territory that the Pakistan Army controls. The intelligence capability required to accomplish this reveals either deep human penetration of PoK’s militant and civilian communities or a technical surveillance capability that can operate in a restricted environment.

The elimination revealed the state that protected him: Pakistan’s inability or unwillingness to prevent the killing, to investigate it, or to arrest any suspects exposes the hollowness of the security guarantee that PoK was supposed to provide. The Pakistan Army’s 23rd Division is headquartered in the region. Checkpoints dot the roads. Yet an assassination team reached al-Qudus mosque, executed a senior LeT commander during prayers, and departed without interception. This failure is not merely an intelligence lapse. It is a structural exposure: the same security apparatus that facilitates militant infiltration into India proved unable to protect the commanders who direct that infiltration within its own territory.

The elimination revealed the doctrine: the mosque-targeting pattern that claimed Abu Qasim has claimed others. Shahid Latif was shot inside a mosque in Sialkot. Other operatives have been killed near religious institutions. The pattern exploits the most predictable routine in the target’s life, the one governed by religious obligation rather than personal choice. A militant can vary his walking routes, change his residence, alter his shopping patterns. He cannot easily change which mosque he attends without arousing community suspicion, and he cannot change the prayer schedule, which is determined by astronomical calculation and published in advance. The mosque is the one place where a practicing Muslim must be, at the one time that cannot be moved. The doctrine that exploits this vulnerability is operationally rational and ethically fraught, and Abu Qasim’s case is the clearest illustration of both dimensions.

The Dhangri-to-Rawalakot chain also challenges the characterization of the targeted killings as random or opportunistic. The speed of the response, the precision of the execution, and the geographic boldness of operating in PoK all point to a coordinated and prioritized campaign rather than a series of isolated incidents. Random violence does not produce attack-to-elimination chains measured in months. Opportunistic killings do not reach into the most heavily guarded territories. The Abu Qasim case is evidence, as strong as any single case can be, that the shadow war operates according to a target-selection doctrine that prioritizes individuals responsible for specific attacks against Indian civilians and that is willing to operate in any environment, however hostile, to reach those targets.

The PoK dimension of the killing carries implications that extend beyond the immediate operational question. For decades, the Line of Control has functioned as a one-way corridor: militants cross from PoK into Indian Kashmir, and India responds through diplomatic protest, border security, and occasional military operations (the 2016 surgical strikes, the 2019 Balakot airstrike). The Abu Qasim killing reversed the direction of the corridor. For the first time, lethal force crossed from the Indian strategic sphere into PoK, not through airstrikes or artillery but through a covert operation that reached a specific individual in a specific mosque in a specific town. This reversal transforms the nature of the LoC as a strategic boundary: it is no longer a wall that protects Pakistani-side militants from Indian reach but a border that violence can cross in both directions.

The reversal has implications for deterrence. If the LoC protects only Indian territory from infiltration but does not protect PoK territory from counter-operations, then the incentive structure for Pakistan’s security establishment shifts. Facilitating infiltration into India still generates the strategic benefits Pakistan seeks (pressure on India in Kashmir, attrition of Indian security forces, domestic political utility), but it now also generates a direct cost: the commanders who plan the infiltration become targets in their own safe havens. The Abu Qasim killing is the case that makes this cost tangible. A commander who planned an attack on Dhangri was killed in Rawalakot nine months later. Future commanders contemplating similar attacks must now calculate whether the operational benefits of a Dhangri-style massacre are worth the personal risk that it will generate a Rawalakot-style response.

Srinath Raghavan, the historian who has documented the long pattern of civilian targeting in the Kashmir conflict, has argued that deterrence operates at the individual level as well as the state level. States may or may not be deterred by the prospect of retaliation, but individual commanders are keenly aware of their own mortality. The shadow war’s targeting of individuals who planned specific attacks creates a form of individual deterrence that no amount of diplomatic protest or economic sanction can replicate. The commander who knows that planning an attack on an Indian village may result in his own death inside a PoK mosque faces a decision calculus fundamentally different from the commander who knows that the worst consequence of his actions will be a diplomatic note from Delhi to Islamabad.

The Abu Qasim case also exposes the operational limits of Pakistan’s counter-intelligence capabilities in PoK. If the intelligence preparation for the mosque killing was conducted by assets operating within PoK, then Pakistan’s counter-intelligence services failed to detect hostile intelligence activity in a controlled territory. If the preparation was conducted through technical means (signals intelligence, satellite surveillance, communications intercepts), then Pakistan’s electronic security proved inadequate to protect a senior militant commander. In either case, the successful elimination reveals a gap in Pakistan’s defensive intelligence posture that the remaining senior militants in PoK must now contend with. The psychological impact of this gap may prove more significant than the operational impact of losing Abu Qasim himself: the knowledge that the hunters can reach into PoK changes the behavior of every potential target in the territory, forcing them into more restrictive security measures that reduce their operational effectiveness even if they personally survive.

The financial dimension of Abu Qasim’s elimination adds a layer that is often overlooked in analyses focused on operational command. Ahmad managed financial flows for LeT. His death disrupted not just the planning of attacks but the movement of money that sustains them. Terror financing networks are brittle: they depend on trusted intermediaries who know the channels, the contacts, the amounts, and the timing of transfers. Replacing a financial manager requires identifying someone who can be trusted with the same level of institutional knowledge, briefing them on existing financial relationships, and re-establishing the flows that were disrupted. During this transition, operations slow, funds are delayed, and the organization’s ability to project force diminishes. The shadow war’s targeting of individuals who occupy dual operational-financial roles, as Ahmad did, compounds the impact of each individual killing by attacking both the organization’s planning capability and its financial infrastructure simultaneously.

The comparative dimension places the Abu Qasim killing within a broader analytical context. Israel’s Mossad, the most documented practitioner of targeted killings by a democracy, has conducted operations in hostile territory for decades, from the Wrath of God campaign after the Munich Olympics to the assassinations of Iranian nuclear scientists. What distinguishes the Abu Qasim case from the Mossad precedent is the proximity and intimacy of the operational environment. Mossad operations in Beirut, Dubai, or Tehran involved operating in foreign countries with no pre-existing intelligence infrastructure. The PoK operation involved operating in territory that sits directly across the LoC from Indian military positions, territory where cross-border intelligence flows have existed for decades in both directions. The geographic proximity potentially enabled human intelligence collection methods, local asset recruitment, and exfiltration routes that a more distant operational theater would not provide. This proximity advantage does not make the operation less impressive; it makes it more interesting analytically, because it suggests a model of targeted killing that depends on geographic adjacency rather than long-range operational reach.

The killing also raises questions about the campaign’s target-selection criteria and prioritization methodology. Not every LeT operative who poses a threat to Indian security has been targeted. The campaign appears to select targets based on a combination of factors: direct involvement in specific attacks against Indian civilians or military personnel, seniority within the organizational hierarchy, operational significance (the degree to which the target’s elimination would degrade the organization’s capability), and accessibility (whether the target can be reached by available operational methods). Ahmad scored highly on all four criteria: he was directly implicated in the Dhangri massacre, he held a senior regional command position, his elimination would degrade LeT’s Poonch-Rajouri pipeline, and his relocation from Muridke to Rawalakot made him more accessible than he had been at the fortified headquarters. The convergence of high scores across all four dimensions may explain the speed of the Dhangri-to-Rawalakot chain: Ahmad was not merely a target of opportunity but a priority target whose elimination checked every box on the selection matrix.

The psychological impact on the surviving LeT leadership is difficult to quantify but analytically important to consider. After four senior commanders were killed in a single year, the organization’s remaining leaders faced a set of security choices that were all operationally costly. They could reduce their visibility by retreating deeper into protected spaces, which would reduce their operational effectiveness. They could vary their routines more aggressively, which would disrupt the habitual patterns that organizational management depends on. They could restrict communications, which would degrade their ability to coordinate operations across the LoC. They could relocate to new areas, which would sever the local relationships and institutional knowledge that effective regional command requires. Every adaptive measure that improves personal security comes at a cost to organizational capability. The campaign forces the organization to choose between the safety of its leaders and the effectiveness of its operations, a dilemma that degrades the organization regardless of which choice is made.

In the final analysis, Abu Qasim’s killing on the floor of al-Qudus mosque in Rawalakot is the case that demonstrates the shadow war’s three defining characteristics most clearly. It demonstrates reach: the ability to operate in PoK, the most heavily controlled territory available to Pakistan’s militant proxies. It demonstrates precision: the attackers knew the mosque, the prayer time, and the position of the target within the congregation. And it demonstrates the attack-to-consequence logic that defines the campaign as a whole: seven people died in Dhangri on New Year’s Day 2023, and nine months later, the man Indian intelligence held responsible died on his knees in a place of worship, in territory that was supposed to protect him, killed by men whose names no one has ever learned.

The Dhangri families who lost Satish Kumar, Deepak Kumar, Pritam Lal, Shishu Pal, Prince Sharma, four-year-old Vihan, and sixteen-year-old Samiksha were not consulted about whether the elimination of Abu Qasim constituted justice for their loss. The village that refused to cremate its dead in January, demanding accountability from the government, received a different kind of accountability in September: not a trial, not a conviction, not a transparent judicial process, but a bullet in a mosque in Pakistan-Occupied Kashmir. Whether this form of accountability is sufficient, whether it deters future attacks or merely perpetuates a cycle of violence, whether it represents strategic wisdom or moral compromise, are questions that the Abu Qasim case concentrates but cannot resolve. What the case does establish, with the clarity of operational evidence, is that the chain from attack to consequence now runs faster, reaches deeper, and operates in territories that were previously considered beyond reach. For the commanders who direct the next Dhangri, the calculus has changed. Whether that change saves lives or merely relocates violence is the question the shadow war’s architects must answer, and the one that the families of Dhangri are still waiting to see resolved.

Frequently Asked Questions

Q: Who was Abu Qasim of Lashkar-e-Taiba?

Abu Qasim was the operational alias of Riyaz Ahmad, a Lashkar-e-Taiba commander originally from the Jammu region of India who crossed into Pakistan-Occupied Kashmir in 1999 and rose through the organization’s ranks to become the senior operative responsible for coordinating militant activities in the Poonch and Rajouri districts of Jammu and Kashmir. He operated from LeT’s Muridke headquarters before relocating to Rawalakot in PoK, and was a close associate of Sajjad Jaat, LeT’s chief commander. Indian intelligence identified him as a principal conspirator behind the Dhangri village terror attack of January 2023.

Q: What happened at the Dhangri village attack in Rajouri?

The Dhangri attack was a twin terror assault on a Hindu-majority village in Rajouri district, Jammu and Kashmir, on January 1 and 2, 2023. On the evening of January 1, two gunmen entered the village and fired on at least three Hindu households, killing four people and injuring others. The following morning, an IED planted by the attackers detonated near the home of one victim, killing two children, a four-year-old boy and a sixteen-year-old girl. A seventh victim later died in hospital. In total, seven civilians were killed and thirteen injured, making it the deadliest attack in the Jammu division in years.

Q: How was Abu Qasim killed inside a mosque in Rawalakot?

Abu Qasim was shot in the head at point-blank range by unidentified gunmen inside al-Qudus mosque in the Rawalakot area of Pakistan-Occupied Kashmir in September 2023. The attackers entered the mosque during prayer time, identified their target among the congregation, shot him, and departed before anyone could react or identify them. No group claimed responsibility for the killing.

Q: How did the attackers know which mosque Abu Qasim attended?

The specific intelligence methods used to identify Abu Qasim’s mosque are not publicly known. However, analytical reconstruction suggests that either locally embedded human assets or cross-LoC intelligence networks provided the information. Rawalakot is a small town where community knowledge of residents’ daily routines, including mosque attendance, is readily available. Surveillance over a period of weeks could have confirmed which mosque he attended, which prayer sessions he was present for, and his position within the congregation.

Q: What is the connection between the Dhangri attack and Abu Qasim’s killing?

Indian intelligence identified Abu Qasim as one of the chief conspirators behind the Dhangri village attack, based on his role as LeT’s commander for the Poonch-Rajouri sector and specific intelligence linking him to the attack planning. Nine months after the Dhangri massacre killed seven civilians, Abu Qasim was shot dead in a PoK mosque. This Dhangri-to-Rawalakot chain represents the fastest major attack-to-elimination sequence documented in the shadow war, suggesting that the Dhangri attack generated an immediate and prioritized intelligence response.

Q: How many people died in the Dhangri attack?

Seven people died in the twin attacks on Dhangri village. Five were killed on January 1, 2023, in the gunfire assault: Satish Kumar (45), Deepak Kumar (23), Pritam Lal (57), Shishu Pal (32), and Prince Sharma (who died of injuries on January 8). Two children, Vihan Sharma (4) and Samiksha Sharma (16), were killed by the IED blast on the morning of January 2. Thirteen additional people were injured across both attacks.

Q: Is Rawalakot in Pakistan-Occupied Kashmir?

Rawalakot is the administrative headquarters of Poonch district in Pakistan-Occupied Kashmir (PoK), also referred to by Pakistan as Azad Jammu and Kashmir. It sits roughly twenty-five kilometers from the Line of Control in the Poonch sector. The town has served for decades as a staging area for militant infiltration into Indian-administered Poonch and Rajouri districts across the LoC.

Q: Was this the first targeted killing inside PoK?

The Abu Qasim killing was the second documented targeted elimination in Pakistan-Occupied Kashmir. The first was the kidnapping and beheading of Khwaja Shahid, the Sunjuwan Army camp attack mastermind, whose headless body was found near the Line of Control. The two PoK killings used dramatically different methods: the Shahid case involved abduction and beheading, while the Abu Qasim case involved a rapid mosque shooting.

Q: What was Abu Qasim’s role in LeT’s financial operations?

Beyond his operational planning responsibilities, Abu Qasim managed financial aspects of Lashkar-e-Taiba’s activities. Terror financing is critical to sustaining militant operations, covering everything from camp maintenance and weapons procurement to family support payments for active militants. His dual role in operational planning and financial management meant his elimination disrupted both the command chain directing attacks and the money flows sustaining LeT’s infrastructure.

Q: What does Abu Qasim’s killing reveal about surveillance in PoK?

The killing demonstrates that intelligence assets or technical surveillance capabilities have penetrated Pakistan-Occupied Kashmir, a controlled territory under Pakistan Army security. The precision of the operation, knowing the specific mosque, the specific prayer session, and the target’s position, indicates weeks of surveillance by locally embedded assets or intelligence sources familiar with the target’s routine. This penetration undermines PoK’s value as a safe haven for militant commanders.

Q: Was Abu Qasim definitely the Dhangri mastermind?

The attribution of the Dhangri attack to Abu Qasim comes from Indian intelligence and security assessments based on his known role as LeT’s commander for the Poonch-Rajouri sector and specific intelligence linking him to the attack planning. Pakistani sources did not confirm this attribution. The attribution should be understood as an intelligence assessment rather than a proven judicial finding, though Abu Qasim’s operational position and command authority in the sector where the attack occurred make the attribution analytically plausible.

Q: How does the Abu Qasim killing compare to the Shahid Latif mosque killing?

Both Abu Qasim and Shahid Latif were killed inside mosques during prayers, confirming a targeting pattern that exploits the predictability of religious routine. The key differences are geographic: Latif was killed in Sialkot, a major city in Punjab province, while Abu Qasim was killed in Rawalakot, a small town in PoK. The PoK location makes the Abu Qasim killing operationally more impressive and strategically more significant, as it demonstrates the ability to operate in a controlled military territory rather than a civilian urban center.

Q: What happened to LeT after Abu Qasim’s death?

Abu Qasim was the fourth senior LeT commander killed by unknown gunmen in 2023 alone. The cumulative impact of these losses forced the organization to adjust its operational practices, tighten security protocols, and replace lost leadership. However, LeT’s institutional depth, supported by its network of madrassas, charitable fronts, and state patronage, means that individual losses, even at the senior operational level, do not destroy the organization. The campaign’s strategic logic targets not individual replacement but cumulative degradation of LeT’s operational layer.

Q: Why are mosques used as targeting locations?

Mosques offer three operational advantages for targeted killings. First, attendance is predictable because prayer times are fixed by astronomical calculation and publicly known. Second, the target’s physical posture during prayer, kneeling, bowing, facing the qibla wall, creates vulnerability. Third, the open-entry nature of mosques means an additional person entering does not trigger alarm. These advantages make mosques the most operationally reliable targeting location available, though targeting a place of worship raises ethical questions that the campaign’s architects have evidently judged acceptable against the operational benefits.

Q: What was the impact on the Rajouri-Poonch security situation?

Abu Qasim’s elimination in September 2023 came during a year of exceptionally high violence in the Rajouri-Poonch sector. The district saw multiple encounters throughout 2023, with eleven Indian soldiers and eight militants killed. Whether Abu Qasim’s death contributed to a decline in subsequent infiltration activity in the sector is difficult to isolate from other factors, including increased Indian security deployments (eighteen additional CRPF companies) and broader seasonal and operational patterns. The network he built, however, would have experienced immediate disruption in command and financial management following his death.

Q: How does the Dhangri-to-Rawalakot chain compare to other attack-to-elimination chains?

The nine-month interval between the Dhangri attack (January 2023) and Abu Qasim’s killing (September 2023) is among the fastest documented attack-to-elimination chains in the shadow war. By comparison, Shahid Latif was killed seven years after the Pathankot airbase attack he masterminded, and Zahoor Mistry was killed years after the IC-814 hijacking in which he participated. The speed of the Dhangri-to-Rawalakot response suggests either that Abu Qasim was already under surveillance or that the Dhangri attack triggered a rapid and prioritized intelligence mobilization.

Q: What does Abu Qasim’s case tell us about the shadow war’s geographic expansion?

The Abu Qasim killing is a key data point in the shadow war’s geographic expansion into Pakistan-Occupied Kashmir. The earliest documented eliminations occurred in Karachi and other major Pakistani cities. The progression into PoK demonstrated that the campaign was not limited to large urban centers where operational anonymity is readily available. Rawalakot is a small town under Pakistan Army security, and executing a targeted killing there required a qualitatively different set of capabilities than operating in Karachi. The geographic expansion into PoK reversed the traditional direction of cross-LoC violence, transforming the border from a one-way infiltration corridor into a two-way operational space.

Q: Could Abu Qasim’s killing have been the work of internal Pakistani rivalries?

Some Pakistani analysts and officials have attributed targeted killings to internal rivalries, sectarian feuds, or criminal disputes rather than Indian intelligence operations. In Abu Qasim’s case, this explanation is weak. He was a senior LeT operative with no reported involvement in sectarian disputes or criminal activity. His killing fits the established pattern of targeted eliminations: unknown gunmen, precision execution, no claim of responsibility, and a target who appeared on India’s most-wanted list. The internal-rivalry hypothesis fails to explain why only India-wanted militants are being killed through this specific modus operandi.

Q: What ethical questions does the Abu Qasim killing raise?

The killing raises several interconnected ethical questions. First, targeted killing itself, executing a specific individual outside a judicial process, is contested under international law. Second, the location of the killing, inside a mosque during prayers, introduces the question of whether places of worship should be treated as protected spaces regardless of who occupies them. Third, the targeting of an individual based on intelligence assessments rather than judicial findings raises questions about evidentiary standards. Fourth, the operation in PoK raises sovereignty questions that intersect with the broader dispute over Kashmir’s political status. These ethical dimensions do not have simple answers, and the Abu Qasim case concentrates all of them into a single event.

Q: How many LeT commanders were killed in 2023?

Abu Qasim was the fourth senior Lashkar-e-Taiba commander killed by unknown gunmen in 2023. The accelerating tempo of eliminations in 2023 marked a significant escalation from previous years. Multiple LeT operatives, along with members of Jaish-e-Mohammed and other organizations, were killed across different Pakistani cities and in PoK during the same year, suggesting a campaign operating at an increasing operational tempo with expanding geographic reach.

Q: What is al-Qudus mosque in Rawalakot?

Al-Qudus mosque is a mosque in the Rawalakot area of Pakistan-Occupied Kashmir where Abu Qasim regularly attended prayers. The mosque is a community institution in a small town, which means its congregation would have been familiar with regular attendees. The targeting of Abu Qasim at this specific mosque demonstrates the intelligence precision of the operation: the attackers had identified not just the target’s city of residence but his specific place of worship and his prayer schedule.