Extortion and intimidation calls are designed to win in the first few seconds. Attackers use foreign numbers, VoIP routes, virtual numbers, hidden caller identity and impersonation to create instant fear. For a business owner, doctor, contractor, trader or public-facing citizen, the damage starts before a formal complaint is even filed.

The earlier process was reactive. A person received the call, read the message, heard the voice note, became frightened and only then reported it. By then the attacker had already delivered the psychological payload. Abhedya changed the direction of the workflow: detection first, block before exposure, record the event and let police teams investigate patterns without forcing the citizen to absorb every threat.

Threat Model

• International or virtual numbers used to hide the origin of extortion calls.
• VoIP-based calls and messages routed through common messaging platforms.
• Hidden or private numbers used to bypass ordinary caller identification.
• Unsaved domestic numbers that may be used after international paths are blocked.
• WhatsApp and WhatsApp Business threat calls, images, voice notes, videos, forwarded media and missed-call artifacts that can still trigger fear even when the call is not answered.

The core solution was a layered mobile defense system. Abhedya watches the incoming WhatsApp and WhatsApp Business communication surface, classifies suspicious origin patterns, blocks or suppresses threat calls and harmful media before the user is exposed and stores the event trail for authorized review. The companion dialer package extends that control into regular telephony where Android requires a dialer-aware component.

Package Responsibilities

• com.iamcod3x.abhedya: WhatsApp and WhatsApp Business protection for threat calls, images, voice notes, videos, media artifacts, policy handling, event capture, controlled reporting and backend coordination.
• com.iamcod3x.dialer: dialer-side call handling, verified contact checks, suspicious incoming-call suppression and user-safe call state management.

Protection Flow

1. Incoming WhatsApp, WhatsApp Business and phone communication is observed at the call, notification, media, or messaging layer.
2. The source is classified using number type, country prefix, virtual-number signals, saved-contact state and local policy.
3. If suspicious, the threat call, image, voice note, video or message artifact is rejected, blocked, muted or removed before the citizen interacts with it.
4. A minimal event record is stored for backend intelligence and later investigation.
5. Rules are refined from district feedback so the system blocks threats without isolating the user from legitimate contacts.

incoming_event
  -> normalize source
  -> check saved and verified contacts
  -> classify international, virtual, hidden, unsaved, suspicious domestic or risky media
  -> block threat calls, images, voice notes, videos and message artifacts before user exposure
  -> store event metadata for authorized investigation
  -> update local policy cache

Debugging Abhedya was less about one crash and more about timing, permissions and trust. A call-blocking app fails if it is one second late, one permission short or one false positive too aggressive. We treated the system as a real-time safety product and tested it against the messy edges of Android behavior.

1. Reproducing the Threat Surface

We used controlled numbers, saved contacts, unsaved contacts, international prefixes, hidden caller identity, WhatsApp calls, WhatsApp Business calls, images, voice notes, videos and messaging notifications to recreate the paths attackers were using. Each test was measured by a simple standard: did the citizen see the threat or did Abhedya intercept it first?

2. Fixing Android Role and Permission Edges

Android protects call handling behind roles and sensitive permissions. That is why the dialer package exists. Instead of forcing one app to do everything, the series separated the protection engine from the dialer surface and tested permission grants, default-role behavior, contact access, phone-state access, notification access and boot persistence independently.

3. Beating Race Conditions

The hardest bugs were race conditions: a notification flashing before removal, a WhatsApp media preview appearing before suppression, a voice note or video notification becoming visible, a VoIP alert appearing before the classifier finished or a blocked number leaving a visible missed-call artifact. We moved decisions earlier, cached recent classifications locally and reduced dependency on slow network checks during the incoming-event window.

4. Reducing False Positives

Blocking everything unknown would be easy, but it would be unusable. We tested saved contacts, verified contacts, emergency contacts, local service numbers, banks, district officials and common business workflows. The aim was to block threat channels while keeping ordinary life reachable.

5. Verifying Backend Evidence

Blocking helps the citizen; evidence helps the investigation. We validated that blocked-event metadata reached the backend with timestamps, source indicators and policy decisions, while keeping the data surface minimal and auditable. Public reports later connected Abhedya-backed tracking with arrests of five members of an interstate gang.

