Chicken Road has no app, no website and no notifications: 84 surfaces use its name
For press and research
This week, a person who has never played received a phone notification titled “Chicken Road | PLAY NOW”; tapping it opened a website showing a crash game with betting amounts. The game could not have sent it: it is supplied to casinos only, with no consumer channel at all. So we counted the surfaces that use its name — and visited each one. There are 84.
- 84 surfaces catalogued on 29 October 2026, in seven families — from the app listing to the APK mirror site — 72 of them verified by a direct visit.[1]
- The fact that settles it: the game is supplied to casinos only; under its name there is no consumer app, no official website and no notification service.
- The escalation the verification found: one site presents itself, in the first person, as the developer's own official site; eight domains call themselves the sequel's official site, with licence numbers that do not agree with each other.
- The notification mechanism is confirmed in the surfaces' own words: three visited sites sell the APK install and the push notifications that come with it as one package.
The complete register — all 84 surfaces, name and address — is shared with journalists and researchers on request, through the Press page.
The short version: the census in 5 numbers
Where the numbers come from: a census run on 29 October 2026 across the app stores, the APK mirror sites and web search, followed by a surface-by-surface verification — every surface counted was visited directly, and 21 further surfaces, found during the verification, joined the catalogue. There is one counting rule: a surface counts if it uses the game's name without being the developer that supplies it to casinos, or a casino that distributes it. Pages that route visitors to casinos are counted separately (the country-targeted pages) from surfaces that present themselves as the game itself, its official site or its download source. Every line of the register carries its evidence grade: 72 surfaces verified by a direct visit, 10 recorded from search results, 2 not openable on census day. The full method is published below; the complete register is shared on request with journalists and researchers.[1]
The incident: a notification on the phone of someone who never played
The starting point is a public report published this week. Its author describes a phone receiving a notification titled “Chicken Road | PLAY NOW”, although they had never signed up for anything. Tapping the notification opened a website showing a crash game with betting amounts. Screenshots were attached to the report, and its author asked whether this was an advertisement or something suspect. The same report was reposted in a second help space, with no answer that settles it.[2]
What the report establishes: the type of destination (a betting site displaying the game) and the format of the message (a title in the game's name, a “PLAY NOW” call to action). What it does not establish: the exact surface that sent the notification — it is not named in the report, and it cannot be determined from outside. Our reading: the “an ad inside the app” hypothesis is the weakest of the available explanations: an ad displays inside an app's feed; it does not arrive as a system notification on a phone's screen.
The incident is not isolated in its mechanics. Its ingredients are sold openly by surfaces this census counted — and since the verification, the pairing is written out in plain words on three of them, visited one by one: one APK install page states that the app sends “push notifications that alert you to special promotions and daily rewards”, another promises the installed app “gives you push notifications for bonuses”, a third presents “optional notifications” as a feature of its announced app. This week's notification is the finished form of an apparatus the census below counts piece by piece.
The base fact: the game has no consumer channel
Chicken Road is a business-to-business product: its developer delivers it to online casinos, which integrate it into their catalogues. The game is played only inside a casino's lobby, it is paid for in the currency of the casino account, and it appears there under its developer's name in the provider filter.[3] Under the game's name there is therefore no consumer app, no downloadable file, no official website and no notification service.
That sentence is the complete test. Anything that presents itself as the game's app, its install file or its official site was built by someone other than the developer. And a casino-lobby title has no channel to the phone of a person who does not play it: the game itself materially cannot send the notification described above.
The fact is corroborated by the counted surfaces themselves: several pages that use the game's name to attract visitors state in writing that no official app exists and that files offered elsewhere do not come from the developer. Even the ecosystem that lives off the name acknowledges it, when it addresses readers it wants to reassure.
The census: 84 surfaces, seven families
| Family | Surfaces | What the surface asks the visitor to do |
|---|---|---|
| Android store — listings under the game's name | 25 | Listings documented one by one in the largest Android app store — where a single search returns around fifty results under the game's name (about 17 exact titles, money-promising variants, and many listings under the sequel's name). One verified listing claims “official” app status in its title, while its publisher is an unrelated studio that publishes several more listings under the same name; several listings share near-identical description text built around the same official-app claim.[4] |
| Standalone websites | 21 | Present themselves as the game, its “official” site or its download source: “play” buttons, APK download sections. One of them displays a scrolling ticker of “recent wins” naming winners and amounts; several publish release dates and payout rates that contradict the game's published data — one single site shows four different payout rates across its own sections. |
| APK mirror sites | 14 | Downloadable packages outside any store: two listings claim “official” status in their titles, one of them filed in the casino category; a 66.3 MB package is titled with the game's name followed by the words “real money”. Three mirrors state themselves that the package they offer for manual install is no longer present in the store. |
| Country-targeted pages | 13 | Guides and affiliate pages published under the game's name, one country at a time: step-by-step instructions for installing an APK outside the store, bonus promises, routing to casinos. |
| Second app gallery | 3 | APK listings under the game's name on a third-party gallery; one imitates the functions of a betting app (autoplay, session history, daily bonus) and is rated 1 out of 10 there by its users. |
| Clones embedded in apps | 2 | Casino or arcade apps in the other major mobile store (rated 18+, in-app purchases) that embed a clone of the game as one mini-game among others. |
| Reports and alert pages | 6 | Coverage of the phenomenon, counted separately: this week's report and its repost, plus third-party pages cataloguing the tactics — “earn money” apps that demand a payment or set unreachable withdrawal thresholds, “guaranteed winnings” promotions on social media. |
The fate of one listing illustrates the whole mechanism: one of the catalogued apps, tracked by a listing-statistics service at 30,333 downloads, has since been removed from the store — and its permission list, captured by that service, included sending notifications and access to the camera. Removed from the store does not mean removed from phones: an installed app keeps its permissions.
A neighbouring layer exists, and this census counts it at zero rather than estimating it: the game's “predictors” — signal robots sold by monthly subscription and app titles pairing the game's name with the word “predictor”. The pattern is documented by third-party pages, but no standalone listing of this type was independently retrieved on 29 October 2026; the register therefore leaves it at 0, and says so.
The escalation: impersonating the studio, not just the game
The first pass of this census counted surfaces borrowing the game's name. The verification found surfaces borrowing its developer's identity. One step further, a site speaks in the developer's own voice for a national market: a playable game catalogue in demo form, and a licence claim displayed as its own. That is no longer a borrowed game name; it is an assumed studio identity.
The game's sequel concentrates the densest form of the phenomenon: at least eight domains each title themselves the sequel's official site. Two of them, opened and read, display licence numbers that do not agree with each other — and release dates of March and June 2023, although the sequel was released on 15 April 2025.[3] The first game's “official” sites do the same at their scale: release dates announced in July and November 2023, for a game released on 4 April 2024; and, as noted above, four different payout rates across the sections of a single site, none equal to the published 98%.[3]
These contradictions are the verifiable part of the phenomenon — and its signature. A single official operator cannot have two licence numbers, three release dates and four payout rates. Each of these figures is checkable by the reader against the developer's product pages cited in the references; their disagreement is the cleanest measure of what the census counts.[1]
The mechanism: a permission, not a message from the game
Two channels can place such a notification on a phone. The first is the “push” permission granted to a website: a visitor taps “Allow” one day — often on a page that asks for it in order to “continue” — and the site can then write to them through the browser, even when it is closed. The notification arrives in the phone's notification shade, where it blends in with the apps' own; its owner attributes it to the app they were using, while it came from the browser. The second channel is an installed app — a clone downloaded outside the store, or a “web app” added to the home screen — holding its own notification permission.[5]
Both channels are permission mechanisms, not intrusions: somewhere, a tap granted a right to write, and that right outlives everything else — the site being closed, a casino account being deleted, the app being removed from the store, time. That is why these notifications “keep coming” for the people reporting them, and why they stop outright when the permission is revoked in the device's settings.
What nobody can do from outside: say which precise surface sent a given notification. This week's report names no address, and its screenshots could not be retrieved. The answer is on the device itself — every system lists, surface by surface, who holds the write permission. Our help page (in French) describes the complete procedure, system by system: identifying the sender of these notifications and revoking its permission.
What these surfaces get from you
Every family in the census takes something specific, and the taking is the point of the apparatus. The tap on "Allow" hands over a channel: a persistent push subscription inside the phone, which carries with it the technical identifiers of the device and the browser. That subscription outlives the visit, does not expire on its own, and can be used indefinitely by whoever holds it — to write today, in six months, or never, at a rhythm of their choosing.
And the holder changes. In the push-traffic trade, subscriber bases are a commodity: they are routinely rented and resold between advertisers, as standard practice in that market. The consequence is concrete: the message that arrives months after the tap may come from a buyer of the base, not from the site the tap happened on — blocking "the site" says nothing about who will write tomorrow, because the asset sold is not a message, it is the channel.
Installing an APK file hands over permissions — and the permissions are the exposure. The census documents this without extrapolation: the catalogued app that has since been removed from its store carried, in its captured permission list, the sending of notifications and access to the camera. Depending on the build installed, the same mechanism can ask for contacts, storage or the camera: the user hands over whatever the list contains, at install time, and an installed app keeps those rights for as long as it stays on the device.[6]
Signing up on a routing page hands over contact details. The name and phone number entered for a "bonus" enter affiliate lead flows — flows in which the lead is the product that gets sold on: it passes from one operator to the next along the chain, and every new hand is a potential sender of calls and messages the person never requested from them.
Our analysis: an impersonation of distribution, measured on our own counts
Everything above is the census itself. What follows is our analysis, and it mixes three things that we distinguish at every step: the census's findings, credited to it and cited; our calculations on its published tables, flagged as ours, with their margins; and our interpretations, labelled as such. The shares below are computed on the census's exact counts and rounded to one decimal; the counts are given beside every share so the arithmetic can be re-run.
Distribution first: 52.4% of the surfaces are install channels. Our calculation on the family table: the surfaces whose function is to get something installed — Android store listings (25), APK mirror sites (14), the second app gallery (3) and clones embedded in apps (2) — total 44 surfaces out of 84, or 52.4%. The surfaces that live in the browser — standalone websites (21) and country-targeted pages (13) — total 34, or 40.5%. Inside the install channel itself, the largest family weighs only 29.8% of the total (25 of 84), and 17 of the 44 install surfaces, or 38.6%, sit outside the main store — mirrors and a third-party gallery. Our reading: a removal from that main store does not reach them.[1]
The core of the phenomenon claims to be the game. The census counts 65 surfaces that pass themselves off as the game or its official channel; our cross-check by family recovers that total exactly — 25 + 21 + 14 + 3 + 2 — and sets it against the whole: 65 of 84, or 77.4%. The rest splits between routing to casinos (13 country-targeted pages, 15.5%) and coverage of the phenomenon (6 reports and alert pages, 7.1%), which does not exploit it. More than three quarters of the counted surfaces therefore do not comment on the game's name: they assume it.[1]
The official-marker test: zero agreement. We re-read, in the census's findings, every marker of official status a reader can check against a public source: the announced release dates (July and November 2023 for the first game, March and June 2023 for the sequel), the licence numbers displayed by two of the sequel's "official" sites, and the payout rates published across the sections of a single site (four values). The result of our cross-check: none of the four dates agrees with the developer's published dates — 4 April 2024 for the first game and 15 April 2025 for the sequel[3] —, the two licence numbers contradict each other, and none of the four payout values equals the published rate of 98%[3]. The announced dates even predate the real releases: by about five and nine months for the first game, and by about twenty-two and twenty-five months for the sequel. Dates, licences, rates: three types of marker checked, zero agreement. Our reading: it is the most concentrated form of the phenomenon our counts bring out.[1]
Verification produced a quarter of the catalogue. The first sweep had recorded 63 surfaces — 84 minus the 21 added by the second pass, on the counts published above; surface-by-surface verification therefore added 25.0% of the final catalogue. The floor can also be measured inside the main store: the 25 listings documented one by one represent about half of the roughly 50 listings a single search there returns. Our reading: a one-pass census, without verification, would have published a total a quarter below the documented floor — and that floor remains, as stated, a floor.[1]
The APK + notifications pairing: rare in words, central in mechanism. Three visited surfaces — 4.2% of the 72 surfaces verified by a direct visit — explicitly sell, in their own words, the file install and the notifications that come with it.[1] That is a small share, and it is the only mechanism in the census documented end to end by the surfaces themselves: install, permission, persistent channel. Our reading: the rarity of the written pairing does not measure the rarity of the real pairing — it measures what the surfaces choose to advertise; the report that triggered this census shows a notification of this kind at work, on the phone of someone who never played, without any surface having had to write the pairing down.[2]
What this census does not say
84 is a documented floor, not a total. The catalogue documents 84 surfaces one by one; the first search page of a single store already shows around fifty listings under the game's name, not all of which were opened — they are recorded as a count observation, not as register lines. A further cluster of same-name listings on a download platform is recorded the same way: observed, not counted line by line.
Evidence grades are displayed, line by line. 72 surfaces verified by a direct visit on 29 October 2026; 10 recorded from search results (among them two domains known only from the third-party pages that call them “official”, with no direct visit); 2 not openable on census day — the two publications of the triggering report, whose text rests on the alert excerpts received by the newsroom. A few visited pages were read through search-engine archive copies dated 2026 and flagged in the register; a same-day live-browser check would raise them to the top grade.
Counters are those the surfaces themselves display. Store pages show neither download counters nor permission lists in the retrieved text: in the register, that data exists only where a listing-tracking service or a mirror displays it — the register's one complete permission list comes from that tracking service.
Part of the census is name collision. A few exact-name apps — a puzzle game, an arcade clone — may be animal-crossing-the-road games rather than exploitations of the casino name; the register keeps them because they occupy the exact name in the store, and flags them as the census's weak tier.
The triggering incident remains partly read. The report's text: yes, through the received excerpts. Its comments, screenshots and reaction counts: not retrievable on census day. The incident's reach is therefore not quantified — and the notification's sender remains, as stated, indeterminable.
Methodology
The complete register. The complete list of the 84 surfaces — name, address in plain text, publisher where shown, and what each surface asks the visitor to do — is not published as a download: it is shared with journalists and researchers who ask for it, through the Press page, free to reuse with attribution (CC BY 4.0).
Are you a journalist or a researcher who wants an extract, a particular format, or a comment on this data? Contact the newsroom via the Press page. We are an independent publication; this study is self-funded and its data is free to reuse with attribution. The game's developer neither reviewed nor approved this analysis before publication.
Frequently asked questions
Does the game send notifications?
No. No notification service exists under the game's name: a notification with that title comes from a website the browser allowed to write, or from a clone app installed on the device.
Is there an official app for the game?
No. The game exists only inside the lobbies of the casinos that distribute it; any file offered for download under its name was built by a third party.
Where did this week's reported notification come from?
It cannot be determined from outside: the report names no surface. The two possible channels are a push permission granted to a website, or an installed app; the answer is visible in the device's settings, which list every holder of the permission.
Are 84 surfaces the total?
No: it is the total documented line by line. A single search of the main store returns around fifty listings under the game's name on its first page alone; not all of them were documented individually, and new surfaces appear without the old ones always disappearing.[1]
How do I stop these notifications?
By revoking the sending surface's permission: our help page (in French) walks through the procedure system by system — desktop browser, Android phone, iPhone, installed app: notifications in the game's name: why they keep coming, and how to cut them off.
References
- Chicken Road Productions — Census of the surfaces using the Chicken Road name, 29 October 2026: counting rule, two-pass sweep protocol, families and evidence grades, published in the "Methodology" section of this study. The line-by-line register is held by the newsroom and shared with journalists and researchers on request via the Press page; it is not published as a download, and this study names no counted surface. Methodology ↑
- The triggering report: a user's public report published on 28–29 October 2026, reposted in a second help space. Text read through the alert excerpts received by the newsroom; screenshots, comments and reaction counts not retrievable on census day — the incident's reach is not quantified, and no address is named in it. ↑
- InOut Games — the developer's official product pages: "Chicken Road" (RTP 98%, released 04.04.2024) inout.games and "Chicken Road 2.0" (RTP 95.5%, released 15.04.2025) inout.games, consulted on 30 October 2026. ↑
- Google Play — "Impersonation", Developer Program Policies: Google Play does not allow apps that mislead users by impersonating another developer, company or app, including titles claiming "official" status without the necessary rights. support.google.com ↑
- MDN Web Docs — "Push API": a web application can receive messages pushed from a server whether or not it is in the foreground, or even currently loaded; each push subscription is unique to a service worker and lives with the permission granted. developer.mozilla.org ↑
- Android Developers — "Request runtime permissions": sensitive permissions are requested at runtime, and the user can grant and later revoke them in the device settings; an installed app keeps the permissions granted to it until they are revoked. developer.android.com ↑