14th January, 2015 3:56am
National Comments
Bengaluru blast,Syed Ismail Afaq,operative,National Investigation Agency
HYDERABAD: Alleged Indian Mujahideen operative Syed Ismail Afaq, who was picked by the Karnataka police in Bhatkal district of the state last week for his role in the recent Bengaluru blast, reportedly supplied explosives used in the Dilsukhnagar twin blasts in February, 2013. The blasts had claimed 18 lives and injured over 130 persons.
Top sources in the intelligence told TOI that Afaq had revealed names of persons from whom he had been receiving explosives, which were used for blasts across the country, including the Dilsukhnagar blasts in Hyderabad. The sources said Afaq was a hardcore IM operative.
"Afaq supplied explosives, but had not assembled the improvised explosive devices (IEDs) strapped to cycles and used in the Dilsukhnagar blasts. He divulged names of some more persons who were part of the IM explosive logistics team and they will be nabbed soon to know the actual source of the material. Afaq had in February, 2013 handed over explosives to IM operative Asadullah Akhtar near a commercial complex in Mangalore,'' the sources said. It is learnt that the National Investigation Agency (NIA) and other intelligence officials have information that explosives originated in Bihar.
A commercial complex watchman in Mangalore found Afaq, clutching a big bag, moving suspiciously in the vicinity of the complex and enquired about his whereabouts. Sensing trouble, Afaq escaped from the place with bag of explosives, which were sent to Hyderabad, police sources said.
Afaq was directly in contact with fugitive Riyaz Bhatkal, the most wanted terrorist in India and the prime accused in the Dilsukhnagar twin blasts. On Riyaz's instructions, Afaq used to deliver explosives to unknown persons linked to IM module.
On interrogation of the IM operatives Asadullah Akhtar, Waqas and Tehseen, arrested in the Dilsukhnagar case, they claimed ignorance of the identity of the person who had supplied the explosives.
User Comments ( 0 )