Mein A1 (AT) (at.mobilkom.android.meina1): 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 Mein A1 (AT).
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Mein A1 (AT)
WBAG
2026-06-21
90d ago
Silent
Critical
A1's self-service app for more than five million mobile customers, holding your billing details, phone number, device ID and real-time location, hardcodes the address of its own live database directly in the app. It also allows full device backups of that same data and bundles Facebook's tracking tools, so your account and whereabouts are more exposed than a carrier handling this kind of data should allow.
at.mobilkom.android.meina1. A1 Telekom Austria AG carrier self-service app, 5M+ subscribers (billing, MSISDN, IMEI, real-time GPS). C1: Firebase key AIzaSyBYAFbLEHBtxNobOacHrvDskpevjb92A2I + DB mein-a1-prod.firebaseio.com hardcoded. H2: Vodafone NetPerform SDK with BIND_CARRIER_SERVICES + BOOT_COMPLETED. H1: allowBackup=true. Facebook AppEvents on carrier app. R1 2026-06-21, follow-up 2026-06-28, no reply.
click to expand
GDPR Art. 32(1)GDPR Art. 32(1)(a)GDPR Art. 6(1)(a)+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.