Help for owners
I found out my app is leaking customer data
Short answer
Treat it as real until proven otherwise. Close the access first, keep the evidence, and change the credentials involved. Then find out what was exposed, to whom and for how long, because that decides whether you must notify customers or authorities. Do not delete logs or data in a hurry.
Does this sound like your situation?
- Someone emailed me that my users' details are visible without logging in.
- I can see other customers' data in the app or in a web address.
- A database or storage bucket belonging to my app shows up in a search or scanner report.
- Customers say they got spam or phishing that mentions my service.
- My developer says it is probably fine and I do not trust that.
Why does this happen?
A database or storage was left open
Cloud databases and file storage can be set to public by mistake or left on test settings after launch. Anyone with the address can then read them.
The app server returns more than it should
An endpoint may hand out any user's record to any logged-in user, or even to someone not logged in, because it never checks whose record is being asked for.
A secret was published
A key or password sitting in the app code or in a public repository can open the back end to anybody who finds it.
Technical detail: An API key or .env file was committed to a Git repository
Old accounts and access were never cleaned up
A former developer's login, or a shared password, is a common way in. Old logins and shared passwords need to be found and removed as part of the clean-up.
What can I do about it today?
- Do not delete anythingLogs, the exposed data and the messages you received are the evidence of what happened. Deleting them makes the investigation harder.
- Ask your developer to close the exposed part nowClosing a database or switching one feature off is better than leaving it open while you investigate. Ask for a backup of what is there first, so the evidence is kept.
- Change the passwords and keys around itCredentials that were exposed stay dangerous after the hole is closed. Your developer should list which passwords and keys were reachable and replace them.
- Write down what you knowWho reported it, when, what they saw and what you did, with times. Keep the original messages.
- Find out which rules apply to youUnder the EU's GDPR, the European Commission says a breach that is likely to risk people's rights must be notified to the supervisory authority with a deadline of 72 hours after you became aware of it, and that people must be told when the risk to them is high. Other countries have their own laws. Speak to a lawyer who knows where your customers live; I am an engineer and cannot give legal advice.
- Hold off on telling customers until you know the factsA message that is wrong or vague can do more harm. Once you know what happened and what data was involved, your lawyer can help word what you tell people and what they can do.
When should I bring someone in?
- You cannot tell whether the exposure is still open.
- The developer who built the system is unavailable or defensive.
- Payment, health, ID or password data may be involved.
How do I handle it?
- Contain itI find the open door (storage, endpoint, key or account) and close it, after taking a backup so the evidence is preserved.
- Work out the extentFrom access logs and the data itself I establish what could be reached, since when, and whether there are signs it was read.
- Rotate and clean upKeys, passwords and tokens are replaced, old logins are removed, and access moves to named accounts.
- Write it down for youA plain report of what happened and what was fixed, which you can hand to your lawyer or insurer for decisions about notification.
- Prevent the next oneI check the rest of the app for the same kind of mistake and suggest a regular review.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Do I have to tell my customers?
That depends on the law where you and your customers are, and on what data was exposed. The European Commission, for the GDPR, says people must be informed when a breach poses a high risk to them. Ask a lawyer; I can give the technical facts they need.
Can you tell me whether anyone actually downloaded the data?
Sometimes. It depends on whether logs were kept for the period. If they were not, the honest answer is that it cannot be proved either way.
Should I take the app off the store?
Usually not needed. Closing the exposed back-end part is what stops the leak. If the app cannot work safely without it, you and I decide together.
Is this the same as a hacked website?
No. A hacked website has had its files changed. A data exposure is about information that could be read. They can happen together.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
remote: error: GH013: Repository rule violations found for refs/heads/main. (a push blocked because it contains a secret)An API key or .env file was committed to a Git repositoryPossible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis.Redis logs a possible security attack from POST or Host commandsfound 12 vulnerabilities (3 low, 6 moderate, 3 high)npm audit fix runs, but the vulnerabilities are still listed