On April 22, 2025, between approximately 1:00 p.m. and 2:45 p.m., armed men entered the Baisaran Valley meadow near Pahalgam in southern Kashmir’s Anantnag district and systematically executed twenty-six civilians, most of them Hindu tourists who had traveled to one of India’s most celebrated mountain destinations for a spring holiday, separating victims by religion before firing at point-blank range with M4 carbines and AK-47 assault rifles in what became the deadliest terror attack on Indian civilians since the 2008 Mumbai massacre and the single event that made Operation Sindoor inevitable.

Pahalgam Attack Minute by Minute Reconstruction - Insight Crunch

Baisaran Valley sits approximately seven kilometers from the town of Pahalgam, accessible only by foot or horseback along a muddy, rocky trail that winds through dense pine forests. The meadow itself stretches roughly 200 meters wide and 800 meters long, ringed by a seven-foot chain-link fence with two gates, one for entry and one for exit, enclosed on all sides by thick alpine woodland that rises toward the Pir Panjal range. Tourists call it Mini Switzerland. On April 22, it became a killing ground whose geography conspired against every attempt to escape or summon help, with the nearest CRPF base four to five kilometers away across terrain that takes forty to forty-five minutes to traverse on foot. What follows is the most granular publicly available reconstruction of those approximately ninety minutes, compiled from eyewitness testimonies, survivor accounts, security force reports, and investigative journalism, with the acknowledgment that exact timings from a chaotic mass-casualty event are inherently approximate and that different accounts conflict on specific sequences. The reconstruction establishes not just what happened, but how the attack’s methodology, specifically the religious identification process that preceded each killing, transformed what might have been absorbed as another security incident into a national trauma that demanded a response India could not calibrate as proportionate.

Baisaran Valley Before the First Shot

Pahalgam had been enjoying a strong spring tourist season. After several days of intermittent rain, April 22 brought clear weather that drew hundreds of visitors to the Baisaran meadow, a broad alpine grassland sometimes described as the heart of Pahalgam’s tourist infrastructure. Families on vacation, honeymooning couples, solo travelers, and groups of friends had made the trek from Pahalgam town, most riding ponies led by local Kashmiri guides along a path that passes through forests before opening into the meadow’s wide expanse. The valley sits at roughly 8,000 feet above sea level, surrounded by pine-covered slopes that cut it off from direct sight of any settlement or security post.

The security environment around Pahalgam on April 22 reflected the broader pattern of reduced militant activity in Kashmir’s tourist corridors. Armed security presence within the Baisaran meadow itself was essentially nonexistent. The closest CRPF deployment was stationed in Pahalgam town, connected to Baisaran only by the single foot trail. J&K Police maintained checkpoints on the main roads leading into Pahalgam, but the meadow’s interior fell within a security gap that assumed the remote location was its own protection. Tourists entered and exited through the fence gates with no security screening, no armed escorts, and no communication infrastructure beyond personal mobile phones, whose signals in the valley’s terrain were unreliable at best.

Several factors converged to create the conditions for maximum casualties. The meadow’s enclosure by fencing funneled movement toward the two gates, creating natural chokepoints. The single access trail meant that reinforcements could not arrive quickly. The altitude and terrain meant helicopter response required specific landing zones and favorable weather. Dense forest surrounding the meadow on all sides provided concealment for both approach and escape. What tourists experienced as Baisaran’s charm, its isolation, its quiet, its feeling of being suspended in a world apart, was precisely what made it a tactically optimal killing ground for attackers who understood the geography and the security gaps it created.

Pahalgam’s economy depends almost entirely on tourism. The town and its surrounding valleys employ thousands of pony operators, hotel workers, tourist guides, handicraft sellers, and tea-stall vendors whose livelihoods rise and fall with each season’s visitor numbers. April marks the beginning of the spring season, when snowmelt opens the trails and tourists begin arriving from across India. For Pahalgam’s working population, the season’s first weeks represent the start of the year’s primary income cycle. Baisaran Valley, as the most popular day-trip destination from Pahalgam town, functions as the economic heart of this tourist ecosystem. On any clear spring day, the meadow hosts hundreds of tourists alongside dozens of local workers, creating a dense, unarmed civilian population in an enclosed space with no security infrastructure and limited communication capability. The attackers chose not just a soft target but the softest possible target within Kashmir’s tourist corridor, a location where maximum civilian density coincided with minimum security presence and maximum geographic isolation.

The tourism-as-normalcy narrative had become central to both the Indian government’s and the J&K administration’s political messaging since the abrogation of Article 370 in August 2019. Rising tourist numbers were cited as evidence that Kashmir was peaceful, developing, and welcoming to outsiders. Pahalgam’s visitor statistics were regularly featured in government presentations about J&K’s transformation. This narrative investment meant that an attack specifically targeting tourists at Pahalgam’s most iconic destination carried a symbolic weight far exceeding its casualty count. It was an assault not just on twenty-six individuals but on the entire political architecture that their presence was supposed to validate.

In the weeks preceding the attack, the broader India-Pakistan atmosphere had been deteriorating. India had secured the extradition from the United States of Tahawwur Rana, a former Pakistani Army officer linked to Lashkar-e-Taiba and convicted for supporting the 2008 Mumbai attacks. Pakistan’s Army chief, General Asim Munir, had delivered a speech invoking the two-nation theory, describing Hindus and Muslims as fundamentally distinct in identity and worldview, language that Indian security analysts would later interpret as ideological preparation for the sectarian targeting methodology the Pahalgam attackers employed. Whether Munir’s rhetoric directly influenced the attack’s planning or merely reflected the environment in which it was conceived remains debated, but the coincidence of timing between the Army chief’s sectarian framing and the attackers’ sectarian methodology was noted by investigators within days of the massacre.

The Approach Through the Forest

The attackers entered the Baisaran Valley through the surrounding pine forests, approaching from positions that exploited the dense woodland as concealment. Based on subsequent investigation by J&K Police and the National Investigation Agency, the assault team consisted of at least three to five individuals, a number that different accounts place at anywhere from two to seven, who were armed with M4 carbines and AK-47 assault rifles and dressed in military-style uniforms, with at least one wearing a Kashmiri pheran, the traditional loose garment that would allow concealment of weapons while moving through areas where locals might observe them. The attackers carried modern communication equipment and, according to eyewitness accounts later confirmed by investigators, mounted body cameras that recorded the massacre as it unfolded.

On the night before the attack, the attackers had been harbored at a hut approximately two kilometers from the Baisaran meadow. Two local Kashmiris, later identified as Parvaiz Ahmad Jothar and Bashir Ahmad Jothar, allegedly provided shelter on April 21, feeding and housing the gunmen before they set out for the meadow the following day. The NIA detained both men in June 2025, and during questioning they disclosed details about the attackers’ preparations, their weapons, and the route they took into the valley. DNA samples collected from the hut were matched against items recovered from the terrorists later killed in Operation Mahadev, confirming the shelter location.

The lead attacker was subsequently identified as Hashim Moosa, known by the alias Suleman Shah or Faizal Jatt, a former para-commando in Pakistan’s Special Service Group who had crossed into Indian-administered Kashmir sometime in 2023 and had been linked to at least six previous terror attacks in Jammu and Kashmir, including a deadly October 2024 assault in Ganderbal that killed seven people and another in Baramulla where four security personnel died. His military training and operational experience made him the most capable tactician among the group, and investigators believe his SSG background shaped the attack’s tactical planning, including the use of the meadow’s geography to channel victims and the coordinated positioning of gunmen at both the entry and exit gates.

J&K Police subsequently released sketches and identities of four attackers: Ali Bhai alias Talha (Pakistani national), Asif Fauji (Pakistani national), Adil Hussain Thoker (resident of Anantnag), and Ahsan (resident of Pulwama). All four were linked to Lashkar-e-Taiba. At least two were confirmed foreign nationals who had infiltrated from Pakistan, and police established connections between the attackers and previous militancy-related incidents in the Poonch region.

The composition of the attack team reflected a deliberate organizational design. Pakistani nationals provided the core tactical capability, particularly Hashim Moosa’s SSG-trained combat skills, while local Kashmiri members contributed terrain knowledge, linguistic fluency in Kashmiri (distinct from the Punjabi and Urdu spoken by the Pakistani infiltrators), and logistical connections that enabled shelter, food, and movement through areas where outsiders would attract attention. This hybrid structure mirrors the model that LeT and ISI have employed in Kashmir for decades, pairing foreign fighters with local sympathizers to produce cells that combine external capability with indigenous cover.

The infiltration route that brought the Pakistani members of the cell into Indian-administered Kashmir remains a subject of intelligence investigation, but the broader pattern of cross-border infiltration through the Poonch-Rajouri sector and along the mountainous stretches of the Line of Control provides the most likely pathway. Hashim Moosa’s presence in Kashmir since 2023 and his involvement in at least six prior attacks indicated that the infiltration and sustainment infrastructure supporting foreign fighters remained operational despite India’s significant investment in border fencing, surveillance technology, and counter-infiltration operations. The fact that a former SSG commando could operate in Kashmir for two years, conduct multiple attacks, and maintain operational freedom sufficient to plan and execute a mass-casualty event at a major tourist site suggests that the support network within Kashmir, the overground workers, shelter providers, and logistical facilitators who enable foreign fighters to survive and operate, remained more robust than Indian security assessments had publicly acknowledged.

First Contact at the Exit Gate

At approximately 1:00 p.m. on April 22, the first shots were fired near the Baisaran meadow’s exit gate. The timing was deliberate. Midday is when the meadow reaches peak occupancy, tourists having completed the morning trek from Pahalgam town and settled into the valley for picnics, pony rides, and photography. By early afternoon, several hundred people were distributed across the meadow, many sitting on the grass with families, eating packed lunches, or walking along the perimeter paths.

