DataBreaches.Net

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

Should we send in CSI to figure out the source of a data dump?

Posted on June 20, 2012 by Dissent

Here’s a great example of the perils in trying to report on hacks or breaches disclosed on Twitter or Pastebin.

A hacker who self-identified as Reckz0r initially claimed to have hacked Visa and MasterCard and to have dumped 50GB worth of data (without credit card numbers).

I had my doubts, and wasn’t surprised to read later that Visa had cast doubt on the claims, noting that they do not collect or store some of the data types the hacker had disclosed. A reporter also reported that the data might be old data, as one of the individuals whose data were dumped said that he hadn’t lived at that address in over seven years. MasterCard would also eventually deny the claim.

Ultimately, the hacker retracted his claim and said that he had obtained the data from 79 banks, but not from Visa and MasterCard directly.

Even then, the controversy continued, as it would still be newsworthy if 79 banks were just hacked over the last three months. But another individual tweeted that what Reckz0r dumped was spoils from others’ hacks.

So what’s the real news story here? I have no idea. But this is a useful example of why I sometimes don’t rush to post a breach on this blog until I see confirmation or additional information to support it.

Category: Breach IncidentsCommentaries and AnalysesFinancial SectorHack

Post navigation

← LinkedIn sued over inadequate security
UK: Data breach exposed as council launches new policy →

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

  • Episource notifying 5.4 million patients of cyberattack in January
  • Investigation of 2024 Helsinki data breach – Report
  • Major trial underway for data leak that left 72,000 victims in France
  • Anubis: A Closer Look at an Emerging Ransomware with Built-in Wiper
  • HealthEC Agrees to $5.48 Million Settlement to End Data Breach Lawsuit
  • US offering $10 million for info on Iranian hackers behind IOControl malware
  • Sompo Japan Insurance submits improvement plan after info leakage
  • Moreno Valley, Calif., Schools Report Data Breach
  • The Growing Cyber Risks from AI — and How Organizations Can Fight Back
  • UPDATING: Credit Control Corporation denies any current breach

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

  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data
  • DOJ Seeks More Time on Tower Dumps
  • Your household smart products must respect your privacy – including your air fryer
  • 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?

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.