Lingolol

Cybernews▪️Cybernews research▪️TalentHook, a cloud-based applicant tracking system, left a misconfigured instance open. It spilled tens of millions of job seekers' CVs, full of personal details ranging from full names to home addresses.<a href="https://infosec.exchange/tags/CV" class="mention hashtag" rel="nofollow noopener" target="_blank">#CV</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> Read more: <a href="https://cnews.link/talenthook-data-leak-exposes-millions-6/" rel="nofollow noopener" translate="no" target="_blank">https://cnews.link/talenthook-data-leak-exposes-millions-6/</a>

Dissent Doe :cupofcoffee: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.To his credit, <a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@JayeLTee</a> 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. 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:<a href="https://jltee.substack.com/p/fact-checking-claims-by-cybernews" rel="nofollow noopener" translate="no" target="_blank">https://jltee.substack.com/p/fact-checking-claims-by-cybernews</a><a href="https://infosec.exchange/tags/journalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#journalism</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/infostealers" class="mention hashtag" rel="nofollow noopener" target="_blank">#infostealers</a>

Dissent Doe :cupofcoffee:With great thanks to <a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@masek</a> and <a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@JayeLTee</a> and others who assisted or tried to, including Rogers ISP and law enforcement in Canada, we can finally say:Bolton Walk-In Clinic patient data leak locked down! Read about this very frustrating effort to get exposed patient data locked down:<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">https://databreaches.net/2025/06/30/bolton-walk-in-clinic-patient-data-leak-locked-down-finally/</a><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/PHIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHIPA</a> <a href="https://infosec.exchange/tags/HIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#HIPA</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#incidentresponse</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a>

Dissent Doe :cupofcoffee:As much as I generally detest claims that something should be a wake-up call, <a href="https://infosec.exchange/@lawrenceabrams" class="u-url mention" rel="nofollow noopener" target="_blank">@lawrenceabrams</a> response to <a href="https://infosec.exchange/@cybernews" class="u-url mention" rel="nofollow noopener" target="_blank">@cybernews</a> "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. 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">https://www.bleepingcomputer.com/news/security/no-the-16-billion-credentials-leak-is-not-a-new-data-breach/</a>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. Comments: <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">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/</a><a href="https://infosec.exchange/tags/journalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#journalism</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/infostealers" class="mention hashtag" rel="nofollow noopener" target="_blank">#infostealers</a> <a href="https://infosec.exchange/tags/passwords" class="mention hashtag" rel="nofollow noopener" target="_blank">#passwords</a> <a href="https://infosec.exchange/tags/hype" class="mention hashtag" rel="nofollow noopener" target="_blank">#hype</a> <a href="https://infosec.exchange/tags/clickbait" class="mention hashtag" rel="nofollow noopener" target="_blank">#clickbait</a> <a href="https://infosec.exchange/tags/ethics" class="mention hashtag" rel="nofollow noopener" target="_blank">#ethics</a><a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@GossiTheDog</a> <a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@JayeLTee</a> <a href="https://infosec.exchange/@dangoodin" class="u-url mention" rel="nofollow noopener" target="_blank">@dangoodin</a> <a href="https://mastodon.green/@gcluley" class="u-url mention" rel="nofollow noopener" target="_blank">@gcluley</a> <a href="https://mastodon.social/@brianhonan" class="u-url mention" rel="nofollow noopener" target="_blank">@brianhonan</a>

Marcel WaldvogelAgentic AI as the enemy's agent.It is a bad idea to allow an LLM access to internal data and external communication (web pages, APIs, email, …) at the same time. <a href="https://waldvogel.family/tags/AgenticAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AgenticAI</a> <a href="https://waldvogel.family/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataLeak</a> <a href="https://waldvogel.family/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLM</a> <a href="https://fortune.com/2025/06/11/microsoft-copilot-vulnerability-ai-agents-echoleak-hacking/" rel="nofollow noopener" translate="no" target="_blank">https://fortune.com/2025/06/11/microsoft-copilot-vulnerability-ai-agents-echoleak-hacking/</a>

Cybernews▪Cybernews research▪ Adult dating app has leaked over four million private records.<a href="https://infosec.exchange/tags/app" class="mention hashtag" rel="nofollow noopener" target="_blank">#app</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://infosec.exchange/tags/dataprivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataprivacy</a> <a href="https://cnews.link/headero-data-leak-gps-chat-exposed-3/" rel="nofollow noopener" translate="no" target="_blank">https://cnews.link/headero-data-leak-gps-chat-exposed-3/</a>

