Indian strikes during the May 2025 Operation Sindoor crisis hit Pakistan's Kirana Hills nuclear-storage site and triggered a radioactive leak

Why the story spread so fast

To understand why so many people believed it, take the claim on its own terms for a moment. It did not feel like a random rumor. It felt like a scoop.

Kirana Hills is a real place with a real reputation. Open-source analysts have long linked it to Pakistan's nuclear program and to cold tests conducted decades ago, and it sits near a major airbase in the country's most secretive military zone. So a story about Kirana Hills was not starting from zero; it was borrowing the plausibility of a genuinely sensitive site. Layer on a shooting war in which strikes were actually happening, and the leap to “one of those strikes hit the nuclear hill” felt small.

Then came the specifics, which are what gave the claim its authority. A named type of aircraft. A foreign aid flight. A document. Photographs of people in hazmat suits. To a viewer scrolling in the middle of a crisis, that texture reads as research, as the kind of detail a fabricator would not bother to invent. The problem, as the fact-checkers would show, is that the details were real objects attached to the wrong story.

The claim was not believed in spite of its specifics. It was believed because of them, and the specifics were exactly where it fell apart.

Finally, it fit what audiences on both sides wanted. For one, it was evidence of a crushing blow delivered; for the other, proof of a reckless, poisoning attack. A claim that confirms an existing grievance does not have to fight for belief. It gets waved through.

The evidence that fell apart

The visual case for the leak collapsed under exactly the kind of reverse-image and source-tracing work fact-checkers do in a crisis. The photographs shared as US Department of Energy personnel inspecting fallout near Kirana Hills were not from Pakistan. As BOOM documented, they were old images from the Semipalatinsk nuclear-test site in Kazakhstan, a long-closed Soviet facility that has nothing to do with Operation Sindoor.

The video fared no better. A clip passed around as an explosion at Kirana Hills was traced by NewsMeter and others to a 2015 airstrike in Sanaa, Yemen, years before this conflict and thousands of kilometers away. The leaked letter that supposedly confirmed the contamination went viral without any verified provenance; analysts reviewing the crisis, including the Bulletin of the Atomic Scientists, described it as doctored.

Strip away the misattributed images, the recycled footage, and the unauthenticated document, and there is nothing left holding the claim up. What remained was an inference: aircraft moved, a sensitive site exists, a war was on, so surely something nuclear happened. Inference is not evidence, and every concrete artifact offered as evidence turned out to be about somewhere else.

What the officials and the watchdog actually said

The claim also failed at its two load-bearing joints: the strike and the leak. Both were addressed directly by the people positioned to know, and both were denied.

On the strike: at a joint DGMO briefing on 12 May, India's Director General of Air Operations, Air Marshal A K Bharti, was asked point-blank about the Kirana Hills speculation. He said the Indian Air Force had not hit it, adding, in a line widely quoted afterward, that he was grateful to be told the site apparently housed nuclear installations because the air force had not known. Pakistan's military, for its part, dismissed the account and rejected the premise that a nuclear facility there had been struck.

On the leak: the International Atomic Energy Agency, the body whose entire mandate is to monitor exactly this, addressed the reports and said that, based on the information available to it, there had been no radiation leak or release from any nuclear facility in Pakistan. That is not a non-denial or a bureaucratic dodge; it is a direct statement from the relevant authority responding to the specific claim.

One official comment did complicate the picture, and it is worth being honest about it. India's defence minister, Rajnath Singh, said Pakistan was an irresponsible state and that the IAEA should take charge of its nuclear weapons. Made while the leak rumor was already circulating, the remark was read by some as tacit confirmation. But invoking the IAEA is not the same as the IAEA finding a leak, and the agency had reported none. A politician's rhetorical jab does not override the monitor's technical finding.

The psychology of a wartime nuclear scare

There is a reason nuclear-leak rumors travel so well in a crisis, and it is not that people are gullible. It is that the stakes are so high that the cost of dismissing a true warning feels enormous, so the mind leans toward taking the scary claim seriously just in case. Fear is not irrational here; it is the rumor's fuel.

The fog of war does the rest. When verified facts are scarce and arrive slowly, the fastest, most vivid claim occupies the space that confirmation has not yet reached. By the time a careful debunk lands, the impression, that maybe a nuclear site really was breached, has already been planted in people who will never see the correction. Corrections are quieter and slower than the panic they answer.

A nuclear-leak claim does not need to be proven to do damage. It only needs to be plausible for long enough, in a moment frightening enough, to shape how people read everything that follows.

That is why analysts studying the 2025 crisis treat this episode as more than a curiosity. A false radiation claim between two nuclear-armed states, amplified by officials and cable news, is the kind of thing that can feed real escalation, hardening publics and narrowing the room decision-makers have to step back. The harm is not only that some people believed a hoax; it is that the hoax raised the temperature of an already dangerous standoff.