The initial gunfire near the exit gate served a tactical function beyond simply beginning the killing. By attacking at the exit, the gunmen blocked the most intuitive escape route, the path back toward Pahalgam town, and created a herding effect. Tourists who heard shots and instinctively moved toward what they perceived as the way out found themselves running toward the gunfire. Those who turned and fled in the opposite direction were channeled toward the entry gate, where additional attackers were positioned. The meadow’s chain-link fence, designed to keep livestock from straying, became a containment barrier that prevented escape into the surrounding forest from most points along its perimeter.

Witnesses described the initial seconds as surreal. The sound of automatic weapons fire in an alpine meadow, a place associated exclusively with beauty and recreation, did not immediately register as real for many tourists. Several survivors reported a gap of several seconds between hearing the first shots and understanding that an attack was underway. During those seconds, some tourists remained seated. Others stood to look toward the sound. A few began to run. The attackers, moving with what multiple witnesses described as methodical calm rather than frantic urgency, used this interval of confusion to close distance to their nearest targets.

The acoustic properties of the meadow amplified the disorientation. Surrounded by forested hillsides, the valley creates an echo chamber that makes it difficult to determine the direction of gunfire. Survivors reported hearing shots that seemed to come simultaneously from multiple directions, even when only one or two gunmen were firing, because the echoes off the surrounding slopes multiplied each report. This acoustic confusion compounded the difficulty of choosing an escape direction, as tourists could not reliably determine which areas of the meadow were safe and which were under fire.

Several families described a horrifying sequence in which they initially moved toward what they believed was the source of help, only to realize they were approaching gunmen. The attackers’ military-style uniforms were a deliberate element of the deception. In Kashmir, where army and paramilitary patrols are a daily presence, camouflage uniforms are associated with protection rather than threat. Tourists who spotted armed men in military dress instinctively moved toward them, expecting rescue. This inversion of the trust normally associated with uniformed personnel added a psychological cruelty to the attack that survivors described as among the most disorienting elements of their experience.

Pony operators and local guides, who knew the meadow’s terrain intimately, reacted more quickly than most tourists. Several guides immediately recognized the sound of automatic weapons fire and began directing their groups toward the edges of the meadow where the fence could potentially be breached or where small paths led into the surrounding forest. At least one guide positioned himself between his group and the approaching gunmen, creating a human shield that gave the tourists behind him seconds to reach cover. The guides’ speed of reaction reflected their familiarity with the security environment of Kashmir, where awareness of potential violence is an occupational reality that tourists from other parts of India do not share.

Shubham Dwivedi, a businessman from Kanpur who was visiting Kashmir on a family holiday and had planned to return home the following day, was among the first victims. He was sitting with his wife Eshanaay when a gunman approached from behind and asked a question that would be repeated dozens of times across the next ninety minutes: “Are you a Hindu or a Muslim?” Eshanaay, taken aback, answered that they were Hindus. The gunman shot Shubham point-blank in the head. When Eshanaay, in shock, pleaded to be killed as well, the attacker refused, telling her she was being spared so she could convey the message to Prime Minister Narendra Modi as a witness.

The Identification Process

What distinguished the Pahalgam massacre from virtually every other terror attack in Kashmir’s modern history was the systematic, individual-level process of religious identification that the attackers conducted before each killing. This was not indiscriminate fire into a crowd. It was targeted, deliberate, and sustained execution preceded by interrogation of each victim’s faith.

The identification process took multiple forms. Attackers approached individuals and groups and demanded they recite the kalma, the Islamic declaration of faith, a verse that practicing Muslims would know but Hindus, Christians, Sikhs, and members of other faiths typically would not. Those who could recite it were told to move aside. Those who could not were shot. In cases where the recitation test was inconclusive or where attackers doubted the response, they escalated to physical verification. Hindu men were forced to remove their trousers so attackers could check for the absence of circumcision, a bodily marker that distinguishes Muslim males (who practice circumcision) from Hindu males (who generally do not). Out of the twenty-six dead, approximately twenty were found with their trousers unzipped or pulled down, a forensic detail that corroborated the eyewitness accounts of the identification methodology.

Several victim accounts illustrate the process’s horrifying granularity. Indian Air Force Corporal Hilyang, from Arunachal Pradesh in northeastern India, was a newlywed on honeymoon with his wife. The attackers approached, asked about his religion, and stripped him at gunpoint. Upon discovering his IAF identity card and confirming his non-Muslim status, they shot him dead. Hilyang had been nearing a transfer from Kashmir to Dibrugarh. He was on leave, visiting the valley one last time before departing.

Sushil Nathaniel, a regional manager for the Life Insurance Corporation from Indore, had come to Pahalgam on vacation with his wife and two children. Before being shot, he was demanded to recite the kalma. When Nathaniel identified himself as a Christian, he was killed immediately. His case established that the targeting was not exclusively anti-Hindu but anti-non-Muslim, a sectarian framework that treated all non-Muslim identities as equally deserving of death.

Intelligence Bureau officer Manish Ranjan had traveled to Kashmir on a government leave travel concession trip with his wife and two children when the attack began. Ranjan was among those killed, his professional identity as an IB officer unknown to the attackers, who selected him based solely on his religion. His death added a layer of institutional grief to the national response.

Lieutenant Vinay Narwal of the Indian Navy, from Haryana, had married his wife Himanshi just six days before the attack. The couple had come to Pahalgam for their honeymoon. The image of Himanshi Narwal sitting in shock beside her husband’s lifeless body became one of the most widely circulated photographs from the massacre, a visual that etched itself into Indian public consciousness as a symbol of the attack’s cruelty. Witnesses reported that the attackers approached the couple while they were eating bhelpuri, a snack, asked about Vinay’s religion, and shot him after confirming he was Hindu.

Shailesh Kalathiya, a State Bank of India employee from Gujarat, was killed on the day before what would have been his forty-fourth birthday. His wife later recounted how the attacker laughed as Shailesh bled out in front of her and their children. A sixty-eight-year-old man, the oldest victim, was seen attempting to flee before attackers chased him down and shot him despite his reported pleas for mercy.

The one Muslim victim was Syed Adil Hussain Shah, a local pony-ride operator and tourist guide who attempted to intervene and protect tourists. Shah’s cousin, Nazakat Ahmad Ali Shah, also a guide and trader in woollen clothes, managed to save eleven people, including the daughter of a BJP political leader. Nazakat first carried two children to the relative safety of Pahalgam town, then returned to escort the remaining members of the group to safety through terrain he knew intimately as a local resident.

The attackers’ decision to spare Muslim tourists and local Kashmiri guides was not incidental. It was integral to the operation’s logic. By releasing some survivors, specifically choosing Hindu women as witnesses, the attackers ensured the attack’s sectarian character would be communicated directly to the Indian government and public, maximizing its emotional and political impact. They were not simply killing. They were staging an act of sectarian theater designed to provoke a specific response.

Movement Through the Meadow

After the initial killings near the gates, the attackers moved through the meadow in a pattern that witnesses described as methodical rather than random. The gunmen progressed across the 200-meter-wide, 800-meter-long space, approaching groups of tourists clustered on the grass, at tea stalls, or near pony-ride areas, conducting the identification process with each group, and killing those identified as non-Muslim.

At one point during the attack, an eyewitness reported that the attackers paused to take selfies with their weapons against the backdrop of the meadow and the surrounding mountains. They also recorded portions of the massacre using body-mounted cameras. Security sources told reporters that this footage was captured by LeT operatives and transmitted to handlers, presumably in Pakistan, for propaganda purposes, although the footage was never publicly released. The body cameras and selfies indicated that the attackers operated with the confidence of men who believed they had sufficient time to complete their operation and that no security response would arrive quickly enough to interrupt them.

The meadow’s geography transformed what might have been a chaotic firefight into a sustained execution. With the fence blocking lateral escape, the two gates either occupied by gunmen or already sites of carnage, and the surrounding forest accessible only by scaling or breaching the fence at points far from any clear path, most tourists were trapped within the enclosure. Some hid behind rocks or in shallow depressions in the terrain. Others pressed themselves against the ground and played dead. Families separated in the panic, parents losing sight of children as the crowd fragmented into dozens of small groups running in different directions without clear exits.

The attackers’ military-style uniforms created an additional layer of confusion. In a region where armed forces personnel are a regular presence, some tourists initially approached the gunmen believing them to be security forces who might provide protection. This confusion proved fatal in at least several documented cases, where tourists ran toward the attackers seeking help and were shot after being identified as non-Muslim.

What is particularly striking about the timeline is its duration. The attack was not a thirty-second burst of violence. It lasted approximately ninety minutes, from the first shots at roughly 1:00 p.m. to the attackers’ withdrawal into the forest sometime after 2:30 p.m. Ninety minutes is an eternity in tactical terms. It is enough time for an organized security response to deploy, assess, and engage. That no armed response reached the meadow during the killing itself is the starkest evidence of the security gap that the attackers exploited and that Indian security planners subsequently scrambled to close.

The pattern of the killing reveals training and coordination rather than frenzied violence. Witnesses described the attackers communicating with each other, calling out to confirm targets, and maintaining awareness of each other’s positions within the meadow. The lead attacker, later identified as the SSG-trained Hashim Moosa, appeared to direct the others, indicating targets and controlling the pace of the group’s movement through the space. This coordination is consistent with a rehearsed plan rather than an improvised attack, suggesting the group had discussed and possibly physically reconnoitered the meadow’s layout before April 22. The overnight stay at the hut two kilometers away would have provided an opportunity for final planning, including assignment of positions at the entry and exit gates and agreement on the identification methodology.

