DataBreaches.Net

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

When you try to confirm or disconfirm a claimed hack, Thursday edition

Posted on October 31, 2013 by Dissent

As regular readers know, I often try to confirm or disconfirm claimed hacks before just repeating what I see or read elsewhere. And I generally use a notification feature to let me know whether my requests have been delivered and/or read.

Here’s an example of why people may be frustrated or just say “screw it” instead of trying to give entities a chance to respond to claims online. From my e-mail today, complete with header and emphasis added by me:

Subject: Not read: Alleged hack of 1.1 million FB accounts
From: “Press (No-Reply)” <[email protected]> Date: Thu, October 31, 2013 19:06
To: “[email protected]” <[email protected]>
Priority: High

Your message

To: Press (No-Reply)
Subject: Alleged hack of 1.1 million FB accounts
Sent: Wednesday, May 08, 2013 1:02:04 PM (UTC-08:00) Pacific Time (US & Canada)

was deleted without being read on Thursday, October 31, 2013 4:06:02 PM (UTC-08:00) Pacific Time (US & Canada).

Yes, I realize I’m not a New York Times reporter or some big gun, but really, Facebook, you should have read and replied to the inquiry.

Category: Commentaries and Analyses

Post navigation

← Commentary: It's time for California and HHS to do a serious smackdown on "jokes" that invade privacy (update 1)
From the ICO today… →

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

  • Rajkot civic body’s GIS website hit by cyber attack, over 400 GB data feared stolen
  • Taiwan’s BitoPro hit by NT$345 million cryptocurrency hack
  • Texas gastroenterology and surgical practice victim of ransomware attack
  • Romanian Citizen Pleads Guilty to ‘Swatting’ Numerous Members of Congress, Churches, and Former U.S. President
  • North Dakota Enacts Financial Data Security and Data Breach Notification Requirements
  • Pro-Ukraine hacker group Black Owl poses ‘major threat’ to Russia, Kaspersky says
  • Vanta bug exposed customers’ data to other customers
  • Lyrix Ransomware Targets Windows Users with Advanced Evasion Techniques
  • Central Maine Healthcare tackles suspected cybersecurity issue; hospitals remain open
  • Cartier Data Breach: Luxury Retailer Warns Customers that Personal Data Was Exposed

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

  • Florida ban on kids using social media likely unconstitutional, judge rules
  • State Data Minimization Laws Spark Compliance Uncertainty
  • Supreme Court Agrees to Clarify Emergency Situations Where Police Don’t Need Warrant
  • Stewart Baker vs. Orin Kerr on “The Digital Fourth Amendment”
  • Fears Grow Over ICE’s Reach Into Schools
  • Resource: HoganLovells Asia-Pacific Data, Privacy and Cybersecurity Guide 2025
  • She Got an Abortion. So A Texas Cop Used 83,000 Cameras to Track Her Down.

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.