BillFour billion Chinese records leaked due to a poorly configured database. And the contents lead to more questions than answers.<a href="https://cybernews.com/security/chinese-data-leak-billiones-records-exposed/" rel="nofollow noopener" translate="no" target="_blank">https://cybernews.com/security/chinese-data-leak-billiones-records-exposed/</a><a href="https://infosec.exchange/tags/china" class="mention hashtag" rel="nofollow noopener" target="_blank">#china</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a>

nemo™ 🇺🇦🚨 Over 90 Chrome extensions—including big names like Avast, Trust Wallet & Browsec VPN—were found leaking sensitive data & credentials! 🕵️‍♂️🔑 Millions at risk from hardcoded secrets & unencrypted traffic. Stay safe & review your extensions! Read more 👉 <a href="https://cyberinsider.com/over-90-chrome-extensions-found-exposing-sensitive-data-and-credentials/" rel="nofollow noopener" translate="no" target="_blank">https://cyberinsider.com/over-90-chrome-extensions-found-exposing-sensitive-data-and-credentials/</a> <a href="https://mas.to/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cybersecurity</a> <a href="https://mas.to/tags/ChromeExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeExtensions</a> <a href="https://mas.to/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataLeak</a> <a href="https://mas.to/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://mas.to/tags/Infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#Infosec</a> <a href="https://mas.to/tags/newz" class="mention hashtag" rel="nofollow noopener" target="_blank">#newz</a>

CybernewsMajor data leak exposed 184M Facebook, Snapchat, Roblox logins and passwords <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://infosec.exchange/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://infosec.exchange/tags/Roblox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Roblox</a> <a href="https://infosec.exchange/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> Learn more: <a href="https://cnews.link/data-leak-facebook-roblox-instagram-passwords-2/" rel="nofollow noopener" translate="no" target="_blank">https://cnews.link/data-leak-facebook-roblox-instagram-passwords-2/</a>

Dendrobatus AzureusThis is something you need to read in order to believesubject: VoLTE provider O2 UK nightmare: infosecEnormous. Outragerous are some of the words I would use. Take you time to read and learn because they are not the only culprits on the planet with such bad data protection practicesExcerpt>>Quite quickly I realised something was wrong. The responses I got from the network were extremely detailed and long, and were unlike anything I had seen before on other networks. The messages contained information such as the IMS/SIP server used by O2 (Mavenir UAG) along with version numbers, occasional error messages raised by the C++ services processing the call information when something went wrong, and other debugging information. However, most notable were a set of five headers near the bottom of the message:SIP Msg ... P-Mav-Extension-IMSI: 23410123456789 P-Mav-Extension-IMSI: 23410987654321 P-Mav-Extension-IMEI: 350266809828927 P-Mav-Extension-IMEI: 350266806365261 ... Cellular-Network-Info: 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=2341010037A60773;cell-info-age=26371Synthesised excerpt of IMS signalling message for demonstration; not a genuine IMEI/IMSI/cell ID.Two sets of IMSIs, two sets of IMEIs, and a Cell ID header. How curious…Sure enough, when comparing both the IMSIs and IMEIs in the message to those of my own devices, I had been given both the IMSI and IMEI of my phone which initiated the call, but also the call recipient's.<< ^Z<a href="https://mastodon.bsd.cafe/tags/O2" class="mention hashtag" rel="nofollow noopener" target="_blank">#O2</a> <a href="https://mastodon.bsd.cafe/tags/UK" class="mention hashtag" rel="nofollow noopener" target="_blank">#UK</a> <a href="https://mastodon.bsd.cafe/tags/TeleCom" class="mention hashtag" rel="nofollow noopener" target="_blank">#TeleCom</a> <a href="https://mastodon.bsd.cafe/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://mastodon.bsd.cafe/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataLeak</a> <a href="https://mastodon.bsd.cafe/tags/WTF" class="mention hashtag" rel="nofollow noopener" target="_blank">#WTF</a> <a href="https://mastdatabase.co.uk/blog/2025/05/o2-expose-customer-location-call-4g/" rel="nofollow noopener" translate="no" target="_blank">https://mastdatabase.co.uk/blog/2025/05/o2-expose-customer-location-call-4g/</a>

