Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
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.

Administered by:

Server stats:

508
active users

101010.pl: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.5

#dataleak

5 posts4 participants0 posts today
*
Dendrobatus Azureus

This is something you need to read in order to believe

subject: VoLTE
provider O2 UK
nightmare: infosec

Enormous. 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 practices

Excerpt

>>

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=26371

Synthesised 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

#O2 #UK #TeleCom #InfoSec #DataLeak #WTF

mastdatabase.co.uk/blog/2025/0

*
JayeLTee

A 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 @PogoWasRight 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: jltee.substack.com/p/us-childc

The Hub of Stupi.. *misconfigs · U.S. Childcare Center Leaks Thousands of Children's Private DataBy JayeLTee
#cybersecurity#infosec#education
Brian Greenberg :verified:

😳 😱 ⚠️ Massive privacy breach: 21M employee screenshots leaked from WorkComposer 📸🔓

Researchers discovered a misconfigured S3 bucket that exposed:
💬 Emails, internal messages, and screenshots
🔑 Passwords, API keys, and sensitive login details
📄 Confidential internal documents

🛡️ Fallout risks include:
• GDPR and CCPA violations
• Business data compromise
• Employee trust erosion

Employee monitoring tools must protect, not expose.
Security hygiene isn’t optional — it’s the foundation.

#CyberSecurity #DataLeak #PrivacyBreach #WorkComposer #Compliance
cybernews.com/security/employe

*
Dissent Doe :cupofcoffee:

Correcting one of my posts: It was not Atrium Health that owned the data Jeremiah Fowler reported on to Website Planet. I heard from Atrium Health today and it was Carolina Anesthesiology, P.A., who owned the data that were exposed.

My corrected post is at:
databreaches.net/2025/04/24/no

#healthsec #dataleak

(I can't believe it but I just had to correct my correction on the name of the actual owners. Please make this week be over.)

JayeLTee

Database for an internal chat with millions of chat messages and over 130,000 files with PII and PHI from the United States exposed publicly for over a month.

Contacted the company responsible for setting up the chat and one of their clients, a Mental Health Clinic, but no one replied back to me and just silently fixed the issue.

jltee.substack.com/p/internal-

The Hub of Stupi.. *misconfigs · Internal chat database for multiple US companies exposed publiclyBy JayeLTee
#cybersecurity#infosec#database
*
Vengeur Masqué

#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

JayeLTee

All-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: jltee.substack.com/p/all-in-on

The Hub of Stupi.. *misconfigs · All-in-One Platform GoHighLevel Exposed Attachments From Their Clients PubliclyBy JayeLTee
#cybersecurity#infosec#data
Dissent Doe :cupofcoffee:

Another day, another leak, another inaccurate claim by an entity, and another inappropriate attack on a researcher. Buckle up.

@JayeLTee had alerted me to his nasty encounter with TeammateApp's CEO. See his post infosec.exchange/@JayeLTee/114 and his substack at jltee.substack.com/p/new-zeala

My report/commentary is at :

No need to hack when it’s leaking, Monday edition: TeammateApp:
databreaches.net/2025/02/24/no

@zackwhittaker @SchizoDuckie

Infosec ExchangeJayeLTee (@JayeLTee@infosec.exchange)🇳🇿 I've had quite a few outrageous responses to my alerts, this is another one of those, sent by teammateapp.com CEO. After my initial alert and follow up email, I get a reply lying about the severity of the exposure and telling me to stop harassing the company. This CEO also didn't know what Proton is and thought I work for them and threatened to report me to them in case I didn't stop. :blobshrug: Read about it here: https://jltee.substack.com/p/new-zealand-companys-impossible-to-hack-security #cybersecurity #infosec #privacy #database #databreach #leak #newzealand #nz #teammateapp #ceo #incidentresponse
#incident_response#disclosure#notification
ExploreLive feeds
About