Bengal STF arrests another suspected associate of Jaish operative Hamim Mondal from Howrah

Partially corroborated74

Investigators suspect Aditya Singh came in contact with Mondal through an online gaming platform and was subsequently drawn into the alleged conspiracy.

First seen 3d ago · latest update 3h ago · India · other

Indian mainstream 6
Indian independent 0
International 0
Official 0

How 6 outlets headlined it

The same event in each outlet’s own words. Differences in emphasis and language are part of the picture — we show them, you judge them.

India Today
Owned by: Living Media / India Today Group (Purie family)
- “Hamim's aide arrested as STF probe reveals Bengal CM on Pak operatives' target list”2d ago ↗
Mint
Owned by: HT Media (Bhartia family / Birla group)
- “JeM operative plotted attack on Suvendu Adhikari, Jantar Mantar sabotage — how girlfriend's social media led STF to him”1d ago ↗
Hindustan Times
Owned by: HT Media (Bhartia family / Birla group)
- “Jaish operative, his girlfriend, honeytrap, and a plan to ‘target’ CM Suvendu, CJP protest: Bengal police's big case”1d ago ↗
- “Jaish operative held in Bengal planned to target CM Suvendu, infiltrate Jantar Mantar protest: STF”1d ago ↗
Free Press Journal
Owned by: FPJ Publications Pvt Ltd
- “JeM-Linked Threat Forces West Bengal CM Suvendu Adhikari To Switch To Bulletproof Vehicle After STF Uncovers Alleged Plot | Video”4h ago ↗
- “STF Arrests Hamim Mondal's Associate Arpita Sarkar; Alleges Plot To Target CM, Minister's Son”2d ago ↗
The Hindu
Owned by: The Hindu Group / Kasturi & Sons (family-owned)
- “Bengal STF arrests another suspected associate of Jaish operative Hamim Mondal from Howrah”3h ago ↗
- “Suspected JeM operative arrest leads Bengal STF to Jharkhand woman gathering info on politicians”2d ago ↗
Deccan Herald
Owned by: The Printers (Mysore) Pvt Ltd (family-owned)

Community discussion (1)

JeM operatives allegedly planned terror attack during Jantar Mantar students' protest, says WB STFr/india · 1d ago ↗

Community posts are engagement signals — they never count as corroboration.

See a mistake? Wrong summary · Wrongly grouped · Missing source · Wrong category/region · Dispute outlet rating — each opens a pre-filled report on GitHub.