Home Cyber Security News Researchers identify the hacker behind the dump of 773million credentials

Researchers identify the hacker behind the dump of 773million credentials

by Unallocated Author

Researchers identified the hacker behind a dump of 773million credentials after a meticulous investigation. It totalled over 900GB of data consisting of passwords, telephone number and addresses of individuals. This was likely to be from more than one source.

Recorded Future revealed the hacker’s name as “Corpz,” pseudonymised evidently to conceal their identity.

Recorded Futures’ Investigation and Findings

Upon investigating the dump data, Recorded Futures discovered C0rpz first distributed it. It is not however confident in the fact that C0rpz stole the data. The researchers further believed that C0rpz collected the data over three years as opposed to all at once. Its originality is not known but it is assumed the number of sources it was retrieved from was already leaked data. This could potentially render some of the credentials worthless as targeted organisations would have been obligated to notify victims to change or reset their passwords.

The mass data was dumped on hacking forums such as RAID where C0rpz additionally sold a custom-made brute-forcing tools. This was likely for account stuffing attacks.

The hacker divided the 12,000 files separately within a root folder, labelled “Collection#1.” The other folders, later discovered, contained 845 GB  worth of data. The data minimised, by removing duplicates, were released as Collection numbers 2-5. The publication of the data files go as far back as 2017 with the “ANTIPUBLIC #1” file.

The consequence of using sold data

Recorded Future note the data sold for free in a mega cloud service and on torrent trackers. It concluded that big data dumps will continue to happen across the dark web, where it can use it for a range of criminal activities such as identity theft and other fraudulent activities. Further hackings can result from the sold data such as phishing campaigns or use of passwords to gain access to IoT devices.

You may also like

Latest Hacking News

Privacy Preference Center

Necessary

The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]

Advertising

DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.

doubleclick

Analytics

The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid