Pokemon Champions (jp.pokemon.pokemonchampions): Privacy & Security Findings

report - rfi-irfos
Skip to content

Permanent Disclosure Ledger

The discipline, demonstrated

On behalf of our research partners, we investigate publicly distributed Android and iOS apps: we decompile them, follow their code and data flows, and trace every connection to the servers it reaches. Hundreds of agents work through each app and join the technical evidence into one picture, which our specialists then review and verify.

387+
Android/iOS apps audited
Every app is decompiled at source-code level, not just scanned from outside.
1.04M+
Smali classes read
The full shipped code we have actually read, not an estimate.
262+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
970+
Weak points found
Third-party tracking we have provably found inside the binary.
567+
Endpoints investigated
Real servers and countries where data actually flows.
132+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for Pokemon Champions.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Pokemon Champions
TYO
2026-06-25
92d ago
Waiting
High
A Pokémon game aimed at children starts sending advertising and tracking data the moment the phone boots up, and Facebook's tracking code queries a device attribution ID before any parent has had a chance to give consent, so a child can be profiled inside an app their parents never actually agreed to on their behalf.
jp.pokemon.pokemonchampions. All findings re-scored under CVSS v4.0. Pre-consent Firebase+Adjust init and a combined AdMob+Adjust+Facebook attribution stack both compute MEDIUM/6.9, held at HIGH via blast-radius escalation given Pokémon's globally recognized children's-franchise audience (GDPR Art. 8). BOOT_COMPLETED autostart + data-sync foreground service and a hardcoded Firebase key correct to MEDIUM. Twelve messages sent across 83 days, nine successfully delivered, zero reply of any kind ever.
click to expand
GDPR Art. 8GDPR Art. 5(1)(b)GDPR Art. 8
Yes
Closed
Disclosure
92d 00h 00m 00s
Published
PDF

This ledger is updated in real time as companies respond. Silence is public. Severity is scored primarily by CVSS v4.0, we reserve the right to deviate based on blast radius.