DataBreaches.Net

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

The Twitter hack that wasn’t?

Posted on May 10, 2012 by Dissent

When the news started circulating a few nights ago that Twitter had been hacked and over 55,000 logins had been dumped on the Internet, I looked at the five pastes comprising the data dump. The data didn’t look right to me, and as I told a colleague on DataLossDB, I was going to hold off on adding the incident.

Not surprising to me, Twitter quickly issued a statement and noted that a significant percentage of the logins were duplicates and many of accounts looked like spam accounts that had already been terminated by Twitter. They said they were continuing to investigate. And I continued to hold off on treating this as an incident in the database.

Today Jay Alabaster reports:

None of the recently leaked Twitter logins and passwords came from within the company, according to a message posted on Twitter’s Japanese blog Thursday.

“We have confirmed that no one’s information has been leaked from Twitter,” the blog said, after apologizing to users for their concerns.

[…]

In its Japanese blog posting, Twitter said that account information had likely been leaked from a different site, and it had sent password reset requests to users on the list.

Read more on Computerworld while I congratulate myself on not spending time researching the hack that wasn’t.

Category: Business Sector

Post navigation

← $500,000 bond for stealing trade secrets
Plaxo online address book service warns of security breach →

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

  • B.C. health authority faces class-action lawsuit over 2009 data breach (1)
  • Private Industry Notification: Silent Ransom Group Targeting Law Firms
  • Data Breach Lawsuits Against Chord Specialty Dental Partners Consolidated
  • PA: York County alerts residents of potential data breach
  • FTC Finalizes Order with GoDaddy over Data Security Failures
  • Hacker steals $223 million in Cetus Protocol cryptocurrency heist
  • Operation ENDGAME strikes again: the ransomware kill chain broken at its source
  • Mysterious Database of 184 Million Records Exposes Vast Array of Login Credentials
  • Mysterious hacking group Careto was run by the Spanish government, sources say
  • 16 Defendants Federally Charged in Connection with DanaBot Malware Scheme That Infected Computers Worldwide

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

  • D.C. Federal Court Rules Termination of Democrat PCLOB Members Is Unlawful
  • Meta may continue to train AI with user data, German court says
  • Widow of slain Saudi journalist can’t pursue surveillance claims against Israeli spyware firm
  • Researchers Scrape 2 Billion Discord Messages and Publish Them Online
  • GDPR is cracking: Brussels rewrites its prized privacy law
  • Telegram Gave Authorities Data on More than 20,000 Users
  • Police secretly monitored New Orleans with facial recognition cameras

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.