2025 Pahalgam attack
Islamist terror attack in India
The 2025 Pahalgam attack, also referred to as the 2025 Pahalgam massacre, was an Islamist terrorist attack on tourists by three armed militants near Pahalgam in Indian-administered Jammu and Kashmir in which 26 civilians were killed on 22 April 2025. The attackers targeted Hindu tourists, though a Christian tourist and a local Muslim pony ride operator were also killed. The attackers, armed with M4 carbines and AK-47s, entered the Baisaran Valley, a popular tourist spot, through the surrounding forests. This incident is considered the deadliest attack on civilians in India since the 2008 Mumbai attacks. Scholars and analysts contend that the specific targeting of Hindus, the high civilian casualty of the massacre and its barbarity was aimed at exploiting 'communal fault lines' and elicit a reaction from the Indian government, compelling the government to respond militarily.
The Resistance Front (TRF), a proxy of the Pakistan-based Islamist UN-designated terrorist group Lashkar-e-Taiba (LeT), with a history of attacks on religious minorities,
initially claimed responsibility for the attack. It did so twice, on both the day of the attack and the next day. TRF released a statement that the attack was in opposition to non-local settlement in the region resulting from the abolition of the special status of Kashmir. After a few days, TRF denied its involvement in the attack.
The militants singled out the men and asked for their religion before shooting the Hindu and Christian tourists.
“2025 Pahalgam attack” enters the record as islamist terror attack in India. Crown Archives preserves that source wording while asking what Pahalgam, attack and Islamist can confirm, complicate or overturn.
Why this record matters
“2025 Pahalgam attack” is worth following because a concise public description often conceals a longer documentary argument. Here, Pahalgam, attack and Islamist provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 22, 2026. The linked authority identifier is Q134044277. Authority coordinates are 34.004, 75.334. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2025 and 2008.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “2025 Pahalgam attack”, its source revision and the description used here.
- Expand the search: follow 2025 Pahalgam attack primary sources, 2025 Pahalgam attack archive and Pahalgam research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “2025 Pahalgam attack”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “2025 Pahalgam attack” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.