The body camera footage, while never released, represents one of the most consequential pieces of unreleased evidence in the attack’s aftermath. Security sources have indicated that the footage was transmitted to handlers, likely in Pakistan, using the attackers’ satellite phone. If released, it would provide the most granular record available of the attack’s minute-by-minute progression. Its suppression, following TRF’s retraction of responsibility, suggests that LeT’s leadership concluded the footage was too incriminating to distribute as propaganda, as it would have provided visual evidence of the religious identification process that TRF was attempting to deny. For investigators, the existence of the footage confirms that the attack was planned with a propaganda dimension from the outset, one that was abandoned only when the international backlash exceeded what the organization’s deniability architecture could absorb.

Tea stalls near the meadow’s center, where vendors served kahwa and snacks to visiting tourists, became sites of particular horror. Tourists gathered at these stalls were approached in groups, sorted by religion, and those identified as non-Muslim were executed while others watched. The vendors themselves, local Kashmiri Muslims, were generally spared, consistent with the attack’s targeting methodology, but several were traumatized by witnessing executions of their customers at close range. One tea-stall operator later described to journalists how an attacker had asked a family seated at his stall to identify their religion, then shot the father in front of his wife and children while the operator stood paralyzed behind his counter.

Escape, Survival, and the Local Response

While the attackers conducted their systematic killing, some tourists managed to escape through a combination of luck, quick thinking, and the actions of local Kashmiri civilians who risked their lives to protect them.

Nazakat Ahmad Ali Shah’s rescue of eleven tourists represented the single most consequential act of civilian bravery during the attack. Operating with local knowledge of the terrain, trails, and hiding spots that no outsider would have possessed, Nazakat navigated the group through forest paths toward Pahalgam town, carrying two children on the initial trip before returning for the remaining group members. His actions, and his cousin Adil’s decision to intervene directly, which cost Adil his life, became central to the post-attack narrative of Kashmiri solidarity with the victims. For many Indian commentators, Nazakat’s story was proof that the attackers’ sectarian framework did not reflect the values of ordinary Kashmiris.

Other local pony operators and guides played critical roles in alerting security forces. The first notification to the CRPF commanding officer came from pony operators who had fled the meadow, reaching the CRPF base in Pahalgam town and reporting the gunfire. This informal chain of communication, local civilian to military officer, turned out to be faster than the formal alert system, as the first phone call to the J&K Police control room did not arrive until approximately 2:45 p.m., roughly ninety minutes after the shooting began. The delay was attributable to the valley’s unreliable mobile signal coverage and the fact that many tourists who attempted to call for help found their phones without service.

Survivors later recounted the psychological dimension of the escape. Families who had been separated during the initial panic spent hours searching for spouses, children, and elderly relatives. Several groups hid in the forest surrounding the meadow for hours after the attackers withdrew, unsure whether additional gunmen remained in the area. The trek back to Pahalgam town, normally a leisurely forty-five-minute walk, became a traumatic forced march for injured survivors and families carrying wounded members through the rocky, muddy trail.

The local response extended beyond individual acts of heroism. Protests erupted across Muslim-majority areas of Kashmir, including Srinagar, Pulwama, Shopian, Pahalgam, Anantnag, and Baramulla. Demonstrators expressed grief and anger, calling the attack a blow to Kashmiriyat, the centuries-old tradition of Kashmiri composite identity that transcends religious boundaries. Shops and businesses shut down in solidarity. On April 24, an all-party meeting in Srinagar condemned the attack unanimously. On April 25, Mirwaiz Umar Farooq, in his Friday sermon at Srinagar’s Jamia Masjid, declared that Kashmiris stood shoulder to shoulder with the victims. A minute of silence preceded prayers in memory of the dead.

The response from Kashmiri civil society organizations was equally unequivocal. Statements from trade bodies, bar associations, and student groups condemned the massacre and rejected any attempt to frame it as resistance against Indian rule. For many Kashmiris, the attack represented a double violation: an assault on innocent tourists and an assault on the Kashmiri tradition of hospitality that had sustained the valley’s identity for centuries. The pony operators and tourist guides who witnessed the killing bore a particular burden, as their livelihoods depended on the very tourist traffic that the attackers had targeted. Several guides who had led tourists into the meadow that morning spent the days following the attack searching for families they had accompanied, attempting to account for every member of groups they had been responsible for.

Hospital records from Pahalgam and Anantnag document the medical response to the massacre. Injured survivors, many with gunshot wounds to the torso and limbs, were transported by whatever means available: carried on ponies, loaded into private vehicles, and eventually airlifted by military helicopters. The hospitals nearest to Pahalgam were small district facilities not equipped for mass-casualty events, and several seriously wounded patients required transfer to Srinagar’s larger hospitals, a journey of approximately ninety kilometers along mountain roads. The dead were identified over the following days as families and authorities worked to match victims with missing-person reports filed from across India.

The breadth and speed of the Kashmiri response was significant because it preempted what might otherwise have become a communal narrative pitting Kashmiri Muslims against Indian tourists. The attackers had intended to drive a wedge between communities. The Kashmiri public’s response, from street protests to the J&K Legislative Assembly’s special session on April 28 that passed a three-page condemnation resolution, demonstrated that the wedge did not take hold where the attack occurred. It took hold, instead, at the national level, where the massacre’s sectarian character fueled a demand for retribution that no diplomatic measure could satisfy.

Security Forces Race to Baisaran

The CRPF’s response timeline to the Pahalgam attack is both a record of individual courage under impossible constraints and a case study in the consequences of security architecture that failed to account for Baisaran Valley’s vulnerability. Twenty-five CRPF personnel, the initial response team, reached the meadow at approximately 2:30 p.m., having covered the four-to-five-kilometer trail from their base in Pahalgam town in under forty minutes through difficult terrain while carrying weapons and equipment. They were followed by a J&K Police team, and efforts were subsequently coordinated between the two forces.

By the time security forces reached the meadow, the attackers had already withdrawn into the dense forest surrounding Baisaran. The forest’s canopy, combined with the attackers’ knowledge of the terrain, which their overnight stay at the nearby hut suggests they had reconnoitered, made immediate pursuit exceptionally difficult. The attackers had exploited the same geographic isolation that attracted tourists, using the meadow’s remoteness as a tactical buffer that guaranteed them approximately ninety minutes of uninterrupted access to hundreds of unarmed civilians.

The Indian government launched Operation Mahadev on the day of the attack, an extensive search-and-cordon operation involving CRPF, J&K Police, and the Indian Army. The operational directive was clear: do not let the attackers escape to Pakistan. Given that Baisaran Valley sits approximately 220 kilometers from the Line of Control, the attackers faced a long and dangerous journey if their plan was to flee across the border. Security forces established a grid across southern Kashmir, supplemented by aerial surveillance using helicopters and drones, and began systematically combing the forests and mountains between Pahalgam and the LoC.

In scale, Operation Mahadev exceeded any previous counter-terrorism search operation in Kashmir’s recent history. Multiple battalions of the Indian Army and paramilitary forces were deployed to establish an outer cordon that prevented the attackers from leaving southern Kashmir, while specialized counter-terrorism teams conducted inner searches through the forests, ridgelines, and valleys where the gunmen might seek shelter. The operation involved coordination among multiple security agencies, each responsible for a defined sector of the search grid, with daily intelligence briefings and drone flyovers updating the search parameters. Local informant networks were activated, and community-level intelligence gathering supplemented the technological surveillance.

Operationally, the challenge facing Operation Mahadev was substantial. Southern Kashmir’s forests, which extend from Pahalgam through Anantnag toward the higher ranges, cover thousands of square kilometers of terrain that provides natural concealment. The attackers, at least one of whom had operated in the region since 2023, possessed local knowledge that allowed them to avoid established paths and move through areas that regular patrols rarely reached. Seasonal shepherds and nomadic Gujjar communities who use the higher forests during summer months complicated the search, as security forces had to distinguish between legitimate forest activity and fugitive movement.

The hunt for the attackers consumed three months. A breakthrough came when a Huawei satellite phone, its IMEI number partially identified from intelligence databases, was tracked pinging the Inmarsat-4 F1 satellite. The phone had been under monitoring since April 22, and security agencies tracked its intermittent signals through the forests of southern Kashmir. On July 26, the device made an unusual call that allowed analysts to narrow the attackers’ location to a four-square-kilometer section of Harwan forest near Mahadev Ridge in the Dachigam area.

On July 28, 2025, a joint operation brought the hunt to its conclusion. At 8:00 a.m., a drone was deployed to gather visual confirmation of the terrorists’ position. Rashtriya Rifles and Para Special Forces personnel ascended Mahadev Hill and took up positions. In the subsequent engagement, security forces killed three of the attackers, identified as Suleman Shah (Hashim Moosa), Abu Hamza (Hamza Afghani), and Yasir (also known as Jibran). All three were confirmed linked to Pakistan-based terror networks, with Suleman Shah’s identity as a former SSG para-commando confirmed through biometric and intelligence records.

Key Figures Behind the Attack

Understanding the Pahalgam massacre requires mapping its organizational architecture, from the gunmen who pulled the triggers to the leadership structure that planned, funded, and directed the operation from across the border.

The Gunmen

Hashim Moosa, alias Suleman Shah or Faizal Jatt, was the tactical leader. A former member of Pakistan’s Special Service Group, he had infiltrated Indian-administered Kashmir around 2023 and established himself as one of the most operationally active terrorists in the region. Before Pahalgam, he had been linked to at least six terror attacks, including the October 2024 Ganderbal attack that killed seven people and a separate assault in Baramulla that claimed four security personnel. His SSG training set him apart from typical LeT foot soldiers. He understood tactical planning, terrain exploitation, fields of fire, and withdrawal procedures in ways that reflected professional military instruction rather than madrassa-based radicalization alone.

