101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

483
active users

#dataleak

2 posts2 participants0 posts today
Dissent Doe :cupofcoffee:<p>So yesterday, I emailed a state court system that appears to be linked to the exposed data I mentioned recently and that the host notified on or about July 28. </p><p>No reply was received.</p><p>Today, I sent a contact form message to the lawyer for a juvenile whose records were sealed. Sealed, except 11 of them were exposed to anyone who can access the data. I told him what was going on and suggested he contact the court and tell them to get the data secured. </p><p>No reply was received.</p><p>Today, I sent an email to the judge who ordered the juvenile's records sealed and I cc:d the district attorney. I gave them the juvenile's name, case number and that I could see all the sealed records. I urged them to have their IT or vendor call me and I could give them the IP address over the phone, etc. </p><p>No reply was received.</p><p>Dear Russia, China, and North Korea:</p><p>You do not need to hack our courts. They are leaking like sieves and do not respond when we try to tell them they need to secure the data.</p><p>Yours in total frustration,</p><p>/Dissent</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incident_response</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/WAKETHEFUCKUP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WAKETHEFUCKUP</span></a></p>
Dissent Doe :cupofcoffee:<p>Correcting this because it looks like this doesn't involve any federal court. But there are exposed sensitive records, some of which were ordered sealed. </p><p>NEW: Federal judiciary says it is boosting security after cyberattack; researcher finds new leaks</p><p>More of those frustrating leaks where, despite our best efforts, we have been unable to get the network shares locked down so far, even with the host's assistance.</p><p>This one involves two courts: and yes, we saw some files that were supposed to be sealed or confidential.</p><p><a href="https://databreaches.net/2025/08/10/federal-judiciary-says-it-is-boosting-security-after-cyberattack-researcher-finds-new-leaks/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/08/10/fe</span><span class="invisible">deral-judiciary-says-it-is-boosting-security-after-cyberattack-researcher-finds-new-leaks/</span></a></p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/govsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>govsec</span></a></p>
Ohmbudsman<p>2️⃣ PBS confirms data leak via Discord fan servers<br>🗞️ <a href="https://www.bleepingcomputer.com/news/security/pbs-confirms-data-breach-after-employee-info-leaked-on-discord-servers/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/pbs-confirms-data-breach-after-employee-info-leaked-on-discord-servers/</span></a><br>👥: <span class="h-card" translate="no"><a href="https://mastodon.social/@pbs" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pbs</span></a></span><br><a href="https://mastodon.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://mastodon.social/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DataLeak</span></a> <a href="https://mastodon.social/tags/MediaWatch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MediaWatch</span></a></p>
Dissent Doe :cupofcoffee:<p>Promises, promises. </p><p>Exclusive: Brosix and Chatox promised to keep your chats secured. They didn’t.</p><p>A researcher found a misconfigured backup with -- yes, you guessed it -- everything in plaintext instead of encrypted. </p><p>Some entities that used the service are medical entities that were actually mentioning protected health information or attaching files with <a href="https://infosec.exchange/tags/PHI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHI</span></a> in the chat. </p><p>There were almost 5k Allstate employees using the service and sharing customer <a href="https://infosec.exchange/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PII</span></a> in files. </p><p>And oh yeah, I found one company gossiping about me and plotting against me after I notified them they were leaking tons of <a href="https://infosec.exchange/tags/PHI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHI</span></a>. I've done them a favor by not publishing all their chat logs about me. :) </p><p>There also appeared to be some "dodgy" stuff on the backup, too. </p><p>Read the details about the exposed backup in my post at <a href="https://databreaches.net/2025/08/05/exclusive-brosix-and-chatox-promised-to-keep-your-chats-secured-they-didnt/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/08/05/ex</span><span class="invisible">clusive-brosix-and-chatox-promised-to-keep-your-chats-secured-they-didnt/</span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/chatox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatox</span></a> <a href="https://infosec.exchange/tags/brosix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>brosix</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a></p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>zackwhittaker</span></a></span></p>
Kevin Dominik Korte<p>"Your data is safe in our AI." Unfortunately, that promise doesn't include the website. I guess it was too much to ask for OpenAI to include basic cybersecurity and web design efforts.<br>Hey, you cannot have everything when changing the world.<br><a href="https://fosstodon.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://fosstodon.org/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://fosstodon.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a><br><a href="https://www.techradar.com/ai-platforms-assistants/chatgpt/chatgpt-chats-are-now-appearing-in-google-search-heres-how-to-stop-google-from-spying-on-your-conversations" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">techradar.com/ai-platforms-ass</span><span class="invisible">istants/chatgpt/chatgpt-chats-are-now-appearing-in-google-search-heres-how-to-stop-google-from-spying-on-your-conversations</span></a></p>
Dissent Doe :cupofcoffee:<p>From the "no-need-to-hack-when-it's-leaking-and-leaking-and-leaking" dept:</p><p>Website Planet recently reported on a leak Jeremiah Fowler discovered. But it wasn't the Gladney Adoption Center's first leak. And while Fowler praised the center for their response to his alert, DataBreaches wants to know what the Gladney Adoption Center is going to do to prevent more leaks. They've had 3 in the past few months alone. </p><p><a href="https://databreaches.net/2025/07/17/gladney-adoption-center-had-serious-data-exposures-in-the-past-few-months-what-will-they-do-to-prevent-more/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/07/17/gl</span><span class="invisible">adney-adoption-center-had-serious-data-exposures-in-the-past-few-months-what-will-they-do-to-prevent-more/</span></a></p><p>Great thanks to <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> for his help on this one. </p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/cybersec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersec</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a></p>
Hackread.com<p>🚨 Over 1.1 million sensitive records exposed from a Texas adoption agency, including PII of children, parents, and staff - no password, no encryption.</p><p>Report: <a href="https://hackread.com/massive-data-leak-texas-adoption-agency-million-records/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackread.com/massive-data-leak</span><span class="invisible">-texas-adoption-agency-million-records/</span></a></p><p><a href="https://mstdn.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://mstdn.social/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DataLeak</span></a> <a href="https://mstdn.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://mstdn.social/tags/Breach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Breach</span></a> <a href="https://mstdn.social/tags/Adoption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Adoption</span></a></p>
Dissent Doe :cupofcoffee:<p>In August 2020, <span class="h-card" translate="no"><a href="https://infosec.exchange/@SchizoDuckie" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SchizoDuckie</span></a></span> and I published what was to become the first of a series of articles or posts called "No Need to Hack When It's Leaking."</p><p>In today's installment, I bring you "No Need to Hack When It's Leaking: Brandt Kettwick Defense Edition." It chronicles efforts by <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span>, <span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span>, and I to alert a Minnesota law firm to lock down their exposed files, some of which were quite sensitive.</p><p>Read the post and see how even the state's Bureau of Criminal Apprehension had trouble getting this law firm to respond appropriately. </p><p><a href="https://databreaches.net/2025/07/04/no-need-to-hack-when-its-leaking-brandt-kettwick-defense-edition/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/07/04/no</span><span class="invisible">-need-to-hack-when-its-leaking-brandt-kettwick-defense-edition/</span></a></p><p>Great thanks to the Minnesota Bureau of Criminal Apprehension for their help on this one, and to <span class="h-card" translate="no"><a href="https://infosec.exchange/@TonyYarusso" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>TonyYarusso</span></a></span> and <span class="h-card" translate="no"><a href="https://hachyderm.io/@bkoehn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bkoehn</span></a></span> for their efforts. </p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/misconfiguration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>misconfiguration</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a> <a href="https://infosec.exchange/tags/responsibledisclosure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>responsibledisclosure</span></a> <a href="https://infosec.exchange/tags/securityalert" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>securityalert</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a></p>
Dissent Doe :cupofcoffee:<p>When Cybernews published an article about a 16 billion credentials leak, some of us strongly criticized the article as irresponsible and misleading journalism. Although some people have tried to suggest that the Cybernews article had some value in highlighting infostealers, the article was so riddled with falsehoods and misleading statements that the confusion and misunderstandings it created outweighs any benefit one might try to ascribe to it.</p><p>To his credit, <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> and a colleague have taken the time to analyze the datasets used in Cybernews‘ reporting and to fact-check their reporting with actual data and proof from their own research. </p><p>He has now written up their findings, in which they identified no less than five significant false claims by Cybernews. You can read his report here:</p><p><a href="https://jltee.substack.com/p/fact-checking-claims-by-cybernews" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jltee.substack.com/p/fact-chec</span><span class="invisible">king-claims-by-cybernews</span></a></p><p><a href="https://infosec.exchange/tags/journalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalism</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/infostealers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infostealers</span></a></p>
Dissent Doe :cupofcoffee:<p>With great thanks to <span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span> and <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> and others who assisted or tried to, including Rogers ISP and law enforcement in Canada, we can finally say:</p><p>Bolton Walk-In Clinic patient data leak locked down! </p><p>Read about this very frustrating effort to get exposed patient data locked down:</p><p><a href="https://databreaches.net/2025/06/30/bolton-walk-in-clinic-patient-data-leak-locked-down-finally/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/30/bo</span><span class="invisible">lton-walk-in-clinic-patient-data-leak-locked-down-finally/</span></a></p><p><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/PHIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHIPA</span></a> <a href="https://infosec.exchange/tags/HIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPA</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a></p>
Dissent Doe :cupofcoffee:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> For the life of me, I cannot understand why this got kicked over to the anti-rackets branch, but thank you for what you managed to accomplish. </p><p>I will post an update to this leak on my blog sometime this week, but in the interim:</p><p>Any patients of the Bolton Walk-In Clinic should consider filing a complaint with the provincial Privacy Commission and requesting an investigation into the clinic's failure to comply with medical privacy laws such as PHIPA. IMO, the IPC should also be asked to require the clinic to notify every patient whose unencrypted information was exposed. </p><p>Additional details about earlier efforts by <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> and I to get this leak secured can be found in my post at <a href="https://databreaches.net/2024/12/03/bolton-walk-in-clinic-in-ontario-lock-down-your-backup-already/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/12/03/bo</span><span class="invisible">lton-walk-in-clinic-in-ontario-lock-down-your-backup-already/</span></a></p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/PHIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHIPA</span></a> <a href="https://infosec.exchange/tags/Ontario" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ontario</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a></p>
Dissent Doe :cupofcoffee:<p>A state forensics lab was leaking its files. Getting it locked down involved a number of people, notably <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> and <span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span> , although yours truly was also involved, as were others: </p><p><a href="https://databreaches.net/2025/06/22/a-state-forensics-lab-was-leaking-its-files-getting-it-locked-down-involved-a-number-of-people/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/22/a-</span><span class="invisible">state-forensics-lab-was-leaking-its-files-getting-it-locked-down-involved-a-number-of-people/</span></a></p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/responsibledisclosure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>responsibledisclosure</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/govsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>govsec</span></a> </p><p>Related:<br><a href="https://jltee.substack.com/p/forensic-lab-with-links-to-montana-doj-leaks-phone-extracts" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jltee.substack.com/p/forensic-</span><span class="invisible">lab-with-links-to-montana-doj-leaks-phone-extracts</span></a></p><p><a href="https://blog.literarily-starved.com/2025/06/postmortem-assumed-doj-montana-leak-of-phone-dumps/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.literarily-starved.com/20</span><span class="invisible">25/06/postmortem-assumed-doj-montana-leak-of-phone-dumps/</span></a></p>
JayeLTee<p>US Forensic Lab was leaking phone data extracts for multiple cases, including ongoing ones.</p><p>Likely the most sensitive data I've found exposed to date, with links to the DOJ in Montana.</p><p>Thanks again to <span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span> and <span class="h-card" translate="no"><a href="https://infosec.exchange/@PogoWasRight" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>PogoWasRight</span></a></span> for helping get the message to the people responsible for this one.</p><p><a href="https://jltee.substack.com/p/forensic-lab-with-links-to-montana-doj-leaks-phone-extracts" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jltee.substack.com/p/forensic-</span><span class="invisible">lab-with-links-to-montana-doj-leaks-phone-extracts</span></a></p><p><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/unitedstates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unitedstates</span></a> <a href="https://infosec.exchange/tags/usa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usa</span></a> <a href="https://infosec.exchange/tags/us" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>us</span></a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>leak</span></a> <a href="https://infosec.exchange/tags/evidence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>evidence</span></a> <a href="https://infosec.exchange/tags/phone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>phone</span></a> <a href="https://infosec.exchange/tags/forensics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>forensics</span></a> <a href="https://infosec.exchange/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>data</span></a></p>
Dissent Doe :cupofcoffee:<p>As much as I generally detest claims that something should be a wake-up call, <span class="h-card" translate="no"><a href="https://infosec.exchange/@lawrenceabrams" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lawrenceabrams</span></a></span> response to <span class="h-card" translate="no"><a href="https://infosec.exchange/@cybernews" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cybernews</span></a></span> "16 billion" story really should be a wake-up call for any news outlets who repeat any claims of discovered leaks or breaches by Cybernews. </p><p>See <a href="https://www.bleepingcomputer.com/news/security/no-the-16-billion-credentials-leak-is-not-a-new-data-breach/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/no-the-16-billion-credentials-leak-is-not-a-new-data-breach/</span></a></p><p>DataBreaches.net will no longer link to Cybernews unless there is some reliable source that confirms that their claims are accurate and that they are not just reporting on leaks that they haven't even seriously tried to get locked down before they report on it. </p><p>Comments:<br><a href="https://databreaches.net/2025/06/20/no-the-16-billion-credentials-leak-is-not-a-new-data-breach-a-wake-up-call-about-fake-news/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/20/no</span><span class="invisible">-the-16-billion-credentials-leak-is-not-a-new-data-breach-a-wake-up-call-about-fake-news/</span></a></p><p><a href="https://infosec.exchange/tags/journalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalism</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/infostealers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infostealers</span></a> <a href="https://infosec.exchange/tags/passwords" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>passwords</span></a> <a href="https://infosec.exchange/tags/hype" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hype</span></a> <a href="https://infosec.exchange/tags/clickbait" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clickbait</span></a> <a href="https://infosec.exchange/tags/ethics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ethics</span></a></p><p><span class="h-card" translate="no"><a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GossiTheDog</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@dangoodin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dangoodin</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.green/@gcluley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gcluley</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@brianhonan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>brianhonan</span></a></span></p>
Petra van Cronenburg<p>"Cybercriminals now have unprecedented access to personal credentials and could exploit them for account takeovers, identity theft, and targeted phishing attacks. This is fresh, weaponizable intelligence at scale,” researchers said.</p><p><a href="https://cybernews.com/security/billions-credentials-exposed-infostealers-data-leak/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cybernews.com/security/billion</span><span class="invisible">s-credentials-exposed-infostealers-data-leak/</span></a></p><p><a href="https://mastodon.online/tags/cyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cyberSecurity</span></a> <a href="https://mastodon.online/tags/passwords" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>passwords</span></a> <a href="https://mastodon.online/tags/dataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataLeak</span></a> <a href="https://mastodon.online/tags/cyberCrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cyberCrime</span></a></p>
Datenpunks Bremen<p><a href="https://norden.social/tags/itsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>itsecurity</span></a> <a href="https://norden.social/tags/datenschutz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datenschutz</span></a> <a href="https://norden.social/tags/passwort" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>passwort</span></a> <a href="https://norden.social/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://norden.social/tags/datenleck" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datenleck</span></a><br><a href="https://www.forbes.com/sites/daveywinder/2025/06/19/16-billion-apple-facebook-google-passwords-leaked---change-yours-now/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">forbes.com/sites/daveywinder/2</span><span class="invisible">025/06/19/16-billion-apple-facebook-google-passwords-leaked---change-yours-now/</span></a></p>
Cybernews<p>The unconfirmed dataset, allegedly from T-Mobile, includes device IDs and phone numbers.</p><p><a href="https://infosec.exchange/tags/TMobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TMobile</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/hack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hack</span></a> </p><p><a href="https://cnews.link/t-mobile-data-leak-millions-exposed-2/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cnews.link/t-mobile-data-leak-</span><span class="invisible">millions-exposed-2/</span></a></p>
Cybernews<p>▪Cybernews research▪ Adult dating app has leaked over four million private records.</p><p><a href="https://infosec.exchange/tags/app" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>app</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://infosec.exchange/tags/dataprivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataprivacy</span></a> </p><p><a href="https://cnews.link/headero-data-leak-gps-chat-exposed-3/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cnews.link/headero-data-leak-g</span><span class="invisible">ps-chat-exposed-3/</span></a></p>
Bill<p>Four billion Chinese records leaked due to a poorly configured database. And the contents lead to more questions than answers.</p><p><a href="https://cybernews.com/security/chinese-data-leak-billiones-records-exposed/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cybernews.com/security/chinese</span><span class="invisible">-data-leak-billiones-records-exposed/</span></a></p><p><a href="https://infosec.exchange/tags/china" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>china</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a></p>
Hackread.com<p>🚨 Popular Chrome extensions found leaking user data via unencrypted connections. Millions affected, only one fix so far.</p><p>🔗 <a href="https://hackread.com/popular-chrome-extensions-data-leak-unencrypted-connection/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackread.com/popular-chrome-ex</span><span class="invisible">tensions-data-leak-unencrypted-connection/</span></a></p><p><a href="https://mstdn.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://mstdn.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://mstdn.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> <a href="https://mstdn.social/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a> <a href="https://mstdn.social/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DataLeak</span></a></p>