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 https://infosec.exchange/@JayeLTee/114057470165488882 and his substack at https://jltee.substack.com/p/new-zealand-companys-impossible-to-hack-security

My report/commentary is at :

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

@zackwhittaker @SchizoDuckie

#incident_response #disclosure #notification #dataleak

JayeLTee (@[email protected])

🇳🇿 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

Infosec Exchange