Abhedya did not begin as a normal mass-market app. In the first phase, access was controlled because the system handled sensitive security workflows and could affect who was allowed to reach a protected person. Public reporting on April 30, 2026 stated that installation files were being provided by police and that the app was not yet available on Play Store.

The move to Play Store required packaging the same protection idea in a policy-compliant Android release path:

1. Separate the core Abhedya app and dialer-side package so each requested only the capabilities it needed.
2. Declare sensitive permissions with clear user-facing purpose: call filtering, contact verification, suspicious-message handling and safety reporting.
3. Prepare Play Console data-safety disclosures around event metadata, backend tracking and security use.
4. Run release builds through device testing for onboarding, default dialer setup, notification behavior, background execution and update migration.
5. Release after operational confidence from the controlled rollout and early district feedback.

By May 21, 2026, Times of India reported that Gurgaon Police leadership was promoting Abhedya and that the app had been made available on the Play Store for Android phones on Tuesday, May 19, 2026. That public milestone marks the transition from authorized distribution to broader citizen availability.

Package links: com.iamcod3x.abhedya and com.iamcod3x.dialer

The strongest user response was not a rating number. It was relief. Publicly reported users said that after installing Abhedya they stopped receiving extortion calls or threatening messages for the observed period, slept more peacefully and felt able to focus on work again.

Reported Feedback Signals

• Trial users reported satisfaction after suspicious numbers were blocked quickly.
• Business users in Bhiwani and Panipat reported no further extortion messages or calls during the first week after installation.
• District-level reporting from Jind, Kaithal, Jhajjar, Panipat, Bhiwani, Hansi and Rohtak described reduced fear and greater confidence.
• Police leadership described the system as helping reduce the use of international numbers in extortion attempts.

This matters because Abhedya's success metric is psychological as much as technical. A blocked packet is a technical event. A citizen sleeping peacefully after weeks of threats is the product outcome.

The verified public count is conservative because Play Console numbers and police backend totals were not publicly visible in the sources available on May 31, 2026. Using only public reporting, Abhedya had protected at least 230 citizens/users by April 6, 2026, after an initial trial of around 25 users and close to 200 installs within 10 days of the March 21 launch.

Publicly Reported Date	Verified Figure	Meaning
Trial phase	~25 users	Initial protected-user test set; all reported satisfaction in public coverage.
March 31, 2026 window	~200 installs	Close to 200 protected businessmen, doctors and prominent persons within 10 days.
April 6, 2026	230 downloads/users	Publicly reported statewide adoption count.
April 30, 2026	21 Faridabad businessmen/traders	District-specific public count of people provided Abhedya protection.
Post Play Store availability	Not publicly verified	Broader Android availability was reported, but a reliable public Play Store install count was not available.

Impact was also visible in threat reduction. Indian Express reported a 40-50% reduction in extortion calls after launch, while other coverage reported a significant decline in international-number threat attempts. Public reporting also connected Abhedya tracking with the arrest of five members of an interstate gang and the disruption of planned targets across Sonipat, Panipat and Delhi.

• Prevention beats response: the system is valuable because it blocks the threat before the citizen has to process it.
• Android roles shape architecture: sensitive call control belongs in a component that respects the platform's dialer and permission model.
• Latency is a safety issue: classification must happen quickly enough that the harmful communication never becomes visible.
• Evidence and privacy must be balanced: backend records help investigations, but the data should be minimal, auditable and purpose-bound.
• Controlled rollout was correct: the product touched high-risk citizens first, gathered operational feedback and then moved toward broader Play Store access.

1. Indian Express. "Abhedya": Haryana Police's new app to block threat calls before they reach citizen.
2. Indian Express. Haryana Police's Abhedya app cracks down on extortion calls, nets gangsters within days.
3. Hindusthan Samachar. Haryana Police's "Abhedya" App Strengthens Public Safety.
4. Hindustan Times. Dual OTP system launched in 4 districts to shield seniors from cyber fraud.
5. Times of India. New Gurgaon police chief wants to promote carpooling to ease traffic problem.
6. TEAM-AwSM. Cyber Intelligence & Digital Safety.
7. Google Play. com.iamcod3x.abhedya and com.iamcod3x.dialer.