From CCTV Clues To DNA Proof: Delhi Blast Probe Unfolds
From CCTV Clues To DNA Proof: Delhi Blast Probe Unfolds
- Raids Intensify; Türkiye Link Under Scrutiny 4-City Terror Plan Surfaces; Al Falah Faces Action
Srinagar- The investigation into the deadly Red Fort blast that killed 13 people earlier this week has expanded across multiple states and now involves international coordination, with forensic confirmation of the bomber's identity, reconstruction of his last movements, fresh detentions, and scrutiny of overseas travel by several doctors linked to what officials describe as a“white-collar terror module.”
DNA Confirms Umar Was Driving the Blast Car
Police sources on Thursday confirmed that DNA samples collected from the blast site match those of Pulwama-based doctor Umar Nabi, establishing beyond doubt that he was driving the explosives-laden Hyundai i20 that blew up outside the Red Fort on Monday evening. The DNA samples of his mother, taken on Tuesday, were analysed alongside the remains recovered from the site.
ADVERTISEMENT“The DNA results confirm that it was indeed Umar who was driving the fateful vehicle,” a senior police source said. Umar was among the key suspects linked to a module with alleged ties to Jaish-e-Mohammed and Ansar Ghazwat- Hind.
Umar's Final 24 Hours: Zigzag Routes & Night Stay In Car
Investigators reconstructed Umar's route using footage from more than 50 CCTV cameras across Delhi and Haryana. The trail shows him leaving Faridabad on Sunday morning, travelling along the Delhi–Mumbai Expressway, halting at a dhaba in Haryana's Nuh district, and spending the night inside his car.
The next morning, he re-entered Delhi via the Badarpur border and drove a looping, zigzag path across Southeast, East, New Delhi, Central and Northwest Delhi-movements police believe were calculated to avoid surveillance.
He was captured stopping at an eatery in Ashok Vihar, appearing calm, before heading toward central Delhi. Later, he visited a mosque near Asaf Ali Road, where he stayed for nearly three hours.
Police said his phone activity during this period is also being closely examined. Investigators suspect he might have received instructions before proceeding toward the site.
“At 3:19 pm, Umar's car entered the parking area adjacent to the Red Fort complex, where it remained stationary for around three hours. CCTV footage shows the car parked quietly among other vehicles near the Sunehri Masjid parking,” an officer privy to the investigation said.
Around 6:22 pm, the car was seen leaving the parking area and heading towards the Red Fort Metro Station side. Barely 30 minutes later, at 6:52 pm, the vehicle exploded in a powerful blast that shattered windows, scattered body parts across the road, and triggered panic among visitors and commuters in the area.
Encrypted Apps, ₹26 Lakh Pool & 4-City Terror Plot
Investigators probing the Red Fort blast have uncovered an extensive network of encrypted communication, pooled funds, coded notes and chemical purchases that point to a meticulously coordinated plan by what officials describe as a“white-coat terror module” involving young medical professionals.
According to police sources, the three core suspects - Dr Umar Nabi, who drove the explosives-laden Hyundai i20 that detonated on Monday, Dr Muzammil Ahmad Ganaie and Dr Shaheen Shahid - allegedly used the Switzerland-based encrypted messaging app Threema to communicate and coordinate their activities. Umar had also created a small Signal group, consisting of two to four members, to handle operational instructions.
Investigators said the group had pooled more than ₹26 lakh in cash, which was handed over to Umar for“safekeeping and operational use.” Using part of the pooled amount, the suspects allegedly bought 26 quintals of NPK fertiliser, worth around ₹3 lakh, from suppliers in Gurugram, Nuh and nearby towns. NPK fertiliser, when mixed with other chemicals such as potassium chlorate and sulphur, can be used to make Improvised Explosive Devices (IEDs).
Legal Disclaimer:
MENAFN provides the
information “as is” without warranty of any kind. We do not accept
any responsibility or liability for the accuracy, content, images,
videos, licenses, completeness, legality, or reliability of the information
contained in this article. If you have any complaints or copyright
issues related to this article, kindly contact the provider above.

Comments
No comment