RE: https://infosec.exchange/@nono2357/116058508249121772
If you cannot read French, Google Translate gives a correct version.
- 8 Followers
- 65 Following
- 33 Posts
Vengeur MasquéOpenAI
Thwaites Glacier
USA federation
Poll ended at .
🐦🔥nemo™🐦⬛ 🇺🇦🍉A high-severity Firefox WebAssembly bug (CVE-2025-13016) silently exposed over 180M users to potential code execution for 6 months, now patched in Firefox 145/ESR 140.5. 🔐 Users are urged to update ASAP. 🔄✨ Details: https://cyberinsider.com/dangerous-firefox-webassembly-bug-went-undetected-for-6-months/ #Firefox #CyberSecurity #InfoSec #Newz
#Tor & #Mullvad are immune to this, given the security slider has been moved to "Safer" 💡. with Librewolf idk 🤷
#MS #Linkedin underhandedly feeds its #IA with your #data and refers to a fallacious argument to circumvent #GDPR
You can check and disable that sneaky option here:
https://www.linkedin.com/mypreferences/d/settings/data-for-ai-improvement
See also https://www.dutchnews.nl/2025/09/dutch-privacy-watchdog-urges-linkedin-users-to-block-ai-data-use/
Brian Greenberg 
Big publicly traded companies are hedging their public AI enthusiasm by quietly disclosing it as a material risk in financial filings. They warn investors that return on AI investment may never come, or that regulatory and competitive pressures could undercut progress. It is smart self‑defense, but also shows a gap between marketing and sober risk assessment.
TL;DR
⚠️ Many S&P 500 firms list AI as a risk in SEC filings
🧠 Some warn AI ROI may never materialise
🔐 Regulatory oversight and “AI washing” enforcement increasing
📉 Disclosures reflect cautious tone beneath bullish public messaging
https://www.theregister.com/2025/07/15/sec_risk_factors_ai/
#AI #SEC #RiskFactors #CorporateGovernance #security #privacy #cloud #infosec #cybersecurity #risk #finance
@jbz
Paying ransom should be strictly forbidden in all countries.
Paying ransom should be strictly forbidden in all countries.
@nono2357 If I understood correctly, the problem is not the dataleak per se. It is actually good news that the bad guys forgot to put a password on their ElasticSearch, bo?
The issue is the infostealer(s) that fed this ES database.
The issue is the infostealer(s) that fed this ES database.
#dataleak #infosec #GDPR
Some figures about the "recent" #twitter #dataleak
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.
#dataleak #infosec #CNIL #RGPD
Quelques chiffres sur la fuite de données #twitter 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êt
288 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
Do you know the difference between #Microsoft #Azure #API #documentation and the #Necronomicon?
None. Nobody could read them and keep their sanity.