Messaging, Stalking & Kidnapping: Hyderabad Woman’s Desperate Attempt To Marry TV Anchor Goes Wrong

A TV anchor was kidnapped by a woman in Hyderabad who thought the TV anchor named Pranav was the same person who cheated her on the pretext of marrying her.

A TV anchor was kidnapped by a woman in Hyderabad. Photo : Times Now

In a recent incident, a person named Pranav, who works as an anchor on an entertainment channel, was kidnapped by a woman in Hyderabad under the pretext of assuming that the anchor was the same person who cheated on her under the pretext of marrying her.

The incident unfolded when someone created a fake profile of the anchor on a matrimonial site and, using his fake ID, was talking to a lady named Trishna. The fake profile guy ghosted her when she pestered him to marry her. She was infatuated and wanted to marry him.

Later, when Trishna started to discover Pranav, she found that he was an anchor and started tracking him, thinking he was the same guy who cheated her.

Pranav was kidnapped by Trishna after she tracked his movements. Four others helped her in the kidnapping and held him hostage. However, Pranav managed to escape and promptly reported the harrowing ordeal to the Uppal police in Hyderabad.

As per a police official, ”There was no financial transaction with Pranav. The woman used an air tag to stalk Pranav.”

Subsequent investigations by law enforcement authorities led to Trishna’s arrest and subsequent remand.

Malkajigiri ACP Purushottam Reddy shed light on the situation, revealing that Trishna, who runs a digital marketing business, came in contact with a man who created a fake ID in Bharat Matrimony.

Furthermore, efforts are underway to apprehend the four other individuals allegedly involved in the kidnapping.

As per ACP Purushottam Reddy, the anchor named Pranav has nothing to do with the person who created the fake ID in Bharat Matrimony.

Source : https://www.timesnownews.com/hyderabad/messaging-stalking-and-kidnapping-hyderabad-womans-desperate-attempt-to-marry-tv-anchor-goes-wrong-article-107956446

Exit mobile version