Ali Bhai (alias Talha) and Asif Fauji were the two confirmed Pakistani nationals among the attackers. Both were linked to LeT and had connections to previous militancy-related incidents in the Poonch region. The involvement of Pakistani nationals was critical to the post-attack diplomatic response, as it provided India with direct evidence of cross-border infiltration and Pakistani state complicity.

Adil Hussain Thoker (Anantnag resident) and Ahsan (Pulwama resident) were the local Kashmiri members of the cell. Their inclusion served the operational purpose of providing local knowledge, terrain familiarity, linguistic capability, and logistical support, but their involvement also fed into The Resistance Front’s narrative of indigenous Kashmiri resistance, a narrative that the group’s organizational structure was specifically designed to project.

The Masterminds

Sheikh Sajjad Gul, alias Sajad Ahmad Sheikh, was identified by investigators as the mastermind of the Pahalgam attack. Gul is the founder of The Resistance Front, the organizational front that claimed and then denied responsibility for the massacre. Based in the cantonment town of Rawalpindi, Pakistan, Gul had been designated a terrorist by the NIA in April 2022, with a bounty of ten lakh rupees on his head. His background defied the stereotype of the cave-dwelling radical. He was educated in Srinagar, completed an MBA in Bangalore, and later took a lab technician course in Kerala. After returning to Kashmir, he opened a diagnostic laboratory while simultaneously providing logistical support to LeT’s operational infrastructure.

Pakistan’s Inter-Services Intelligence, the ISI, reportedly used Gul as a local Kashmiri face for the predominantly Punjabi Lashkar-e-Taiba, a strategic choice that served the deniability architecture Pakistan had been constructing since the abrogation of Article 370 in August 2019. By placing a Kashmiri with professional credentials at the head of a group labeled The Resistance Front rather than Lashkar-e-Taiba, the ISI created a layer of separation between the attack and its actual organizational origin. Investigators identified communication chains linking Gul to LeT’s senior leadership, including connections to Hafiz Saeed’s deputy, Saifullah Khalid Kasuri.

The broader organizational chart behind the attack connected to Pakistan’s most senior designated terrorists. Security agencies identified LeT chief Hafiz Saeed and his deputy Kasuri as the two most senior figures in the attack’s chain of command, both operating from Pakistan. The NIA’s investigation traced funding for TRF operations through international channels, uncovering approximately nine lakh rupees routed through a Malaysian resident named Yasir Hayat, who had connections to Sajid Mir’s network. Mir, one of LeT’s most wanted operatives, was suspected of planning the 2008 Mumbai attacks. NIA analysis of 463 phone calls connected the Pahalgam attack’s financing to anti-India groups operating from Pakistan, Malaysia, and Gulf states.

Investigators following the financial trail uncovered a sophisticated transnational funding network. Funds moved through multiple jurisdictions, using legitimate financial channels, hawala networks, and encrypted digital communications to obscure the origin and destination of money supporting the Pahalgam cell. The Malaysian connection through Yasir Hayat represented one node in a broader LeT financing architecture that extended across Southeast Asia and the Gulf states, regions where Kashmiri and Pakistani diaspora communities provided both witting and unwitting channels for terror financing. NIA raids in Srinagar and Handwara recovered digital evidence, including mobile data, social media communications, bank transaction records, and call logs, that documented the funding chain from its international origins to the local operatives who provided food, shelter, weapons storage, and transportation to the attackers.

Beyond the funding chain, NIA expanded its investigation to target the broader support infrastructure that had enabled the attack. Beyond the Jothar brothers who sheltered the attackers, NIA arrested Shafat Maqbool Wani in Handwara under the Unlawful Activities (Prevention) Act in July 2025. Wani was believed to have received money from TRF to support terrorism. In September 2025, Srinagar Police arrested Mohammad Yousuf Kataria, a twenty-six-year-old seasonal teacher from Kulgam district, for providing logistical support to the terrorists killed in Operation Mahadev. Following the attack, hundreds of former overground workers and ex-militants across Kashmir were interrogated, J&K Police announced a bounty of twenty lakh rupees for information leading to the identification, arrest, or elimination of each attacker, and property belonging to Sajjad Gul’s family in Srinagar, a three-storey residential house valued at two crore rupees, was attached by police as part of asset-seizure operations targeting terror-linked wealth.

The Claim, the Retraction, and the Hacking Lie

The Resistance Front’s handling of its responsibility claim for the Pahalgam attack is perhaps the most revealing episode in the entire post-attack timeline, a masterclass in failed deniability that exposed the very architecture it was designed to conceal.

On the day of the attack, April 22, TRF claimed responsibility through its social media channels. The claim was specific: TRF framed the attack as an act of resistance against non-local settlement in Kashmir resulting from the abolition of the region’s special status. The claim was accompanied by a photograph of the attack site, a detail that demonstrated firsthand access to the massacre’s location and timing. The following day, April 23, TRF repeated the claim.

Then, on April 26, four days after the massacre, TRF reversed course. In a statement posted on its social media handles, the group declared that it “unequivocally” denied involvement in the Pahalgam incident. It claimed that any attribution of the attack to TRF was false. Regarding its earlier claim, TRF stated that “shortly after the attack in Pahalgam, a brief and unauthorized message was posted from one of our digital platforms” and that after an “internal audit,” they had reason to believe the post was the result of a “coordinated cyber intrusion,” which they blamed on Indian intelligence agencies.

Indian security officials dismissed the retraction immediately. Sources within the agencies described the hacking claim as absurd, pointing to the specificity of the initial claim, the accompanying photograph, and the fact that TRF had repeated the claim on a second consecutive day. The retraction’s timing, coming four days later rather than immediately, suggested organizational deliberation rather than the discovery of a genuine security breach. If TRF’s social media had truly been hacked, the group would have been expected to issue a correction within hours, not four days.

The more compelling explanation, one supported by the subsequent UNSC Monitoring Team report and the U.S. State Department’s designation of TRF as a Foreign Terrorist Organization in July 2025, is that the retraction was strategic rather than genuine. TRF’s Lashkar-e-Taiba parent organization, operating under the direction of the ISI, had not anticipated the severity of the international backlash. The attack’s sectarian character, the targeting of tourists by religion in a recreational setting, generated a global condemnation that exceeded what the organization’s deniability architecture was designed to absorb. The retraction was an attempt to re-establish plausible deniability after the attack’s scale made the initial claim a liability rather than an asset.

At the United Nations, the 36th Analytical Support and Sanctions Monitoring Team report explicitly addressed the claim-retraction episode, marking the first mention of LeT in a UNSC monitoring report since 2019. The report documented the sequence: claim on April 22, repeated claim on April 23, retraction on April 26, no subsequent communication from TRF, and no claim by any other group. Two UN member states cited in the report affirmed that the attack could not have been executed without support from Pakistan-based Lashkar-e-Taiba. One state categorically stated that “TRF is synonymous with LeT.” Pakistan attempted to argue that LeT was “defunct,” but the evidentiary weight assembled by the monitoring team rendered that position untenable.

The U.S. designation of TRF as a Foreign Terrorist Organization on July 17, 2025, explicitly cited the Pahalgam attack as the basis for the action. The State Department described TRF as “a front and proxy for the Pakistan-based Lashkar-e-Taiba” and noted that TRF had “claimed responsibility for the April 22, 2025 Pahalgam attack.” The designation treated TRF’s retraction as irrelevant, a legal and diplomatic judgment that the initial claim, corroborated by intelligence and forensic evidence, was the truthful account and that the retraction was disinformation. The statement highlighted that TRF had claimed multiple other attacks against Indian security forces, including incidents in 2024, and characterized the designation as reflecting Washington’s commitment to countering terrorism and pursuing justice for the Pahalgam victims.

TRF issued a statement rejecting the U.S. designation, calling it politically motivated and influenced by India. Hours earlier, Pakistan’s Deputy Prime Minister Ishaq Dar had publicly criticized the American decision. The coordinated timing of Pakistan’s diplomatic objection and TRF’s rejection reinforced the intelligence assessment that TRF operated under ISI direction, as TRF’s media strategy appeared synchronized with Islamabad’s diplomatic messaging. Intelligence sources continued to identify TRF as a front for Lashkar-e-Taiba, and the U.S. designation effectively ended the viability of TRF’s indigenous-resistance narrative in any international forum.

The India-Pakistan diplomatic contest at the United Nations over TRF’s designation illustrated the broader stakes of the claim-retraction episode. Pakistan had initially succeeded in removing references to TRF from the UNSC’s press statement condemning the Pahalgam attack, achieved through backdoor lobbying that produced a statement acknowledging the “reprehensible act of terrorism” without naming the perpetrators. Indian diplomats viewed this as a tactical loss but a strategic opportunity, using the subsequent Monitoring Team process to introduce detailed evidence of TRF’s LeT parentage that the initial press statement had omitted. An Indian delegation met senior officials from the UN Office of Counter-Terrorism and the Counter-Terrorism Committee Executive Directorate in New York on May 14, presenting evidence that TRF should be listed as a UN-designated terrorist organization. The Monitoring Team report’s explicit naming of TRF and LeT reversed Pakistan’s initial diplomatic success and established, in the formal record of the UNSC’s most authoritative analytical body, that the Pahalgam attack was carried out by a Pakistani proxy group.

Consequences and the Road to Operation Sindoor

The Pahalgam massacre set in motion a chain of consequences that escalated over fourteen days from diplomatic suspension to full-scale missile strikes on Pakistani territory. Understanding that chain requires recognizing that Pahalgam was not received in New Delhi as an isolated incident. It was received as the culmination of a twenty-six-year series of attacks, from IC-814 through the 2001 Parliament attack, the 2008 Mumbai massacre, the 2016 Uri assault, the 2019 Pulwama bombing, and the shadow war’s escalating tempo, that had accumulated into a burden of unresponded-to provocation that Pahalgam’s sectarian character made politically impossible to absorb.

