Duc Money Transfer App Exposes Thousands of Driver’s Licenses and Passports in Major Security Failure
A significant security failure at a Canadian fintech company has put the personal data of potentially hundreds of thousands of people at risk. The Duc App, a money-transfer service, left a cloud storage server containing sensitive user documents openly accessible to anyone on the internet without a password. This incident highlights a persistent and dangerous trend in digital finance.
How the Duc App Data Breach Happened
Security researcher Anurag Sen discovered the exposed server earlier this week. The server, hosted on Amazon Web Services, was configured to publicly list its contents. Consequently, anyone with a web browser could view and download the files simply by knowing its web address. The data was stored without encryption, removing any final barrier to accessing the full contents of the files.
According to Sen’s analysis, the server contained over 360,000 files. These were not just random documents; they were the core identity verification materials submitted by users. This means the breach involved driver’s licenses, passports, and user-uploaded selfies—the very documents used to prove “who you are” in the digital world.
The Scope of the Exposed Information
Building on this, the exposure was not limited to static images. The server also held spreadsheets with detailed customer records. These files listed names, home addresses, and the specific dates, times, and details of financial transactions. The files dated back to September 2020 and were being updated daily, indicating a live, ongoing leak of personal and financial data.
Company Response and Lingering Questions
When contacted by TechCrunch, Duales CEO Henry Martinez González stated the data was on a “staging site” used for testing. However, he did not explain why real, sensitive customer information was present on a test server or why that server was publicly accessible. His claim that “all protections are in place” stands in stark contrast to the reality of the open server.
After the notification, the company made the files inaccessible. Nevertheless, a critical question remains unanswered: Martinez González would not confirm if the company has logs to determine who accessed the data or how many times it was downloaded. This lack of visibility means affected users may never know if their data was copied by malicious actors.
A Recurring Problem in Digital Verification
This Duc App data breach is not an isolated event. It fits a worrying pattern where companies aggressively collect sensitive identity documents but fail to implement corresponding security measures. Apps and websites increasingly demand passports and driver’s licenses for “Know Your Customer” (KYC) checks, yet the custodianship of this data is often shockingly weak.
For instance, last year, the social app TeaOnHer exposed thousands of similar documents required for user verification. In another case, Discord confirmed a breach affecting about 70,000 government IDs uploaded for age verification. Each incident erodes user trust and demonstrates a systemic failure to prioritize data security from the outset.
Therefore, the core issue extends beyond a single misconfigured server. It points to a flawed approach where data collection is prioritized over data protection. Companies treat sensitive ID documents as just another file type, storing them in standard cloud buckets without the stringent, additional safeguards they inherently require.
Regulatory Scrutiny and User Fallout
In response to this incident, the Office of the Privacy Commissioner of Canada has initiated contact with Duales. The regulator is seeking more information to determine its next steps, which could include an investigation and potential penalties. This regulatory attention is becoming more common as the frequency and severity of such breaches increase.
For users of the Duc App, the implications are severe. Exposure of a driver’s license or passport number creates a high risk of identity theft and fraud. These documents are difficult to change and are master keys to a person’s identity. Combined with exposed home addresses and transaction histories, the potential for targeted phishing attacks or financial fraud is significantly heightened.
As a result, affected individuals must remain vigilant. They should monitor their financial accounts for unusual activity, be wary of sophisticated phishing attempts referencing their Duc App transactions, and consider placing fraud alerts with credit bureaus. For more guidance on protecting yourself after a data breach, read our guide on post-breach security steps.
Preventing the Next Cloud Storage Catastrophe
So, what can be done to stop this cycle? First, companies must adopt a “security by design” philosophy. Sensitive data like government IDs should be encrypted at rest and in transit by default. Access should be governed by strict, role-based permissions, not left open to the public internet. Regular security audits and penetration testing are non-negotiable for any service handling financial or identity data.
Furthermore, the use of production data on staging or test servers should be strictly prohibited. These environments are inherently less secure and are frequent targets for attacks. Instead, anonymized or synthetic data should be used for all testing and development purposes. Learn more about secure development practices in our article on building secure fintech applications.
Ultimately, the Duc App data breach serves as another stark reminder. In the rush to build and launch digital services, fundamental security practices are too often an afterthought. Until companies are held fully accountable for the data they collect—both legally and in the court of public opinion—these preventable exposures will continue to put millions of people at risk.