On Super Bowl Sunday, February 9, 2026, KatieJakes Bar & Grill was hit with 14 one-star reviews on Yelp — all within 48 hours. On the surface it looked like an angry crowd reacting to a broadcast decision made that night. When we looked at the data behind each reviewer, the picture changed completely.
These were not frustrated customers describing a bad meal. The reviews were short, vague, and nearly identical in structure. Many accounts had no friends, no photos, and no history on Yelp. One reviewer recommended a Mexican restaurant as an alternative — not knowing KatieJakes is an American bar and grill. He had never been there. Another wrote in his own review that he "heard something about" the halftime show — admitting he wasn't present. Yelp's own rules say reviews must be based on a firsthand visit. This one wasn't, and the reviewer said so himself.
In 48 Hours
Makes Money
They Froze Comments.
We built a forensic analysis system from scratch. For each of the 14 reviewers, we pulled every measurable data point: account age, number of friends, photos, location, and the full text of every review they had ever written. We then compared their KatieJakes review against their own personal history on Yelp.
What we found repeatedly: reviewers who normally write detailed, specific, personal reviews — naming dishes, naming staff, describing real visits — suddenly posted a vague 10 to 20 word attack with no details at all. The writing didn't match their history. The voice didn't match. Something else was driving it.
15 Months Before
Your Business
Report Is
Every other reviewer in this case has an obvious tell. New account. Wrong state. No photos. Template phrasing so mechanical it reads like a form field. You can point at them and say "that's a bot" with reasonable confidence. Stephanie E. has none of those tells.
Nine years on Yelp. 87 reviews. 82 photos. She photographs her food. She names dishes. She describes specific incidents across years — a sauce spilling, a contractor failing, a T-Mobile rep giving bad information on a trade-in. She writes in a warm, personal, specific voice that is consistent across nearly a decade of genuine platform activity. By every behavioral metric available to Yelp's own recommendation software, Stephanie E. is a legitimate, established, trustworthy reviewer.
And then on February 9, 2026, she posts 33 words with no photo, no specific dish, no named staff, no visit context — and uses the word "ambiance" — a word that does not appear anywhere else in her entire review history — and closes with a political campaign slogan: "Don't support bars that don't support you."
Is Stephanie E. a real person who was socially activated — handed template language through a viral post, a TikTok, a shared thread — and deployed it without realizing she was carrying someone else's words? Or is Stephanie E. herself a sophisticated ML-trained synthetic account, built by ingesting millions of real Yelp reviews, trained to produce human-cadence writing complete with food photos and personal anecdotes, then activated on social media trigger events to provide credible cover for a bot network? There is no way to answer that question from the outside. Both scenarios are technically possible. Both are deeply concerning. And in either scenario, the word "ambiance" does not belong in that review — because Stephanie has never used it before.
This is what a hybrid network looks like at its most sophisticated. You don't need every account to be a bot. You need a trigger mechanism — a viral post, a coordinated social media thread, a shared template — that reaches real, legitimate, established users in an emotionally activated state and gives them pre-written language. Real people copy-paste. Real people parrot campaign slogans when they're angry. The bots handle the volume. The real humans — or the ML-trained accounts that are indistinguishable from real humans — handle the credibility. The result is a network that Yelp's own detection systems are not designed to catch, because the accounts are genuine. Only the language is coordinated.
If you are running this operation and you are technically sophisticated, this is exactly how you build it. You train a language model on years of authentic Yelp reviewer behavior. You generate accounts that write, photograph, and behave like real people over months and years. You seed your template keywords into viral social content and let the activation happen organically. Nobody sends a traceable instruction. Nobody writes an email that says "attack this business." The operation runs through the noise of genuine human outrage and leaves no clean forensic signature — except the word "ambiance," appearing in the same review wave, across the same businesses, across 15 months, in accounts that have never used it before.
That is the finding. It cannot be proven conclusively from the outside. It requires discovery — source code, account creation metadata, IP clustering, behavioral telemetry — the kind of evidence only Yelp possesses and has successfully protected as trade secret. What this report can do is document the signal clearly enough that someone with the authority to compel that discovery understands exactly what they are looking for.
VIEW STEPHANIE E. FULL ENTITY REPORT →| ENTITY | NAME | LOCATION | VIOLATIONS | SPECIFICITY | WORDS | ANOMALY | CONFIDENCE | REPORT |
|---|---|---|---|---|---|---|---|---|
| david-s | David S. | Vincent, CA | 4 | 0 | 18 | YES | HIGHEST — 95%+ | VIEW → |
| alexis-t | Alexis T. | West Covina, CA | 3 | 0 | 32 | YES | VERY HIGH | VIEW → |
| andrea-s | Andrea S. | Azusa, CA | 3 | 4 | 21 | YES | MEDIUM | VIEW → |
| angela-g | Angela G. | Baldwin Park, CA | 3 | 1 | 24 | YES | MEDIUM-HIGH | VIEW → |
| denise-p | Denise P. | Montebello, CA | 3 | 1 | 18 | YES | HIGH | VIEW → |
| jesse-b | Jesse B. | Los Angeles, CA | 3 | 1 | 17 | YES | MEDIUM-LOW | VIEW → |
| pete-m | Pete M. | Ontario, CA | 3 | 2 | 48 | NO | VERY HIGH | VIEW → |
| victoria-f | Victoria F. | El Rancho, Pico Rivera, CA | 3 | 1 | 21 | YES | HIGH | VIEW → |
| brandon-h | brandon h. | La Puente, CA | 2 | 2 | 21 | YES | VERY HIGH | VIEW → |
| brandon-p | Brandon P. | Upland, CA | 2 | 0 | 26 | YES | MEDIUM-LOW | VIEW → |
| diana-g | Diana G. | Ontario, CA | 2 | 0 | 16 | YES | MEDIUM | VIEW → |
| mo-b | Mo B. | Chino, CA | 2 | 0 | 25 | YES | HIGH | VIEW → |
| olga-r | Olga R. | Corona, CA | 2 | 0 | 19 | NO | HIGH | VIEW → |
| stephanie-e | Stephanie E. | Azusa, CA | 2 | 1 | 33 | YES | MEDIUM | VIEW → |
Three additional businesses were attacked by overlapping accounts from the same bot network. These entities use a different data structure and are displayed as reference summaries. Full reports are linked below.
CRITICAL SMOKING GUN — Pre-attack bot network evidence. Courtney R. posted Nov 20, 2024 (15 MONTHS BEFORE Super Bowl attack on Feb 9, 2026) using the EXACT SAME 'ambiance' keyword that appears in Feb 2026 coordinated attack reviews. This proves the bot network was already active and testing Katie Jakes OVER A YEAR before the Super Bowl incident. This is not a reactive attack — this is a long-running coordinated campaign.
Every forensic entity report, business document, and reference file in this case.