Prime Minister Narendra Modi cut short a visit to Saudi Arabia upon receiving news of the attack. His initial public statement signaled that those responsible would face consequences, a formulation that, in the context of India’s post-Pulwama and post-Balakot escalation trajectory, was understood both domestically and internationally as a signal that military action was under active consideration.

India’s response followed a fourteen-step escalation ladder. On Day 2, India suspended diplomatic engagement with Pakistan. Day 3 brought the revocation of the Simla Agreement, the 1972 framework that had governed bilateral relations. Day 4 saw property demolitions targeting terror-linked assets. Day 7 brought trade suspension. Day 13 saw India restrict water flows under the Indus Waters Treaty, a move that weaponized a sixty-five-year-old resource-sharing agreement that had survived three wars and decades of bilateral hostility. Each step was a signal and an off-ramp. Each step was ignored by Pakistan. India also rescinded visas for Pakistani nationals present in the country and ordered their departure, a diplomatic measure that signaled the depth of the rupture in bilateral relations.

The escalation ladder’s design revealed a strategic sophistication that analysts noted was qualitatively different from India’s responses to previous attacks. After the 2001 Parliament attack, India mobilized a million soldiers to the border in Operation Parakram but ultimately did not strike. After the 2008 Mumbai attacks, India relied on international pressure and criminal prosecution but took no military action. After the 2016 Uri attack, India conducted surgical strikes across the Line of Control. After the 2019 Pulwama bombing, India conducted the Balakot airstrike. Each successive response was more assertive than the last, and each calibrated to exceed the previous response’s intensity while remaining within a boundary that limited escalation. The post-Pahalgam escalation shattered those boundaries entirely, moving from diplomatic measures to economic warfare to resource weaponization to full-scale missile strikes on sovereign Pakistani territory.

The Indus Waters Treaty suspension was particularly consequential. The 1960 treaty, brokered by the World Bank, had been one of the most durable agreements in South Asian diplomacy, surviving the wars of 1965, 1971, and 1999, the Kargil crisis, the Parliament attack mobilization, the Mumbai attacks, and decades of bilateral hostility. Its suspension signaled that India was prepared to use every available lever of pressure, including water, which Pakistan depends on for its agricultural economy.

On May 7, fifteen days after Pahalgam, India launched Operation Sindoor. In twenty-three minutes, Indian forces struck nine targets across Pakistan using a combination of SCALP cruise missiles, BrahMos missiles, and SPICE precision-guided munitions delivered by Rafale jets, Sukhoi Su-30MKIs, and naval platforms. The strikes targeted JeM and LeT training camps, command centers, and weapons depots. Pakistan retaliated with artillery shelling on Poonch and other Indian border towns, producing civilian casualties on both sides. A ceasefire followed, brokered under international pressure, but the broader conflict timeline had fundamentally altered the India-Pakistan deterrence equation.

The J&K Legislative Assembly held a special session on April 28, six days after the attack, passing a three-page resolution condemning the massacre and endorsing the diplomatic measures taken by the Cabinet Committee on Security. The resolution represented the first time J&K’s elected assembly, which had been reconstituted following the 2019 abrogation of Article 370 and the subsequent elections, formally endorsed retaliatory measures against Pakistan in response to a terror attack on its soil. Chief Minister Omar Abdullah, whose National Conference party had historically maintained a position of dialogue with Pakistan, supported the resolution without reservation, a political shift that reflected the magnitude of public sentiment generated by the attack’s sectarian methodology.

The assembly session itself became a demonstration of the cross-party consensus that Pahalgam had produced. Members from the ruling National Conference, the opposition BJP, and smaller regional parties all spoke in support of the resolution. Two minutes of silence were observed for the victims. The unanimity was significant because Kashmir’s political landscape had been deeply divided on virtually every issue related to India-Pakistan relations, security policy, and the region’s constitutional status. Pahalgam collapsed those divisions, producing a moment of political alignment that would have been unthinkable weeks earlier and that gave the Indian central government domestic political cover for the escalation that culminated in Operation Sindoor.

International reactions arrived swiftly and from unexpected quarters. UN Secretary General Antonio Guterres condemned the attack, stating that violence against civilians was unacceptable under any circumstances. The Taliban, Afghanistan’s ruling authority and itself an Islamist organization, condemned the Pahalgam attack, calling it an act that “undermines efforts to ensure regional security,” a remarkable diplomatic development that underscored how far the massacre’s sectarian targeting methodology fell outside even the norms of groups that routinely employ violence against civilian populations. The Taliban’s condemnation was particularly damaging to Pakistan’s position because it came from an organization that Islamabad had historically supported and that shared the Islamist ideological framework that LeT and TRF claimed to represent.

United States President Donald Trump, Russian President Vladimir Putin, and Israeli Prime Minister Benjamin Netanyahu all expressed solidarity with India. Argentina and several European nations offered condolences. The breadth of international condemnation reflected how the attack’s sectarian methodology, the targeting of tourists by religion at a recreational site, transcended the usual geopolitical divisions that constrain international responses to violence in Kashmir. Countries that had historically maintained neutral or pro-Pakistan positions on Kashmir issues found it impossible to frame the Pahalgam massacre as anything other than what it was: a sectarian atrocity against unarmed civilians.

The Religious Targeting Debate

The central analytical question surrounding the Pahalgam attack is whether the religious identification process described by eyewitnesses, the kalma recitation tests, the circumcision checks, the explicit questioning of victims’ faith, represents a systematic and premeditated targeting methodology or whether the chaos of the attack has been retroactively organized into a more coherent narrative than the actual events warranted.

Evidence strongly supports the premeditated thesis. Multiple independent eyewitness accounts, from survivors who did not communicate with each other before providing testimony, describe the same basic process: approach, question about religion, test (verbal or physical), and execution of those identified as non-Muslim. The demographic pattern of the victims corroborates the testimony. Twenty-five of the twenty-six dead were non-Muslim: Hindus, one Christian, and one Muslim who was killed while attempting to protect tourists rather than as a target of the identification process. If the killing had been indiscriminate, the victim demographics would roughly reflect the meadow’s population, which included significant numbers of Kashmiri Muslim locals serving as guides, pony operators, and tea-stall workers.

The physical evidence adds a forensic dimension. The trousers of approximately twenty victims were found unzipped or pulled down, consistent with the circumcision-check methodology described by witnesses. This detail is difficult to explain through any alternative hypothesis. It is not consistent with random gunfire, looting, or post-mortem disturbance. It is consistent with a systematic process of physical inspection conducted before each killing.

Pakistan’s position, articulated through various official and media channels, has been to characterize the attack as a “false flag operation” staged by Indian intelligence to justify military action. This characterization has gained no international traction. The UNSC monitoring report, the U.S. FTO designation of TRF, and the broad spectrum of international condemnation all treated the attack as a genuine terror assault conducted by Pakistan-linked militants. The false-flag allegation is inconsistent with the volume and consistency of eyewitness testimony, the forensic evidence, the TRF’s initial claim of responsibility, and the subsequent identification and killing of the attackers, whose Pakistani origins and LeT connections were confirmed through biometric and intelligence records.

Christopher Clary, an academic specialist on India-Pakistan crises, has argued that the attack’s methodology, specifically the religious identification process, was the factor that determined the escalation trajectory. An indiscriminate attack, even one with the same casualty count, might have been absorbed within the existing framework of condemnation-followed-by-restraint that had characterized India’s response to Kashmir violence for decades. The sectarian methodology made absorption impossible because it transformed the attack from a security incident into a civilizational assault, a framing that demanded a response calibrated to the offense’s character rather than merely its body count.

Radha Kumar, the author of “Paradise at War” and a specialist on Kashmir’s conflict dynamics, has situated the attack within the longer history of sectarian violence in the valley, noting that while targeted killings of Kashmiri Hindus had occurred in previous decades, the Pahalgam massacre represented an unprecedented escalation in both scale and methodology. Previous attacks on minorities in Kashmir had been carried out in urban environments with quick escapes. Pahalgam was conducted in an enclosed recreational space with a deliberate process of victim selection that took ninety minutes to complete, a duration that indicated planning, confidence, and organizational support rather than opportunistic violence.

Kumar’s historical comparison is instructive. During the early 1990s, the exodus of Kashmiri Pandits from the valley was driven by targeted killings, intimidation, and threats that unfolded over weeks and months, not in a single concentrated massacre. Individual Kashmiri Hindus were killed by militants in targeted operations that, while horrifying, did not involve the systematic identification-and-execution methodology that characterized Pahalgam. The 1990s violence was designed to expel a community over time. Pahalgam was designed to kill as many non-Muslims as possible in a single operation, a qualitative shift in methodology that reflected either a change in organizational objectives or a willingness to absorb consequences that previous generations of militants had avoided.

The broader context of targeted killings of minorities in Kashmir between 2020 and 2025 provides additional evidence of a systematic pattern. In the years preceding Pahalgam, TRF and affiliated groups had carried out targeted killings of Kashmiri Hindus, government employees from outside the region, and migrant laborers, attacks that Indian security agencies described as part of a deliberate strategy to make non-Muslims feel unwelcome in the valley. A schoolteacher was killed in Srinagar. A pharmacist was shot in his shop. A bank guard was targeted for his religion. These individual killings, each producing one or two casualties, established the operational template that Pahalgam scaled up to a mass-casualty event: identify the target by religion, confirm non-Muslim status, and execute.

