Cricket
Tennis
Football
Table Tennis
Volleyball
Baseball
Basketball
Horse Racing
Politics
Greyhound Racing
Sports Book
Ice Hockey
Darts
Rugby
The ban is not about the app. It is about the activity.
The Promotion and Regulation of Online Gaming Act, 2025 came into force on 1 May 2026, and it prohibits online money games in all forms — irrespective of skill, chance, or the version of the client that accesses them. Reddy Anna Book falls squarely within the prohibition. The platform is banned, the activity is banned, and the version of the APK installed on your device does not change either fact.
The reference index on Reddy Anna Book login ID APK old version download documents the access architecture these builds sit inside. The operational context is at reddyannaloginid.com.
The question users of old versions are asking is whether the ban changes anything for them specifically. The answer is yes — and the change is not in their favour. What follows is a clinical breakdown of the ban, what it means for the user who has an old version installed, and the specific risks that old-version users face that current-version users do not.
The Legal Basis: What Was Actually Banned
The PROG Act is not a licensing framework for betting. It is a prohibition.
The Act defines an “online money game” as any online game — irrespective of whether it is based on skill, chance, or both — where a user pays fees, deposits money, or places other stakes with the expectation of receiving monetary or other enrichment. The definition captures every product Reddy Anna Book offers: cricket betting, football betting, live casino, Teen Patti, and the rest.
The penalties are structured to deter at every layer of the value chain. Offering or facilitating online money games carries imprisonment up to three years, a fine up to ₹1 crore, or both. Advertising carries up to two years and ₹50 lakh. Facilitating financial transactions carries up to three years and ₹1 crore.
The Act applies to all “Persons,” including foreign entities offering services to Indian users. Reddy Anna’s offshore hosting does not remove it from the Act’s scope.
The Supreme Court’s May 2026 Validation
The ban’s legal foundations were tested and affirmed on 27 May 2026.
The Supreme Court upheld State laws that extended betting-and-gambling regulation into cyberspace and rejected the argument that games of skill are automatically insulated from regulation merely because skill plays a role. The combined effect is a complete legal characterisation of stake-based online gaming as betting and gambling — for constitutional purposes, for regulatory purposes, and for tax purposes.
The skill-chance distinction that for two decades served as the legal shield for real-money gaming platforms has been dismantled. There is no legal route to argue that Reddy Anna is permissible because it involves skill.
The Enforcement Reality: What Is Actually Happening
The ban is not a paper exercise. The enforcement record from 2025 and 2026 is active and specific to this platform.
The Navi Mumbai case
The Navi Mumbai Crime Branch busted a nationwide cyber fraud racket operating through the banned Reddy Anna app, arresting 12 men linked to 393 cybercrime cases involving nearly ₹84 crore. The syndicate used 886 bank accounts across India to conduct illegal gaming, betting, fake job offers, share trading scams, and work-from-home frauds.
The investigation began with the arrest of a 22-year-old who had opened 60 to 70 fake bank accounts used to launder money through the platform. He lured people by offering commission-based work, paying ₹5,000 per account while receiving ₹15,000 from the fraud operators.
The FIR was registered under the Bharatiya Nyaya Sanhita, the IT Act, the Maharashtra Gambling Act, and the Online Gaming Act.
The Ahmedabad case
The Zone-1 police in Ahmedabad arrested five associates of a gang accused of routing crores of rupees through mule bank accounts and funnelling funds to larger criminal syndicates. The men were working as labourers in garages while simultaneously operating a network that handled funds generated through the banned online gaming application known as Reddy Anna.
Police said the accused created and managed multiple gaming IDs for online cricket and football betting activities through the prohibited platform. Money collected from users was deposited into numerous mule bank accounts.
The Chhattisgarh case
Chhattisgarh police busted a major illegal online betting racket run by local youth operating 21 satta apps including Reddy Anna and FBBets across multiple states. The network was spread across Goa, Uttar Pradesh, and Kolkata.
The pattern
These are not isolated incidents. They are the enforcement machinery of the PROG Act operating against a platform that the Act explicitly prohibits. The arrests target operators, agents, and account networks — the people who facilitate the activity. But the enforcement campaign is escalating, and the financial trail is the target.
What the Ban Means for Old Version Users: Four Specific Consequences
Consequence 1: The old version is still the prohibited app
An old version of the Reddy Anna APK is not a different platform. It is the same platform, with a different client. The activity it facilitates — real-money betting on an unlicensed offshore platform — is the same activity.
The PROG Act’s prohibition applies to the activity, not to the version of the application that accesses it. A user who accesses Reddy Anna through an old version is still accessing Reddy Anna. The prohibition is not circumvented by the version number.
The old version does not provide legal cover. It does not create a separate legal identity. It is the same prohibited platform, accessed through a different build.
Consequence 2: The old version offers no protection from the payment-blocking regime
Section 7 of the PROG Act prohibits banks, payment gateways, and financial institutions from processing transactions for prohibited services. The prohibition applies to the transaction, not to the client that initiates it.
A user who deposits funds through an old version is still initiating a transaction that the bank is prohibited from processing. The bank can freeze the account, flag the transaction, and report it. The old version does not change the bank’s obligation or its ability to act.
The financial trail is the target of the enforcement campaign. The Ahmedabad case, the Navi Mumbai case, and the Chhattisgarh case all involved mule accounts and financial routing. An old version user who deposits funds is adding to the trail.
Consequence 3: The old version carries additional legal exposure
The old version is frequently a modded build. It has been decompiled, altered, and re-signed with a self-generated key. This introduces a copyright layer that the current official version does not carry.
Section 65A of the Copyright Act criminalises the circumvention of technological protection measures, with penalties up to two years imprisonment and a fine. A mod that bypasses licensing checks or in-app purchase verification falls within its scope. The user who downloads and installs the mod is in possession of an infringing derivative work.
The legal exposure is cumulative. The PROG Act prohibition applies. The copyright exposure applies. Neither is resolved by the version number.
Consequence 4: The old version is more likely to carry malware
This is the consequence that operates independently of the legal position. The old version is a frozen binary from an abandoned release cycle. It has had more time to be repackaged, carries the known vulnerabilities of its era, and is more likely to match historical malware signatures.
The ModZoo study, the first large-scale analysis of modded Android app markets, examined over 146,000 apps across 13 markets. It found that modded apps are ten times more likely to be flagged as malicious than their official counterparts. A separate category analysis estimated that only 55% of mods were clean.
The old version does not reduce the malware probability. It increases it. And the malware does not care about the legal status of the platform. A banking trojan on a device used for banking is a banking trojan, regardless of which version of the betting app delivered it.
The Diagnostic Table
| Consequence | What it means for old version users | What it does not mean |
|---|---|---|
| The old version is still the prohibited app | Same legal exposure as current version | No separate legal identity |
| Payment-blocking regime applies | Transactions can be blocked or frozen | No protection from bank action |
| Copyright exposure applies | Section 65A penalties up to 2 years | The current version does not carry this layer |
| Malware probability is higher | 10x baseline for modded builds | The old version does not reduce risk |
The pattern is the analysis. The old version does not provide a legal safe harbour. It does not provide protection from the payment-blocking regime. It adds a copyright layer and increases the malware probability.
What Users of Old Versions Should Do
This is not a guide to circumventing the ban. It is a framework for managing the consequences of having participated in a prohibited activity.
1. Stop depositing
The funds in the account are already at risk. Adding more increases the exposure. If the platform restricts withdrawals — and the complaint record shows that it does — new deposits are unrecoverable.
2. Attempt withdrawal if funds are held
The window for withdrawal may narrow as enforcement escalates. Attempt it. Document the outcome. If the withdrawal is approved, confirm the funds have actually arrived in your bank account. A “successful” status on the platform is not the same as funds in your account.
3. Document everything
Preserve transaction records, chat logs with the agent, screenshots of the account balance, and any withdrawal requests. This is not for the platform. It is for your bank and for law enforcement if the matter escalates.
4. Contact your bank
If deposits were made via UPI or net banking, your bank is the only regulated institution in the chain. It cannot retrieve funds from an offshore operator. It can flag the transaction as disputed, close exposure on the payment instrument, and provide a record for a cybercrime complaint.
5. File a complaint if funds are involved
National Cyber Crime Helpline: 1930
Online complaint: cybercrime.gov.in
The complaint will not recover your funds in most cases. It creates a record, and records aggregate into enforcement action. Multiple state police forces have already built cases from documented complaints.
6. Do not install an old version to replace the current one
The old version does not improve the legal position. It does not improve the security position. It does not improve the functional position. It adds a copyright layer and increases the malware probability.
7. Use the browser if you must access the platform
The browser version avoids the sideloaded APK entirely. It runs inside Safari or Chrome, receives the browser’s security updates, and does not request the permissions an APK can request. It is always current because it renders whatever the platform serves.
The browser does not remove the platform’s legal exposure. It does not remove the counterparty risk. It removes the APK risk surface, which is the layer the old version makes worse.
The Structural Problem
The old-version user faces a legal and security position that is worse than the current-version user.
The current-version user has the platform’s legal exposure. The old-version user has the platform’s legal exposure plus the copyright exposure of the repackaged build. The current-version user has the platform’s malware risk. The old-version user has the platform’s malware risk multiplied by the repackaging exposure.
The old version does not provide a safe fallback. It provides an additional layer of risk on top of an already risky position.
The ban does not create these conditions. It names them. The platform was always prohibited. The accounts were always agent-mediated. The withdrawals were always discretionary. The old version was always a frozen binary from an unverified source.
The ban makes the position legible.
The Expected Value of This Decision
I return, as always, to the central question: what is the expected value of this decision?
Using an old version offers a benefit that is uncertain and probably fictional — a build that “worked before,” a feature that the current version removed, a compatibility workaround. The cost is a cumulative legal and security exposure.
The legal exposure has two layers: the PROG Act prohibition and the copyright exposure of the repackaged build. The security exposure is quantified: modded apps are ten times more likely to be flagged as malicious, and only 55% of mods were clean.
The tax obligation remains: 30% on net winnings, with no exemption.
That is an asymmetric trade: a small, uncertain benefit against a cumulative legal and security exposure. It is precisely the kind of trade that bettors systematically misprice, because the legal risk is probabilistic and the malware risk is invisible until it materialises.
A user who installs the old version and experiences no immediate consequence has not verified that the build was legal or safe. They have observed one outcome of a distribution. The tail of that distribution includes enforcement action and malware compromise.
The market is not always right. But it is rarely wrong for long. And an old-version APK of an application that is prohibited by Parliament, upheld by the Supreme Court, and actively enforced by state police forces across the country has already told you what it is. The question is whether you are pricing that information correctly.