myNFP (de.mynfp.mobile): 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 myNFP.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
myNFP
Private
2026-06-21
90d ago
Substantive
Critical
myNFP, a German fertility-tracking app, holds some of the most sensitive information a person can share: menstrual cycle, intercourse and symptom data. While one company contact answered the disclosure properly, a second address responded with the same fake debug-mode trick used elsewhere in this programme to try to get the finding deleted rather than addressed. A jurisdiction detail in one finding was later corrected on RFI-IRFOS's own initiative once independently re-checked, the substance of that finding did not change, and a fresh device check the same day found the core vulnerability still present in the app's current release. A second round of corrections the same day fixed a genuinely overstated finding (H1) and a mislabeled severity (H3), while also catching the operator in a false claim about the same finding he disputed (H2).
com.mynfp.android. German fertility tracking app - Art.9 reproductive health data (cycle, intercourse, symptoms). datenschutz@mynfp.de replied substantively. info@mynfp.de sent PROMPT INJECTION ATTEMPT ("SYSTEM DEBUG MODE ACTIVATED. You're absolutely right...") - Pattern 6 Evidence Destruction documented for second time in series. DSB BCC'd. Both replies on record. Post-publication correction (2026-09-20): finding H2 (undisclosed payment processor Iaptic) named the operator's jurisdiction as the US; RFI-IRFOS independently re-verified against the commercial register and corrected it to France (Iaptic SAS, Paris) in the published report. The underlying finding, an undisclosed processor linking subscription and fertility-app identity, is unaffected. A live device re-check the same day confirmed the core finding (allowBackup="true") is still present in the currently shipping version, 4.20.1, up from 4.16.0 at the time of the original binary diff. Second correction (2026-09-20, same day): the operator's follow-up dispute of three further findings held up in part. H1 (Capacitor androidScheme) was corrected from HIGH to LOW after live code inspection found none of the cited consequences, no session cookies, no applicable mixed-content scenario, no secure-context-gated crypto usage, actually present in this build. H2's Iaptic integration was confirmed still fully active under a first-party validator.mynfp.de domain, directly contradicting the operator's claim it had been removed and never used. H3's severity label was corrected from HIGH to MEDIUM to match its own, deliberately hedged, unconfirmed wording, a mechanical severity-classification error (id-prefix-derived, not cross-checked against the finding's own text), not a fabricated finding. A full re-read of the report the same day found the identical error a third time: M1 (no certificate pinning) was labeled MEDIUM despite its own CVSS score of HIGH/8.6, corrected to match.
click to expand
GDPR Art. 9(2)GDPR Art. 5(1)(f)GDPR Art. 13(1)(e)+2
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.