Freecash (com.freecash.app2): 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 Freecash.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Freecash
Private
2026-06-22
94d ago
CS deflect
Critical
Freecash's support team replied quickly and politely four times, but never once addressed a single one of the eight specific problems found in the app, including one that lets outside companies see every app on a person's phone, not just Freecash. When asked three direct yes-or-no questions twice, the company did not answer either time.
com.freecash.app2. All eight findings re-scored under CVSS v4.0: C2 (PACKAGE_USAGE_STATS combined with confirmed adjoe and CleverTap device-wide usage-stats queries) reaches CRITICAL on the computed CVSS score alone, no editorial escalation needed. C1 and three HIGH findings correct down to MEDIUM. Two findings (a dormant geofence module, a 2014-era minimum OS version) are classified OBSERVATIONAL. Freecash replied four times, faster than almost every other target this year, but every reply was an identical, content-free forwarding confirmation naming no finding. Three specific yes-or-no questions about the two CRITICAL findings, posed 2026-08-18 and repeated 2026-09-05, received no answer at all, not even a fifth forwarding confirmation. 48 days of total silence as of publication.
click to expand
GDPR Art. 32(1)(b)GDPR Art. 5(1)(b)GDPR Art. 6(1)+2
Yes
Closed
Disclosure
94d 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.