CTD announces head money for 11 wanted terrorists

Department’s K-P chapter places collective bounty of Rs13.1 million on these militants


News Desk May 02, 2024
The CTD has placed a collective bounty of Rs13.1 million on these terrorists. PHOTO: EXPRESS

The Counter Terrorism Department (CTD) of Khyber-Pakhtunkhwa (K-P) on Thursday recently released a list featuring 11 individuals identified as highly wanted terrorists, along with their names and photographs.

This move signals a concerted effort to bring these individuals to justice, with a reward offered for their capture, either deceased or alive.

The identified terrorists hail from various regions across K-P, spanning from Lakki Marwat to Bannu, and extending to Shangla and other parts of the province. The CTD has placed a collective bounty of Rs13.1 million on these terrorists, underscoring the seriousness of the threat they pose.

Read more: CTD releases fresh list of 152 wanted terrorists

Among the wanted terrorists, Habibullah, also known as Saifullah, from Lakki Marwat, carries the highest reward of Rs5 million for his apprehension. Similarly, Mohammad Jameel, a resident of Bannu, has a bounty of Rs3 million placed on him.

Other individuals on the list included Mohammad Gul, alias Saqi, from Lakki Marwat, and Rabidullah, alias Chag, from Bannu, with rewards of Rs1 million each for their capture.

This announcement follows the issuance of three previous lists by the CTD last year, which collectively identified 294 wanted terrorists. With the inclusion of these 11 individuals, the total number of wanted terrorists for whom rewards have been offered now stands at 305, highlighting the ongoing efforts to combat terrorism in the region.

Sources indicated that individuals involved in recent terrorist activities have been specifically targeted in this latest list, reflecting the authorities' commitment to addressing current security challenges.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