ÖBB Tickets (at.oebb.ts): 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 ÖBB Tickets.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
ÖBB Tickets
Private
2026-06-20
91d ago
CS deflect
Critical
Austria's federal railway ticketing app hardcodes an access key directly into the software and has no protection against a fake server intercepting your connection. It also embeds a ticketing SDK that routes your location and journey data through infrastructure touching both Chinese payment processing and US servers, a cross-border data path never disclosed to passengers.
at.oebb.ts. Hardcoded Firebase key + no TLS certificate pinning on Austria's federal railway ticketing app. Embeds the FairTiq SDK, which routes passenger location and journey data through infrastructure touching both Chinese UnionPay processing and US-based servers - a cross-border data flow for Austrian public transport passengers with no equivalent disclosure. DPO responded 2026-06-30 acknowledging the report.
click to expand
GDPR Art. 25(1)GDPR Art. 32(1)(a)GDPR Art. 44+2
Yes
Closed
Disclosure
91d 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.