# Your "Private" AI Chatbot Just Leaked 300 Million Secrets — 25M Users, Zero Passwords Needed **URL:** \ **Category:** News & Articles\ **Tags:** hacking, privacy, tips-tricks, ai, news\ **Created:** [Août 6, 2026, 1:43 UTC](https://onehack.st/t/your-private-ai-chatbot-just-leaked-300-million-secrets-25m-users-zero-passwords-needed/324488 "2026-08-06T13:43:13Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![PlayBoy83](https://onehack.st/user_avatar/onehack.st/playboy83/32/164314_2.png) [@PlayBoy83](https://onehack.st/u/PlayBoy83)\ **Post date:** [Août 6, 2026, 1:43 UTC](https://onehack.st/t/your-private-ai-chatbot-just-leaked-300-million-secrets-25m-users-zero-passwords-needed/324488/1 "2026-08-06T13:43:14Z")
# 🔓 Your “Private” AI Chatbot Just Spilled 300 Million Secrets — Meth Recipes And Suicide Notes Included _One typo in a database setting. 25 million people’s darkest 3am questions, sitting there for anyone with a browser._ **300,000,000 messages. 25,000,000 users. 0 passwords needed to read them all.** The app is called [Chat & Ask AI](https://www.malwarebytes.com/blog/news/2026/02/ai-chat-app-leak-exposes-300-million-messages-tied-to-25-million-users) — one of the top-grossing AI apps on the App Store. A researcher poked its backend and the whole diary fell open. No lock. No key. Just… open. ![Chatbot Leak GIF](https://media.giphy.com/media/sIIhZliB2McAo/giphy.gif) > **🧩 Dumb Mode Dictionary** > > | Scary Word | What It Actually Means | > | --- | --- | > | **Firebase** | A free-ish Google service that stores an app’s data. Easy to set up. Also easy to set up _wrong_. | > | **Misconfigured database** | Somebody left the “who can read this?” switch flipped to _everybody_. Like a bank vault with the door propped open by a chair. | > | **Backend** | The part of the app you never see — where all your chats, settings, and history actually live. | > | **Responsible disclosure** | When a good-guy hacker finds a hole, tells the company quietly first, and gives them time to fix it before going public. | > | **Metadata** | The “data about your data.” Not just what you typed — but when, from which AI, under what nickname. Often more revealing than the message itself. | > **📋 What actually happened (the short version)** > > - **Chat & Ask AI** , made by a company called [Codeway](https://codeway.co/), is a chatbot app that pipes you to models like GPT and Claude. > - In **January 2026** , an independent researcher who goes by **“Harry”** was poking around and found the app’s [Firebase](https://firebase.google.com/) storage was wide open. > - No login. No password. Anyone who knew where to look could read **the entire thing**. > - He reported it to Codeway on **January 20, 2026**. To their credit — they patched it across all their apps within _hours_. > - But “patched in hours” doesn’t tell you how long it was open _before_ Harry found it. Nobody knows. That’s the scary part. > **📊 The receipts (the numbers that matter)** > > The data shows this isn’t a “few thousand users” oopsie. Here’s the scale: > > | Metric | Number | > | --- | --- | > | Private messages exposed | ~300 million | > | Users affected | 25+ million | > | Password required to read it | None | > | Time company took to fix | A few hours | > | Time it was _actually_ exposed | Unknown ⚠ | > > **But here’s the thing nobody mentions:** the raw message count isn’t even the worst bit. It’s _what_ was in the messages. Researchers found people asking [how to paintlessly end their lives, how to write suicide notes, how to cook meth, and how to hack into other apps](https://www.enterprisesecuritytech.com/post/ai-chat-app-leak-exposes-hundreds-of-millions-of-private-conversations-researcher-says). People treat these bots like a priest who can’t judge them. Turns out the confession booth had no walls. > **🤔 The counter-argument (before you panic)** > > Let me play fair for a second, because I always do. > > - **The company acted fast.** Hours to patch is genuinely good. A lot of firms take _months_. > - **A good-guy found it first.** “Harry” did responsible disclosure — he didn’t dump it on a dark-web forum for money. > - **No proof criminals grabbed it.** As far as anyone’s said, there’s no confirmed mass-theft. The hole existed; whether the wolves walked through it is unproven. > > **But here’s the thing nobody mentions:** “no _proof_ it was stolen” and “it wasn’t stolen” are not the same sentence. An open Firebase bucket doesn’t leave a guest log. If ten people quietly copied it in December, nobody would ever know. The data shows the _door_ was open — it can’t show you who walked in. Treat your chats as if a stranger read them, because one might’ve. > **🕰️ How we got here (the pattern)** > > This is not a freak accident. It’s the [most common cloud screwup on Earth](https://en.wikipedia.org/wiki/Data_breach). Misconfigured databases have leaked data from [millions of records over and over](https://www.idstrong.com/sentinel/chat--ask-ai-data-breach/) — retailers, hospitals, dating apps, you name it. > > Why AI apps keep doing it: > > - They ship _fast_ to ride the hype. Security is the thing you “fix later.” > - Firebase is the default because it’s cheap and quick — and its default rules are notoriously easy to leave loose. > - Nobody reads an AI app’s privacy policy. Be honest — did you? > > The lesson: an app being on the App Store’s top-grossing list tells you it makes money. It tells you **nothing** about whether it’s locking your data. #### Cool. So My 3AM Robot Therapist Is A Snitch… Now What The Hell Do We Do? (ಠ\_ಠ) ![Detective Magnifying Glass GIF](https://media.giphy.com/media/t4tZuZNCrBtRSJAoB0/giphy.gif) Here’s where the analyst part ends and the hustler part begins. Every leak is a mess for the users — and an _opening_ for the fast people. Five plays. Each one legal-ish, each one doable tomorrow with a laptop and zero dollars. > **🔦 The Open-Door Auditor** > > Misconfigured databases don’t announce themselves — but there are free tools that _sniff them out_. Learn to run a basic scan for open [Firebase](https://firebase.google.com/docs/rules) and cloud-storage buckets, and small app-makers will pay you to check theirs _before_ a “Harry” finds it publicly. > > You’re not breaking in. You’re the guy who knocks and says “hey, your back door’s unlocked” — then hands them an invoice. > > 🧠 _Example:_ A 23-year-old self-taught coder in Lagos, Nigeria runs [free open-source scanners](https://github.com/topics/firebase-security) against indie AI apps he finds on Product Hunt, sends a polite “here’s your hole + here’s the fix” email, and charges $150 a report. Landed 6 clients in his first month. > > > 📈 **Timeline:** First paid audit in ~2 weeks once you can read the tool output. Slows down in ~4-6 months as you’ll want to niche into one platform to stay credible. > **🧾 The Breach Translator** > > Regular people hear “300 million messages leaked” and freeze — they have no idea if _they’re_ in it or what to do. Be the calm human who turns scary security news into a plain-English “here’s what to do in 5 steps” checklist for one specific app or community. > > Package it as a cheap PDF or a pinned post. When the _next_ breach hits (and it will), you’re already the go-to name. > > 🧠 _Example:_ A stay-at-home mom in the Philippines writes dead-simple breach-response guides (“Was your data leaked? Do THIS”) for non-techy Facebook groups, and monetizes with a $5 [Gumroad](https://gumroad.com/) checklist + affiliate links to a password manager. Quiet, steady, boring money. > > > 📈 **Timeline:** First sales within days of any big breach making headlines. Evergreen — breaches never stop, so this doesn’t really burn out. > **🪞 The Local-First Alternative Curator** > > The whole reason this leak stings is your chats went to _someone else’s server_. There’s a growing crowd that wants AI that runs on their _own_ machine so nothing leaves the room. Most people can’t set that up. You can be the one who does. > > Learn to install a [local, offline chatbot](https://ollama.com/) (runs on a normal laptop, no internet needed for chats) and sell the setup + a simple guide. > > 🧠 _Example:_ A college student in Brazil offers a “private AI on your own laptop” setup service over [Discord](https://discord.com/) — walks people through installing [Ollama](https://ollama.com/) + a friendly interface, charges $30 a session. Privacy-nervous freelancers eat it up after every leak headline. > > > 📈 **Timeline:** First client in ~1 week. Demand spikes hard right after any AI-privacy scandal, then cools — ride the news cycle. > **🗂️ The Privacy Scorecard Vault** > > Nobody reads privacy policies. But somebody could read them _once_, for the top 100 AI apps, and turn each into a simple traffic-light score: 🟢 stores nothing / 🟡 stores chats / 🔴 leaks-waiting-to-happen. That single cheatsheet becomes the thing everyone links to. > > First-mover with a clean, comprehensive comparison table = the [SEO](https://en.wikipedia.org/wiki/Search_engine_optimization) anchor everyone else quotes. > > 🧠 _Example:_ A data-analyst in India built a public [Notion](https://www.notion.so/) page rating AI apps’ privacy in plain language, drove traffic with Reddit posts on [r/privacy](https://www.reddit.com/r/privacy/), and monetizes with a “detailed report” paywall + newsletter. The list itself is free; the depth costs. > > > 📈 **Timeline:** Traffic builds over 4-8 weeks as it gets shared. Long-lived if you keep it updated — stale = dead, so it’s real work. > **⏳ The Patch-Window Cleanup Crew** > > When a breach goes public, there’s a frantic 2-4 week window where affected companies are _desperate_ for help and everyone’s shouting. That’s when you offer a done-for-you “incident cleanup” package to small app teams: draft the user apology email, write the FAQ, set up the fix checklist. > > You’re selling _calm_ during their worst week. People overpay for calm. > > 🧠 _Example:_ A freelance writer in Poland pitches tiny app studios right after breach news with a “we’ll handle your user comms in 48 hours” offer, using free templates she built once. One panicked founder = $400 for two days of writing. > > > 📈 **Timeline:** Land your first gig within the same week as a breach. It’s feast-or-famine — dead between scandals, so pair it with the evergreen plays above. > **🛠️ Follow-Up Actions** > > | Move | Do This Today | > | --- | --- | > | 🔍 Check if you’re exposed | Search your email on [Have I Been Pwned](https://haveibeenpwned.com/) | > | 🔒 Lock the basics | Turn on 2-factor everywhere + get a [password manager](https://bitwarden.com/) | > | 🤖 Go local | Try [Ollama](https://ollama.com/) for chats that never leave your laptop | > | 📚 Learn the tools | Read [Firebase security rules docs](https://firebase.google.com/docs/rules) (free) | > | 🗣 Join the crowd | Lurk [r/privacy](https://www.reddit.com/r/privacy/) to spot the next breach early | **⚡ Quick Hits** | You Want To… | Do This | | --- | --- | | 🕵 Know if you leaked | Check [Have I Been Pwned](https://haveibeenpwned.com/) right now | | 🔐 Stop reusing passwords | Set up [Bitwarden](https://bitwarden.com/) (free) tonight | | 🤐 Keep chats truly private | Run a [local AI](https://ollama.com/) — nothing hits a server | | 💸 Turn this news into money | Pick ONE hustle above and take step one tomorrow | | 📖 Understand the screwup | Read the [Malwarebytes writeup](https://www.malwarebytes.com/blog/news/2026/02/ai-chat-app-leak-exposes-300-million-messages-tied-to-25-million-users) | _Your chatbot doesn’t have a conscience — but it does have a database. And this week, that database had no lock._