JayeLTeeA Childcare Center in the United States had a server exposing children's documents publicly for years.I wasn't the first to alert them about this either. I mentioned this to <a href="https://infosec.exchange/@PogoWasRight" class="u-url mention" rel="nofollow noopener" target="_blank">@PogoWasRight</a> and she told me she notified them about the issue on a call in 2022. The call wasn't properly followed up by the company and the data ended up being exposed for almost another 3 years.You can read more about it here: <a href="https://jltee.substack.com/p/us-childcare-center-leaks-thousands-of-childrens-private-data" rel="nofollow noopener" translate="no" target="_blank">https://jltee.substack.com/p/us-childcare-center-leaks-thousands-of-childrens-private-data</a><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/education" class="mention hashtag" rel="nofollow noopener" target="_blank">#education</a> <a href="https://infosec.exchange/tags/usa" class="mention hashtag" rel="nofollow noopener" target="_blank">#usa</a> <a href="https://infosec.exchange/tags/us" class="mention hashtag" rel="nofollow noopener" target="_blank">#us</a> <a href="https://infosec.exchange/tags/unitedstates" class="mention hashtag" rel="nofollow noopener" target="_blank">#unitedstates</a> <a href="https://infosec.exchange/tags/children" class="mention hashtag" rel="nofollow noopener" target="_blank">#children</a> <a href="https://infosec.exchange/tags/childcare" class="mention hashtag" rel="nofollow noopener" target="_blank">#childcare</a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener" target="_blank">#leak</a> <a href="https://infosec.exchange/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#data</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a>

Da lazy beardudeAll things (even people) need to be touched at some point cos things break when they're left unmaintained and lonely out there.I haven't been touched in 5+ years, but I maintain myself every few days lolAlso fuck you Oracle.<a href="https://odysee.com/@AlphaNerd:8/oracle-tried-to-coverup-this-data-breach:8" rel="nofollow noopener" translate="no" target="_blank">https://odysee.com/@AlphaNerd:8/oracle-tried-to-coverup-this-data-breach:8</a><a href="https://mastodon.social/tags/oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#oracle</a> <a href="https://mastodon.social/tags/sql" class="mention hashtag" rel="nofollow noopener" target="_blank">#sql</a> <a href="https://mastodon.social/tags/mentaloutlaw" class="mention hashtag" rel="nofollow noopener" target="_blank">#mentaloutlaw</a> <a href="https://mastodon.social/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a> <a href="https://mastodon.social/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://mastodon.social/tags/oraclecloudservice" class="mention hashtag" rel="nofollow noopener" target="_blank">#oraclecloudservice</a> <a href="https://mastodon.social/tags/oraclebreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#oraclebreach</a>

VM<a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a> Some figures about the "recent" <a href="https://infosec.exchange/tags/twitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#twitter</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> 382 CSV files, 438 GB uncompressed.94 twitter_users_extra_ZZZ.csv files which contain few things. 835 M lines.288 twitter_users_NNN.csv files, 1.7 billions of lines. Few really personal data, only 9 millions lines with an e-mail address (valid or not).Some rare lines also include a description or an URL.EDIT: sick CSV broke my first parser.

Vengeur Masqué<a href="https://mastodon.hofud.com/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://mastodon.hofud.com/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://mastodon.hofud.com/tags/CNIL" class="mention hashtag" rel="nofollow noopener" target="_blank">#CNIL</a> <a href="https://mastodon.hofud.com/tags/RGPD" class="mention hashtag" rel="nofollow noopener" target="_blank">#RGPD</a> Quelques chiffres sur la fuite de données <a href="https://mastodon.hofud.com/tags/twitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#twitter</a> dont on a parlé récemment.382 fichiers CSV, 438 GB décompressés. 94 twitter_users_extra_ZZZ.csv = 935 millions de lignes sans grand intérêt288 fichiers twitter_users_NNN.csv, = 1.7 G lignes. Peu de données réellement personnelles, seulement 9 millions de lignes avec une adresse e-mail, valide ou pas.Certaines rares lignes comportent aussi une description et/ou une URL.EDIT: CSV bizarres mal parsés

JayeLTeeAll-in-One platform leaks millions of attachments from their clients. This server contained a bit of everything, from sensitive piercing selfies next to identity docs, to passports, cvs, insurance docs and more.Read about it here: <a href="https://jltee.substack.com/p/all-in-one-platform-gohighlevel-exposed-attachments-from-clients" rel="nofollow noopener" translate="no" target="_blank">https://jltee.substack.com/p/all-in-one-platform-gohighlevel-exposed-attachments-from-clients</a><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#data</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener" target="_blank">#leak</a> <a href="https://infosec.exchange/tags/gohighlevel" class="mention hashtag" rel="nofollow noopener" target="_blank">#gohighlevel</a> <a href="https://infosec.exchange/tags/highlevel" class="mention hashtag" rel="nofollow noopener" target="_blank">#highlevel</a>

