Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operational Security //

Data Leakage

1/17/2019
03:26 PM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

'Collection #1' Repository Totals 87GB of Stolen Email Addresses & Passwords

With the discovery of 'Collection #1,' security researcher Troy Hunt appears to have found the largest repository of stolen email addresses and passwords ever, totaling more than 87GB and 12,000 separate files.

There are massive data breaches and then there is "Collection #1."

On January 17, security researcher Troy Hunt, who runs the popular Have I Been Pwned website, detailed the discovery of 12,000 separate files that held more than 87GB of stolen personal data, which he dubbed Collection #1. The name comes from a root folder where the data had been stored.

These thousands of files, which were found on the New Zealand-based MEGA cloud hosting service, contained 772,904,991 unique email addresses, along with 21,222,975 passwords. If all the numbers pan out -- there are 1,160,253,228 unique combinations all together -- this is the largest collection of stolen personal data ever found.

"What I can say is that my own personal data is in there and it's accurate; right email address and a password I used many years ago," Hunt wrote in Thursday's blog post. "Like many of you reading this, I've been in multiple data breaches before which have resulted in my email addresses and yes, my passwords, circulating in public."

Hunt noted much of the data was found on a hacking forum, where it was being socialized. Many of the passwords had been de-encrypted and converted to plain text.

It appears all this data was being used, or could be used, for credential stuffing attacks, a brute-force method used to guess passwords and further hijack other accounts using this personal information.

The discovery of this repository of stolen data is likely to respark debates about how passwords are used, how often users should change them and if there's any point anymore in using passwords to keep data secure. (See Microsoft Looks to End the Era of Security Passwords.)

Terence Jackson, CISO of Thycotic, a security vendor that provides privileged access management (PAM) tools, noted in an email that both individual consumers, as well as enterprises, should take notice of Collection #1 since so many people repeatedly re-use passwords.

"This highlights the importance of password management and consumer education in that regard," Jackson told Security Now. He added:

Many people still use the same passwords across sites for personal and business purposes because it's convenient until something like this happens and it's back in the headlines. Using unique passwords on each site isn't a magic bullet, but the goal here is to limit the damage that could be done in a credential stuffing or brute force type attack. As a CISO, this type of attack would concern me because employees often use their corporate emails to sign up for services and often use the same passwords.

Although the data has been removed from MEGA, combinations of passwords and email addresses can still be in someone else's hands. Hunt's site offers services where users can check to see if their passwords have been exposed.

In an email, Raj Samani, chief scientist at McAfee, urged anyone who thinks their email address or password may have been compromised to reset passwords and to look into using a password manager.

"People need to act fast and defend themselves," Samani wrote. "With such a high volume of personal data being discovered, nobody can assume they haven’t been caught up in this. Passwords need to be changed immediately. If you have the same password across any account, device or app you need to make every single one unique, strong and never re-use it again. A password manager is a great option if you want to do this quickly."

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.