DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Months later, KeepNet issues a statement about leak discovered by researcher

Posted on June 10, 2020 by Dissent

Back in March, Security Discovery reported a leak involving KeepNet.  This site had picked up that reporting and linked to it. Shortly thereafter I was contacted by KeepNet. Based on their statement and the fact that Security Discovery revised their own report, this site deleted KeepNet’s name from the reporting and simply linked to Security Discovery’s post.

Some people who had named KeepNet in their reporting and didn’t remove it were apparently threatened with litigation.  Yesterday, Graham Cluley wrote, “After threatening me with legal action, Keepnet Labs finally issues statement over data breach.”

Threatening security researchers or journalists is not a good look, especially for a security firm. If the leak was due to a third-party vendor, why didn’t KeepNet just come out and say that months ago instead of trying to squash all reporting?

It’s 2020. There are tons of leaks and incidents. This would be a great time for all entities to get training on how to deal with researchers and journalists in transparent, constructive ways.

Category: Business SectorExposureNon-U.S.

Post navigation

← Nintendo now says 300,000 accounts breached by hackers
Health and Safety Executive secures court orders preventing IT worker distributing data →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Washington Post investigating cyberattack on journalists, WSJ reports
  • Resource: State Data Breach Notification Laws – June 2025
  • WestJet investigates cyberattack disrupting internal systems
  • Plastic surgeons often store nude photos of patients with their identity information. When would we call that “negligent?”
  • India: Servers of two city hospitals hacked; police register FIR
  • Ph: Coop Hospital confirms probe into reported cyberattack
  • Slapped wrists for Financial Conduct Authority staff who emailed work data home
  • School Districts Unaware BoardDocs Software Published Their Private Files
  • A guilty plea in the PowerSchool case still leaves unanswered questions
  • Brussels Parliament hit by cyber-attack

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation
  • Anne Wojcicki Wins Bidding for 23andMe
  • Would you — or wouldn’t you?
  • New York passes a bill to prevent AI-fueled disasters
  • Synthetic Data and the Illusion of Privacy: Legal Risks of Using De-Identified AI Training Sets
  • States sue to block the sale of genetic data collected by DNA testing company 23andMe

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.