The disagreement over whether the identification process was real or embellished is, at this point, essentially settled. The convergence of eyewitness testimony, forensic evidence, demographic analysis, intelligence investigation, and international adjudication through the UNSC and U.S. State Department all point to the same conclusion: the Pahalgam attack was a premeditated sectarian massacre in which victims were individually identified by religion and executed on that basis. The attackers did not merely kill non-Muslims. They constructed a process for identifying them, a distinction that reveals the depth of planning and ideological commitment behind the operation.

Pakistan’s position, that the attack was a false flag staged by Indian intelligence, found no traction in any international forum and was contradicted by the physical evidence, the TRF’s own initial claim, and the subsequent identification of the attackers as LeT-linked operatives including a former Pakistani SSG commando. The false-flag narrative served domestic consumption within Pakistan but carried no analytical weight beyond that audience. Indian officials and independent analysts both pointed to the sheer implausibility of staging a mass-casualty attack involving real victims, real weapons, and a ninety-minute killing spree in a remote mountain meadow as a provocation for military action that India was already, by many assessments, preparing for through other means.

Why Pahalgam Changed Everything

The Pahalgam massacre occupies a specific position in the twenty-six-year chain of India-Pakistan escalation that stretches from the IC-814 hijacking in December 1999 to Operation Sindoor in May 2025. It was not the deadliest attack in that chain. Mumbai 2008, with 166 dead, killed far more. It was not the most strategically targeted. The 2001 Parliament attack struck at the symbolic heart of Indian democracy. But Pahalgam was the attack that broke India’s remaining capacity for restraint, and understanding why requires looking beyond casualty counts to the attack’s specific characteristics.

Three factors converged to make Pahalgam the breaking point. First, the sectarian identification methodology transformed the attack’s character. Previous attacks could be framed, however unsatisfactorily, as militant operations against strategic targets (Parliament, military bases, security convoys). Pahalgam was civilians on holiday being selected for execution based on their religion. The framing available to India’s political leadership was not “security incident” but “sectarian massacre,” and that framing demanded a response that matched its gravity.

Second, the location demolished the tourism-equals-normalcy narrative that both the Indian government and the J&K administration had been constructing since the abrogation of Article 370. Pahalgam was supposed to be proof that Kashmir was safe, that development was working, that the security situation had been brought under control. An attack at Pahalgam, at the valley’s most iconic tourist destination, during peak season, against the very tourists whose presence was the evidence of normalcy, destroyed the narrative and demanded its replacement with something harder. Indian security agencies had invested significant resources in protecting tourist routes and promoting Kashmir as a safe destination. The attack demonstrated that even the most promoted corridors contained exploitable vulnerabilities that a determined adversary could identify and weaponize.

The economic dimension of this narrative destruction was immediate and severe. Pahalgam’s tourism economy collapsed in the days following the attack. Hotel bookings were canceled across Kashmir. The Indian government temporarily closed forty-eight of eighty-seven tourist destinations in J&K. Taxi drivers, hotel owners, guides, porters, and handicraft sellers who depended on tourist traffic found their primary income source eliminated overnight. The pony operators of Baisaran Valley, many of whom had been present during the attack and had helped evacuate survivors, faced the paradox of losing their livelihoods precisely because they had witnessed the events that generated international attention. The economic damage extended beyond Pahalgam to the entire Kashmir tourism sector, which represents a significant portion of the region’s formal employment.

Third, the timing placed Pahalgam at the end of a sequence that had already been testing India’s threshold. The shadow war’s accelerating tempo, the Guardian investigation, the US-Canada diplomatic fallout from the Pannun and Nijjar cases, and Pakistan Army chief Munir’s inflammatory rhetoric had created an environment in which each new provocation encountered a lower tolerance for absorption. Pahalgam arrived when the threshold was already near collapse, and its sectarian character pushed it past the point of no return.

The distinction between Pahalgam and previous attacks that India absorbed without full-scale military response is critical to understanding why this particular event broke the pattern. After the 2001 Parliament attack, India mobilized but did not strike, in part because the attackers were killed during the assault and Pakistan’s state involvement was deniable enough for diplomacy to provide an off-ramp. After Mumbai 2008, India channeled its response into international pressure, criminal prosecution, and intelligence cooperation with the United States. After Pulwama 2019, India responded with the Balakot airstrike, a limited single-target operation that signaled willingness to use force but remained within a framework of proportionality. Pahalgam broke the pattern because its sectarian methodology made every previous off-ramp unavailable. A government that absorbed the face-to-face religious identification and execution of its citizens at a tourist resort would have lost its claim to providing security, a political reality that transcended party lines or ideological positions.

Pahalgam reshaped India’s counter-terrorism architecture in ways that extended far beyond the immediate military response. Operation Sindoor established the precedent that missile strikes on Pakistani territory were within India’s response menu. Operation Mahadev demonstrated the capacity for sustained, months-long manhunts in difficult terrain. The Indus Waters suspension weaponized a resource-sharing agreement that had been considered sacrosanct. The comprehensive crackdowns, Operations Amrit, Vajra, and Trident, launched nationwide disruption campaigns against terror networks, funding pipelines, and infiltration channels. Thousands of SIM cards were blocked. Hundreds of suspects were arrested. The post-Pahalgam India was a fundamentally different adversary from the pre-Pahalgam India, and that transformation began in the ninety minutes when armed men walked through an alpine meadow asking tourists what god they prayed to.

Restructuring of Kashmir’s tourist security architecture in the months following the attack was among the most visible and immediate changes. Armed security deployments were established within tourist areas themselves, including at Baisaran Valley and other popular destinations, rather than concentrated in towns and along roads. Communication infrastructure was enhanced to ensure that emergency calls could be made from remote tourist locations. Drone surveillance of high-value tourist corridors was introduced, providing aerial monitoring capability that would have significantly reduced the response time had it been in place on April 22. The J&K Police established dedicated tourist-protection units, and security vetting was introduced for pony operators and guides who provide services in sensitive areas.

The targeted killing campaign that constitutes India’s covert shadow war also accelerated dramatically in the months following Pahalgam. The operational tempo of eliminations in Pakistan increased rather than decreased after both the Pahalgam attack and Operation Sindoor’s ceasefire, suggesting that the attack had generated both new intelligence leads and renewed institutional determination to pursue the campaign’s objectives. Several LeT and Hizbul Mujahideen operatives were killed by unknown gunmen in Pakistani cities during the second half of 2025 and into 2026, a pace that exceeded any previous period in the shadow war’s history.

A black marble memorial now stands on the banks of the Lidder River in Pahalgam, inscribed with the names of all twenty-six victims. It serves as both tribute and reminder. The families who lost husbands, fathers, sons, and brothers on an afternoon that was supposed to be about beauty and recreation continue to carry wounds that no military operation can heal. The tactical and strategic analysis of what Pahalgam triggered must not obscure the human reality that preceded it: twenty-six people who woke up on April 22 expecting nothing more dangerous than a pony ride through a mountain meadow, and who instead encountered men with automatic weapons and a question about their faith that determined whether they would live or die.

Frequently Asked Questions

Q: What happened minute by minute at the Pahalgam attack?

On April 22, 2025, between approximately 1:00 p.m. and 2:45 p.m., armed men entered the Baisaran Valley meadow near Pahalgam and systematically killed twenty-six civilians. The attack began with shots fired near the exit gate, which blocked escape and herded tourists toward the opposite end of the meadow. The attackers then moved through the enclosed meadow, approaching groups of tourists, asking about their religion, demanding recitation of the kalma (Islamic declaration of faith), and in some cases forcing men to remove trousers to check for circumcision. Those identified as non-Muslim were shot at point-blank range with M4 carbines and AK-47s. The attack lasted approximately ninety minutes before the gunmen withdrew into the surrounding forest. The first CRPF response team reached the meadow at approximately 2:30 p.m., by which time the attackers had already completed their killing and begun their retreat.

Q: How long did the Pahalgam attack last?

The attack lasted approximately ninety minutes, from roughly 1:00 p.m. to approximately 2:30-2:45 p.m. on April 22, 2025. This extended duration reflected the attackers’ confidence that no armed security response would reach the remote meadow quickly enough to interrupt the massacre. The nearest CRPF base was four to five kilometers away across difficult terrain that takes forty to forty-five minutes to traverse on foot. The first CRPF response team of twenty-five personnel reached Baisaran at approximately 2:30 p.m., while the first formal phone call to the J&K Police control room was logged at 2:45 p.m., nearly ninety minutes after the first shots.

Q: Did the gunmen really check tourists’ religious identity before shooting?

Multiple independent eyewitness accounts consistently describe a religious identification process. Attackers approached victims and demanded they recite the kalma. Those who could not were identified as non-Muslim and shot. In cases where verbal identification was inconclusive, attackers forced male victims to remove trousers to check for circumcision, which distinguishes Muslim males from Hindu males. Forensic evidence corroborated this testimony: approximately twenty of the twenty-six dead were found with trousers unzipped or pulled down. The victim demographics further support the accounts, as twenty-five of twenty-six victims were non-Muslim, a pattern inconsistent with indiscriminate fire. The weight of eyewitness testimony, forensic evidence, and demographic analysis leaves little room for doubt that the identification process was real and systematic.

Q: How many gunmen carried out the Pahalgam attack?

Different accounts place the number of attackers at between two and seven, with the most consistent estimates citing three to five gunmen. J&K Police released sketches and identities of four attackers: Ali Bhai alias Talha (Pakistani national), Asif Fauji (Pakistani national), Adil Hussain Thoker (Anantnag resident), and Ahsan (Pulwama resident). The tactical leader was identified as Hashim Moosa, alias Suleman Shah, a former Pakistani SSG para-commando. Three attackers were killed in the subsequent Operation Mahadev encounter on July 28, 2025. The discrepancy in numbers across accounts reflects the chaos of the attack, the difficulty of counting moving gunmen in a large meadow, and the possibility that some attackers maintained concealed positions rather than moving openly.

