# Google Play Blocked 160 Million Spam Reviews in 2025. Here's the Full Report

> Google's own 2025 safety report says it blocked 1.75 million policy-violating apps, banned 80,000 developer accounts, and held review-bombing damage to an average half-star drop. Here's what that actually means.


**Key points:**
- Google's own blog post, "Keeping Google Play & Android app ecosystems safe in 2025," confirms over 1.75 million policy-violating apps blocked before publishing, and more than 80,000 bad developer accounts banned.
- Anti-spam systems blocked 160 million spam ratings and reviews, including both inflated and deflated ones, per the same post.
- Review bombing's average damage got held to about a half-star rating drop for targeted apps.
- Both the blocked-app and banned-account numbers are down from 2024, which saw 2.36 million apps blocked and 158,000 accounts banned.

A number most developers never see just got a real figure attached to it. How much review manipulation actually got stopped before it reached their rating.

## What Google's own report actually confirms

Per Google's own numbers, over 1.75 million policy-violating apps got blocked. Before they ever reached the Play Store. More than 80,000 developer accounts tied to harmful activity got banned too. Separately, anti-spam systems blocked 160 million spam ratings and reviews. Both kinds. The inflated kind, and the deflated, review-bombing kind.

| Detail | What Google's own report confirms |
|---|---|
| Policy-violating apps blocked | Over 1.75 million |
| Developer accounts banned | Over 80,000 |
| Spam ratings and reviews blocked | 160 million |
| Review bombing's average damage, with protection | About half a star |
| Trend vs. 2024 | Down, from 2.36 million apps and 158,000 accounts |

## Why the half-star figure actually matters

Review bombing is a real fear for any app caught in a public fight, a bad update, or a coordinated attack. Google's own figure says its systems hold the average damage to around half a star. For apps actually targeted. That's not zero impact. It's a real number showing the floor isn't as far down as an unprotected rating could fall. It's also an average. Not a promise. Some targeted apps likely see more damage. Some less.

> **Real-world scenario:** A finance app hit a short PR controversy after a feature change upset a vocal user group. A wave of 1-star reviews followed within days. The team braced for a crash like ones they'd read about elsewhere. A full star or more, overnight. Checking Google's own 2025 report later, they understood why their own rating only dropped about half a star before it recovered. The protection wasn't visible while it happened. It only showed up in hindsight. Once they had Google's own average to compare against.

## Why the numbers being down from 2024 is worth noting

Both headline figures, apps blocked and accounts banned, fell from 2024 to 2025. That's genuinely unclear on its own. It could mean enforcement caught less, because fewer bad actors tried. It could also mean detection missed more. Google's own report doesn't settle which one is true. Neither should any outside reader, without more context. Treat the drop as a real, reported fact. Not proof the ecosystem got safer, or riskier, on its own.

## What to actually do about it

1. **Don't assume a review-bombing event leaves your rating defenseless.** Google's own numbers show real protection exists. Even if it's invisible while it's happening.
2. **Still have a response plan for a coordinated attack.** Half a star of average protection isn't full immunity. Some apps likely see worse.
3. **Don't over-read the year-over-year drop in blocked apps and bans.** The report doesn't say if that's better detection or less bad activity. Neither should you, without more evidence.
4. **Watch your own rating trend closely during any real controversy.** That's the only way to tell if your case matched the average, or didn't.

[AppRankr's Rank Tracker](/rank) tracks your actual rating trend over time, the real way to see how an event like this played out for your own app specifically.

