trivago: 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 trivago.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
trivago
NASDAQ
2026-06-27
90d ago
CS deflect
High
trivago hides a security tool inside its app behind three separate layers of disguise, labeling it as an unrelated company's product, and it starts running before you have given consent. The app also ships a developer logging tool that keeps a permanent record of your network activity, something that should never have reached the version you download. After several rounds of correspondence and a missed deadline for a specific, finding-by-finding response, trivago simply stopped replying altogether.
trivago GmbH (Düsseldorf, DE). com.trivago v6.63.0. All findings re-scored under CVSS v4.0. Cleartext traffic permitted by default and a production Chucker interceptor with FOREVER log retention both reach HIGH on the computed score alone. CyberfEnd libakamaibmp.so (arm64/armeabi/x86/x86_64) in isolated process (:com.akamai.webview.process), branded as Akamai in Manifest - 3 layers of obfuscation: runtime string decryption via DBn(), native binary (statically unanalyzable), separate WebView process. Fires initOrder=100 before consent. Firebase Remote Config (57 classes) allows post-install tracking reconfiguration without APK update. cleartextTrafficPermitted=true base config - hotel search data over HTTP. ChuckerInterceptor + RetentionManager$Period.FOREVER in production binary - dev network logger with indefinite retention shipped to users. Facebook PPML IReceiverService - Meta receives cross-app signals without user interaction. AppsFlyer Privacy Sandbox endpoint (privacy-sandbox.appsflyersdk.com) + all 4 Privacy Sandbox APIs simultaneously. Firebase key AIzaSyCywqj_Xjh8zzj5oaHfuIxUxeaG6iAp8nI hardcoded. BfDI = lead authority. BCC: BfDI + DSB + CERT.at. Three consecutive content-free deflections logged: VDP Redirect (06-29) → Internal Black Box (07-01/R3) → Unfalsifiable Review (07-10/R4, RFI-IRFOS set a 48-hour deadline of 07-12 for a named, dated, finding-by-finding response). trivago never replied. after 24 days of continued silence past that deadline, RFI-IRFOS issued a formal closing notice (2026-08-05, REF: TRIVAGO-R5) treating the case as closed on trivago's side per the terms already stated in R4, not because trivago ever confirmed or denied anything. Embargo unaffected: 2026-09-25.
click to expand
GDPR Art. 5(1)(a)GDPR Art. 13GDPR Art. 32+1
Yes
Closed
Disclosure
90d 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.