Q: Where exactly in Baisaran Valley did the attack occur?

The attack took place in the Baisaran Valley meadow, located approximately seven kilometers from Pahalgam town in southern Kashmir’s Anantnag district. The meadow sits at roughly 8,000 feet above sea level, surrounded by dense pine forests and the Pir Panjal range. It measures approximately 200 meters wide and 800 meters long, enclosed by a seven-foot chain-link fence with two gates for entry and exit. The meadow is accessible only by foot or horseback along a muddy, rocky trail from Pahalgam town, a journey that takes approximately forty to forty-five minutes. The area is a popular tourist destination often called Mini Switzerland.

Q: How did tourists try to escape the Pahalgam attack?

Escape was severely constrained by the meadow’s geography. The chain-link fence surrounding the meadow blocked lateral movement. Both gates were either occupied by gunmen or sites of initial carnage. Some tourists hid behind rocks or in shallow depressions in the terrain. Others pressed themselves to the ground and played dead. Some attempted to scale or breach the fence to reach the surrounding forest. Local Kashmiri guide Nazakat Ahmad Ali Shah rescued eleven tourists by navigating them through forest paths he knew as a local resident, first carrying two children to Pahalgam town before returning for the remaining group. Some tourists ran toward the attackers’ military-style uniforms, mistaking them for security forces, with fatal consequences.

Q: When did security forces arrive at Pahalgam after the attack began?

Twenty-five CRPF personnel, the first armed response team, reached the Baisaran meadow at approximately 2:30 p.m., roughly ninety minutes after the first shots. They had covered the four-to-five-kilometer trail from their base in Pahalgam town under forty-five minutes while carrying weapons and equipment through difficult terrain. A J&K Police team followed shortly after. The first formal phone call to the police control room was logged even later, at approximately 2:45 p.m. By the time security forces arrived, the attackers had already withdrawn into the surrounding forest. The delay was attributable to the meadow’s remoteness, the absence of armed security within Baisaran itself, unreliable mobile signal coverage that hampered emergency calls, and the fact that the first alert came informally through fleeing pony operators rather than through formal communication channels.

Q: What was the demographic pattern of the Pahalgam victims?

Twenty-five of the twenty-six victims were non-Muslim. The majority were Hindu tourists from across India, representing a wide demographic range: newlyweds on honeymoons, families with children, a sixty-eight-year-old man, military personnel on leave, a government intelligence officer, and banking employees. One victim was Christian: Sushil Nathaniel from Indore, who identified himself as Christian when asked and was killed immediately. The sole Muslim victim was Syed Adil Hussain Shah, a local pony-ride operator who was killed while attempting to protect tourists, not as a target of the identification process. The pattern strongly supports the finding that the attack specifically targeted non-Muslims through a systematic identification process.

Q: Who was the first victim of the Pahalgam attack?

Shubham Dwivedi, a businessman from Kanpur, was among the first victims. He was sitting with his wife Eshanaay in the meadow when a gunman approached from behind and asked, “Are you a Hindu or a Muslim?” Eshanaay answered that they were Hindus, and the attacker shot Shubham point-blank in the head. When Eshanaay pleaded to be killed as well, the attacker refused, telling her she was being spared so she could convey the message to Prime Minister Modi as a witness. Dwivedi had been visiting Kashmir on a family holiday and was scheduled to return home the following day.

Q: Why did TRF retract its claim of responsibility for Pahalgam?

The Resistance Front claimed responsibility for the Pahalgam attack on April 22 and repeated the claim on April 23, accompanying it with a photograph of the attack site. On April 26, TRF reversed course, stating it “unequivocally” denied involvement and blaming the earlier claim on a “coordinated cyber intrusion” that it attributed to Indian intelligence agencies. Indian security officials dismissed the hacking claim, pointing to the initial claim’s specificity, the accompanying photograph, and the four-day delay before the retraction. The more compelling explanation is that the retraction was strategically motivated: TRF’s parent organization LeT, operating under ISI direction, had not anticipated the severity of the international backlash and attempted to re-establish deniability after the attack’s scale made the initial claim a liability.

Q: Was the Pahalgam attack connected to The Resistance Front and Lashkar-e-Taiba?

Extensively. TRF initially claimed responsibility. Investigators established that TRF is an organizational front for Lashkar-e-Taiba, created after the 2019 abrogation of Article 370 to project an appearance of indigenous Kashmiri resistance while operating under LeT and ISI direction. The UNSC’s 36th Monitoring Team report confirmed TRF’s connection to LeT. Two UN member states affirmed the attack could not have been executed without Pakistan-based LeT support. The U.S. designated TRF as a Foreign Terrorist Organization in July 2025, explicitly citing the Pahalgam attack and describing TRF as “a front and proxy” for LeT. NIA investigations traced funding through international channels to LeT-connected networks in Pakistan, Malaysia, and Gulf states.

Q: How was Operation Mahadev launched in response to Pahalgam?

Operation Mahadev was launched on the day of the attack with the directive to prevent the attackers from escaping to Pakistan. Security forces established a search grid across southern Kashmir involving CRPF, J&K Police, and the Indian Army, supplemented by aerial surveillance using helicopters and drones. The operation tracked the attackers for three months through southern Kashmir’s forests and mountains. A breakthrough came when a Huawei satellite phone monitored since April 22 made an unusual call on July 26, allowing analysts to narrow the attackers’ location to a four-square-kilometer area in Harwan forest near Dachigam. On July 28, using drone surveillance and Para Special Forces personnel, security forces engaged and killed three attackers identified as Suleman Shah, Abu Hamza, and Yasir.

Q: What was the connection between Pahalgam and Operation Sindoor?

Pahalgam was the triggering event for Operation Sindoor. Fifteen days after the massacre, on May 7, 2025, India launched missile strikes against nine targets across Pakistan. The fourteen intervening days saw a carefully calibrated escalation ladder: diplomatic suspension, Simla Agreement revocation, trade suspension, and Indus Waters Treaty restriction. Each step was a signal and an off-ramp that Pakistan declined to take. The attack’s sectarian character made it politically impossible for India to absorb without a military response proportionate to the offense’s gravity.

Q: Who was Sajjad Gul and what was his role in the Pahalgam attack?

Sheikh Sajjad Gul, alias Sajad Ahmad Sheikh, was identified as the mastermind of the Pahalgam attack. He is the founder of The Resistance Front and operates from Rawalpindi, Pakistan. Designated a terrorist by the NIA in April 2022, Gul was educated in Srinagar, completed an MBA in Bangalore, and later trained as a lab technician in Kerala. He returned to Kashmir and opened a diagnostic laboratory while providing logistical support to LeT operations. The ISI used him as a local Kashmiri face for the predominantly Punjabi LeT, creating a layer of separation between the attacks and their actual organizational origin. NIA investigations linked him to multiple terror attacks between 2020 and 2024, including targeted killings and grenade attacks across central and southern Kashmir.

Q: How did Kashmir’s local population respond to the Pahalgam attack?

The Kashmiri response was swift, broad, and unequivocal in its condemnation. Protests erupted across Muslim-majority regions including Srinagar, Pulwama, Shopian, Anantnag, and Baramulla. Demonstrators called the attack a blow to Kashmiriyat, the tradition of composite Kashmiri identity. Shops and businesses shut down in solidarity. An all-party meeting in Srinagar on April 24 condemned the attack unanimously. Mirwaiz Umar Farooq, in his Friday sermon on April 25, declared Kashmiris stood shoulder to shoulder with the victims. A special session of the J&K Legislative Assembly on April 28 passed a resolution condemning the massacre and endorsing the government’s response. Local heroes like Nazakat Ahmad Ali Shah, who rescued eleven tourists, and Adil Hussain Shah, who died protecting visitors, became symbols of Kashmiri solidarity with the victims.

Q: Was the Pahalgam attack the deadliest terror attack in India’s history?

With twenty-six dead, Pahalgam was the deadliest terror attack on civilians in India since the November 2008 Mumbai attacks, which killed 166 people across multiple locations over four days. It was the deadliest single-location terror attack on civilians in Jammu and Kashmir’s modern history. Previous major attacks in Kashmir, such as the 2016 Uri Army camp assault (nineteen soldiers killed) and the 2019 Pulwama CRPF convoy bombing (forty personnel killed), targeted security forces rather than civilians. The Pahalgam attack’s targeting of unarmed tourists at a recreational site placed it in a category distinct from attacks on military installations.

Q: What weapons were used in the Pahalgam attack?

Armed with M4 carbines and AK-47 assault rifles, the attackers wore military-style uniforms. At least one wore a traditional Kashmiri pheran. They carried modern communication equipment and body-mounted cameras that recorded the massacre. The combination of M4 carbines, typically associated with Western military forces and their allies, and AK-47s, the standard infantry weapon across South Asia, suggested access to diverse supply channels. The M4 carbines were significant because their presence in a Kashmiri militant operation pointed to supply chains that extended beyond the typical Pakistani-origin weapons pipeline.

Q: How did the international community respond to the Pahalgam attack?

International condemnation was broad, spanning the geopolitical spectrum. UN Secretary General Antonio Guterres called the attack unacceptable. The Taliban’s Afghan government condemned it as undermining regional security. U.S. President Donald Trump, Russian President Vladimir Putin, and Israeli Prime Minister Benjamin Netanyahu expressed solidarity with India. Argentina and several European nations offered condolences. The UNSC issued a press statement acknowledging the attack as a “reprehensible act of terrorism.” The U.S. designated TRF as a Foreign Terrorist Organization in July 2025, explicitly citing Pahalgam. The breadth of international condemnation reflected how the attack’s sectarian methodology, the targeting of tourists by religion at a recreational site, fell outside the boundaries of what even states sympathetic to Pakistan’s Kashmir position could defend.