Marcel SIneM(S)USSicherheitsexperten enthüllen triviale Datenlecks bei Legaltechs | Security <a href="https://www.heise.de/news/Sicherheitsexperten-enthuellen-triviale-Datenlecks-bei-Legaltechs-10272273.html" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/Sicherheitsexperten-enthuellen-triviale-Datenlecks-bei-Legaltechs-10272273.html</a> <a href="https://social.tchncs.de/tags/DataLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataLeak</a> <a href="https://social.tchncs.de/tags/Datenleck" class="mention hashtag" rel="nofollow noopener" target="_blank">#Datenleck</a> <a href="https://social.tchncs.de/tags/Datenschutz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Datenschutz</a> <a href="https://social.tchncs.de/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://social.tchncs.de/tags/DSGVO" class="mention hashtag" rel="nofollow noopener" target="_blank">#DSGVO</a> <a href="https://social.tchncs.de/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a>

Erik JonkerThis is funny, "only read access" makes this in any country or legal system still a databreach/leak of gigantic proportions. <a href="https://www.cbsnews.com/news/treasury-says-elon-musk-doge-has-read-only-access-to-payment-systems/" rel="nofollow noopener" translate="no" target="_blank">https://www.cbsnews.com/news/treasury-says-elon-musk-doge-has-read-only-access-to-payment-systems/</a> <a href="https://mastodon.social/tags/Musk" class="mention hashtag" rel="nofollow noopener" target="_blank">#Musk</a> <a href="https://mastodon.social/tags/DOGE" class="mention hashtag" rel="nofollow noopener" target="_blank">#DOGE</a> <a href="https://mastodon.social/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a> <a href="https://mastodon.social/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a>

Dimitri BouniolFYI, Crunchyroll got hacked and all credentials were leaked — now's a great time to change your password (apparently you need to reset it):<a href="https://mastodon.social/tags/Crunchyroll" class="mention hashtag" rel="nofollow noopener" target="_blank">#Crunchyroll</a> <a href="https://mastodon.social/tags/Dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dataleak</a> <a href="https://mastodon.social/tags/Anime" class="mention hashtag" rel="nofollow noopener" target="_blank">#Anime</a><a href="https://www.reddit.com/r/animenews/comments/1i8edhb/crunchyroll_premium_login_details_leaked_users_at/" rel="nofollow noopener" translate="no" target="_blank">https://www.reddit.com/r/animenews/comments/1i8edhb/crunchyroll_premium_login_details_leaked_users_at/</a>

JayeLTee🇬🇧 Security company Assist Security exposed over 100,000 sensitive files publicly.If you're curious what kind of wild excuses I get from companies, this one tried to claim only the file structure was exposed. Apparently I look at filenames and paths and figure what's there from the names only and report this to companies :blobwizard: <a href="https://jltee.substack.com/p/security-company-assist-security-exposed-data" rel="nofollow noopener" translate="no" target="_blank">https://jltee.substack.com/p/security-company-assist-security-exposed-data</a><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener" target="_blank">#leak</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://infosec.exchange/tags/unitedkingdom" class="mention hashtag" rel="nofollow noopener" target="_blank">#unitedkingdom</a> <a href="https://infosec.exchange/tags/uk" class="mention hashtag" rel="nofollow noopener" target="_blank">#uk</a> <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://infosec.exchange/tags/AssistSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssistSecurity</a>

DoerkSurprise: There are companies collecting global geolocation data and selling them. Now hackers claim to have hacked their data and threaten to leak it.I wonder what should worry me more, the fact that there are companies collecting these data or that these companies are getting hacked?However I am afraid that this will have no impact on the public mindset of smartphone usage.<a href="https://mastodon.bsd.cafe/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://mastodon.bsd.cafe/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://mastodon.bsd.cafe/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataleak</a> <a href="https://mastodon.bsd.cafe/tags/breach" class="mention hashtag" rel="nofollow noopener" target="_blank">#breach</a>Article is behind paywall:<a href="https://www.404media.co/hackers-claim-massive-breach-of-location-data-giant-threaten-to-leak-data/" rel="nofollow noopener" translate="no" target="_blank">https://www.404media.co/hackers-claim-massive-breach-of-location-data-giant-threaten-to-leak-data/</a>

Recent searches

Search options

Administered by:

Server stats:

#dataleak