Q: What is the significance of the body cameras used by the Pahalgam attackers?

The attackers’ use of body-mounted cameras to record the massacre served propaganda purposes. Security sources indicated the footage was transmitted to handlers, presumably in Pakistan, for potential use as recruitment or intimidation material. The cameras, combined with the selfies that eyewitnesses reported the attackers taking during the killing, demonstrated operational confidence: the gunmen believed they had sufficient time and security to document their actions without interruption. The footage was never publicly released, and Indian security officials have suggested that after TRF retracted its claim of responsibility, LeT’s leadership decided the body camera material was too incriminating to distribute.

Q: What happened to the attackers after the Pahalgam massacre?

Three of the attackers, identified as Suleman Shah (Hashim Moosa), Abu Hamza (Hamza Afghani), and Yasir (Jibran), were tracked for three months through southern Kashmir’s forests during Operation Mahadev and killed in an encounter on July 28, 2025, in Harwan jungle near Mahadev Ridge in Dachigam. They were located through signals intelligence, specifically the monitoring of a Huawei satellite phone that pinged the Inmarsat-4 F1 satellite. Two local accomplices, Parvaiz Ahmad Jothar and Bashir Ahmad Jothar, who had sheltered the attackers the night before the massacre, were detained by the NIA in June 2025. Additional arrests followed, including a logistical support operative from Kulgam district.

Q: How did Pakistan respond to the Pahalgam attack accusations?

Pakistan officially denied any involvement in or support for the Pahalgam attack, maintaining its standard position of providing only “diplomatic and moral support” for the Kashmiri people. Pakistan’s Deputy Prime Minister and Foreign Minister Ishaq Dar inflamed tensions by suggesting the assailants “might be freedom fighters.” Pakistan also characterized the attack at various points as a “false flag operation” staged by Indian intelligence to justify military action. Pakistan lobbied the UNSC to remove references to TRF from its initial press statement condemning the attack, achieving a partial success that was later reversed by the Monitoring Team report. After Operation Sindoor, Pakistan retaliated with artillery shelling on Poonch and other Indian border towns.

Q: Could the Pahalgam attack have been prevented?

The attack exploited specific security gaps that, in retrospect, were identifiable: the absence of armed security within the Baisaran meadow, the reliance on a single access trail for both tourist traffic and security response, the lack of communication infrastructure in the valley, and the general assumption that Pahalgam’s remoteness was protection rather than vulnerability. Whether addressing these gaps would have prevented the attack is debatable, as determined attackers with local support can often find soft targets, but the ninety-minute gap between the first shots and the first security response represents a systemic failure rather than an operational one. Post-attack security restructuring has addressed several of these gaps, including armed deployments within tourist areas, improved communication infrastructure, and drone surveillance of high-value tourist destinations.

Q: What memorial exists for the Pahalgam attack victims?

A black marble memorial was erected on the banks of the Lidder River in Pahalgam, inscribed with the names of all twenty-six victims. The memorial was established in the year following the attack and serves as both a tribute to those killed and a symbol of India’s collective resolve against terrorism. On the first anniversary of the attack in April 2026, India observed a national day of remembrance. Leaders from countries including Israel, Argentina, the United States, and several European nations expressed renewed solidarity.

Q: What operations were launched after Pahalgam beyond Operation Sindoor?

The post-Pahalgam response extended well beyond the military strikes of Operation Sindoor. Operation Mahadev tracked and eliminated the attackers within three months. Operation Amrit launched a comprehensive nationwide crackdown to disrupt terror networks, funding, and infiltration channels. Operation Vajra targeted specific organizational infrastructure. Operation Trident focused on cross-border infiltration routes. Collectively, these operations resulted in thousands of SIM cards being blocked, hundreds of suspects arrested, terror-financing channels disrupted, and a sustained intelligence-driven campaign against LeT and TRF operatives and support networks across India. India also suspended the Indus Waters Treaty, rescinded visas for Pakistani nationals, and ordered those already in the country to leave.

Q: How did the Pahalgam attack compare to the 2019 Pulwama attack?

Both attacks triggered massive Indian military responses. The Pulwama attack killed forty CRPF personnel in a vehicle-borne IED attack on a convoy and led to the Balakot airstrike. Pahalgam killed twenty-six civilians in a sectarian massacre and led to Operation Sindoor’s multi-target missile strikes. Key differences: Pulwama targeted security forces using an IED (impersonal destruction); Pahalgam targeted tourists using religious identification (personal, face-to-face killing). Pulwama was attributed to JeM; Pahalgam was linked to LeT through TRF. Pulwama’s response (Balakot) involved a single airstrike on one target; Pahalgam’s response (Sindoor) involved simultaneous strikes on nine targets using multiple weapons platforms. The escalation from Pulwama to Pahalgam, in both attack methodology and response intensity, represented a significant ratcheting of the India-Pakistan conflict spiral.

Q: What role did Pakistan’s Army chief Asim Munir play in the context of the Pahalgam attack?

In the weeks preceding the Pahalgam massacre, Pakistan’s Army chief General Asim Munir delivered a public speech invoking the two-nation theory, declaring that Hindus and Muslims are fundamentally distinct in religion, culture, traditions, thoughts, and ambitions, and that their forefathers understood Hindus and Muslims to be two separate nations. Indian security analysts and commentators noted the ideological alignment between Munir’s rhetoric, which framed Hindu identity as fundamentally incompatible with Muslim identity, and the Pahalgam attackers’ methodology of identifying and killing victims based on precisely that Hindu-Muslim distinction. Whether Munir’s speech directly influenced the attack’s planning or merely reflected the prevailing institutional ideology within which the attack was conceived remains a matter of analysis rather than established fact, but the temporal and ideological proximity between the Army chief’s sectarian framing and the attackers’ sectarian targeting was widely remarked upon.

Q: What was the Huawei satellite phone that helped track the Pahalgam attackers?

A Huawei satellite phone, its IMEI number partially identified from intelligence databases, became the critical piece of signals intelligence that led to the attackers’ eventual location and elimination. The phone had been under electronic monitoring since April 22, 2025, with its signals tracked pinging the Inmarsat-4 F1 satellite as the attackers moved through southern Kashmir’s forests. For three months, intelligence analysts monitored the phone’s intermittent signals, attempting to narrow the geographic area of the fugitives. On July 26, the device made an unusual call that allowed analysts to triangulate the attackers’ position to a four-square-kilometer section of Harwan forest near Mahadev Ridge in the Dachigam area. This intelligence enabled the planning and execution of the July 28 encounter that killed three of the attackers. The episode demonstrates both the value and the limitations of signals intelligence in counter-terrorism: the phone provided eventual location data but required three months of patient monitoring before yielding actionable intelligence.

Q: What is the significance of the Pahalgam attack for India-Pakistan nuclear deterrence?

The Pahalgam attack and the subsequent Operation Sindoor response fundamentally altered the nuclear deterrence equation between India and Pakistan. For decades, Pakistan’s nuclear arsenal was assumed to provide a shield against Indian conventional military retaliation for terror attacks, a dynamic that analysts described as the “stability-instability paradox” in which nuclear weapons stabilize the relationship against major war while creating instability at lower levels by enabling Pakistani proxy attacks with reduced fear of conventional retaliation. Pahalgam and Sindoor demonstrated that India was willing to conduct substantial military strikes on Pakistani territory despite Pakistan’s nuclear capability, suggesting that the deterrent effect of Pakistan’s nuclear arsenal had diminished significantly, at least against strikes that India judged proportionate to the provocation. The precedent has implications extending far beyond the India-Pakistan dyad, as it suggests that nuclear weapons may not indefinitely protect states that sponsor cross-border terrorism from conventional military consequences.

Q: Who was Syed Adil Hussain Shah and what did he do during the Pahalgam attack?

Syed Adil Hussain Shah was a local Kashmiri pony-ride operator and tourist guide who was killed while attempting to protect tourists during the Pahalgam attack. He was the only Muslim victim, and his death occurred not because the attackers targeted him by religion but because he intervened to shield tourists from the gunmen. His cousin, Nazakat Ahmad Ali Shah, also a guide and trader in woollen clothes, survived and managed to rescue eleven tourists by navigating them through forest paths to the safety of Pahalgam town, first carrying two children on the initial trip before returning for the remaining group. Adil’s sacrifice and Nazakat’s heroism became central to the post-attack narrative of Kashmiri solidarity with the victims. Their actions demonstrated that the attackers’ sectarian framework did not represent the values of ordinary Kashmiris, a point emphasized by Kashmiri civil society organizations, political leaders, and the public protests that erupted across the valley in the attack’s aftermath.

Q: How has Pahalgam’s tourism industry recovered after the attack?

The immediate impact on Pahalgam’s tourism economy was devastating. Hotel bookings across Kashmir were canceled en masse. The Indian government temporarily closed forty-eight of eighty-seven tourist destinations in J&K. Pony operators, hotel workers, guides, and handicraft sellers lost their primary income source. Recovery has been gradual and uneven. Enhanced security measures, including armed deployments within tourist areas, drone surveillance, and dedicated tourist-protection units, have been introduced to rebuild confidence among potential visitors. The black marble memorial on the Lidder River has itself become a site that visitors acknowledge, and Pahalgam’s tourism numbers have shown recovery trajectories comparable to other destinations that suffered major terror attacks. However, the psychological impact on the local tourism workforce remains significant, with many guides and pony operators who witnessed the massacre reporting ongoing trauma that affects their ability to work in the same locations where the killing occurred.