The Hatman Heist: Massive Enterprise Data Exfiltration
Since around 31 July, a threat actor using the handle TheHatman has been posting large internal employee directories to cybercrime forums, each one advertised as having been downloaded directly from a victim company’s Microsoft Azure or Entra tenant using stolen login credentials. Cybercrime intelligence firm Hudson Rock reviewed samples of the data and published its findings on 16 August, and coverage has since spread across the security press.
Nine organisations are named across the listings, with a combined total the seller puts at roughly 3.6 million records. The scale of each individual dataset varies widely, from McDonald’s at the top down to a few thousand records for the smallest listed company.
Who’s named, and how many records
| McDonald’s Corporation | ≈ 1,700,000 records |
| Tata Consultancy Services (TCS) | ≈ 800,000 records |
| Vodafone | ≈ 425,000 records |
| HCL Technologies | ≈ 250,000 records |
| InterContinental Hotels Group (IHG) | ≈ 185,000 records |
| Kyndryl | ≈ 170,000 records |
| Gap Inc. | ≈ 80,000 records |
| Hexaware Technologies | ≈ 20,000 records |
| Wyndham Hotels & Resorts | ≈ 9,000 records |
The fields reportedly included in the dumps are consistent with a standard Azure Active Directory export: full names, employee ID numbers, corporate email addresses, phone numbers, job titles, postal addresses, and in some listings, service accounts and Global Administrator entries. That last category matters more than the headline record counts — a directory that identifies which accounts hold administrative privileges gives an attacker a map for follow-on phishing rather than just a contact list.
Cybercrime intelligence firm Hudson Rock, which first reviewed the leaked samples, says it has high confidence the data itself is authentic — the field structures and domain formats match standard Azure directory exports rather than looking fabricated. What Hudson Rock has not confirmed is the access vector: how TheHatman actually got in remains unverified, and BleepingComputer notes it has not been able to independently confirm the data’s authenticity either.
What “stolen from Azure” actually means here. None of the coverage or Hudson Rock’s research points to a flaw in Microsoft’s platform itself. The consistent explanation across reporting is compromised credentials — obtained through infostealer malware, phishing, or accounts without multi-factor authentication enforced — used to log into individual companies’ Azure and Entra tenants and export their directory data. It’s a credential theft story wearing an Azure name, not a story about Azure being broken.
How researchers say this happened
Hudson Rock’s working theory centres on infostealer malware — the kind that harvests saved passwords and active session tokens from an infected employee’s machine — which researchers say they were able to link to compromised Azure credentials tied to accounts at most of the named companies. Beyond that starting point, several routes could account for how a stolen login turned into a full directory export: phishing that yielded administrative access, tenants without strict multi-factor authentication, or a third-party integration with broader read permissions than it needed.
The pace and consistency of the postings — one directory after another, over roughly two weeks, all following the same format — points toward a repeatable process rather than a series of one-off intrusions, though the exact mechanism has not been confirmed by any of the named organisations.
Two companies dispute the claim
Tata Consultancy Services filed a notification with the National Stock Exchange of India stating it had investigated the allegation and found no credible evidence of a breach affecting TCS systems or customer environments. The company went further than a general denial: TheHatman’s listing claimed password spraying and MFA fatigue as the attack vector, and TCS stated it has had strong safeguards against both techniques in place for more than two years. TCS’s position, as reported by BleepingComputer, is that the data being circulated is at least four years old and limited to basic employee information.
Gap Inc. gave BleepingComputer a similar statement, saying its preliminary investigation found the advertised data limited in scope, non-sensitive, and dated back several years, with no evidence its corporate systems had been compromised.
McDonald’s, Vodafone and Wyndham had not issued a public response at the time this article was published, and Microsoft has not commented on the campaign. No company has confirmed a breach.
What these denials do and don’t settle. A company finding no evidence of a current breach in its own systems doesn’t rule out that the underlying data is genuine but old, that it originated from a third-party vendor or contractor rather than the company’s own tenant, or that it was gathered through a route the seller is misrepresenting. Old, real data can still cause real harm — email formats, job titles and organisational structure don’t expire even if the specific employee named has moved on.
Why this matters even if some of it is exaggerated
Employee directory data doesn’t unlock a bank account, but it’s the raw material for the attacks that do. A phishing email that gets someone’s name, exact job title, direct manager and company email format right is far more convincing than a generic one — and identifying which accounts carry Global Administrator rights tells an attacker exactly who to target for maximum access if a single phish lands.
For organisations, not just the ones named, the practical response isn’t waiting to see whether this specific seller’s claims hold up. It’s the standing basics: enforcing multi-factor authentication across every Azure and Entra account without exception, auditing which third-party integrations have directory read access and scoping that down, and treating any infostealer detection on an employee device as a reason to rotate that person’s credentials immediately rather than after the fact.
For individuals, the relevant risk isn’t that your password was exposed in this dataset — it’s that your name, job title and company email format now make you a more convincing phishing target. Being alert to unexpected emails that reference accurate internal details, even from someone claiming to be a colleague or manager, is the practical takeaway regardless of whether you work at one of the nine named companies.
My Take — Mr Wangdoo
The number that gets repeated in every headline on this — 3.6 million records — is doing a lot of work it probably shouldn’t. It’s the seller’s own claimed total, not an independently audited figure, and two of the nine named companies have already pushed back on the underlying premise. That doesn’t mean the story is nothing. Hudson Rock says the samples it reviewed carry the hallmarks of genuine Azure directory exports, and genuine or not, the method being described — credential theft feeding into automated data harvesting — is exactly the kind of low-effort, high-yield attack that keeps working because basic account hygiene keeps lagging behind it.
What I’d watch for next isn’t whether the total record count holds up. It’s whether any of the remaining seven companies follow TCS and Gap’s lead and go on the record, and whether Microsoft or any of the named organisations confirm the entry point rather than leaving it at “compromised credentials,” which currently covers everything from a phished employee to a poorly scoped API key.
Common questions
Who is TheHatman?
An alias used by a threat actor selling the datasets on cybercrime forums. No real-world identity has been publicly attributed to the name in the reporting so far.
Was Microsoft Azure itself hacked?
Nothing in the current reporting points to a vulnerability in Microsoft’s platform. The consistent explanation is that individual companies’ Azure and Entra tenant accounts were accessed using stolen login credentials, not a flaw in Azure or Entra as a service.
Has any company confirmed the breach?
No company has confirmed a breach. Two named companies have disputed the claim: TCS says it found no credible evidence of a breach and that the circulating data is at least four years old, and Gap Inc. gave a similar statement, describing the data as limited, non-sensitive and several years old. McDonald’s, Vodafone and Wyndham had not issued a public response, and Microsoft has not commented, at the time of writing.
What kind of data is in the datasets?
Reporting describes employee names, corporate email addresses, phone numbers, job titles, employee ID numbers, manager relationships, and in some cases service account and Global Administrator listings. No payment card data or customer financial information has been reported as part of these specific listings.
What should affected employees do?
Treat unexpected emails referencing accurate internal details — your manager’s name, your job title, your employee ID — with more scrutiny than usual, since that’s the practical risk this kind of data creates. Reporting suspicious messages through your company’s normal channel remains the most useful individual step.
Sources
- Hudson Rock — original research on the compromised Azure credentials and affected organisations, as cited across the reporting below.
- BleepingComputer — on TCS’s National Stock Exchange of India filing, TCS’s dispute of the claimed attack vector, and Gap Inc.’s statement denying a breach. bleepingcomputer.com
- The Register — on the full list of nine named organisations and record counts. theregister.com
- SecurityWeek — on the exfiltration method and threat actor attribution. securityweek.com
- GovInfoSecurity — on the forum posting timeline and data fields included. govinfosecurity.com
- Help Net Security — on the full company list and researcher analysis. helpnetsecurity.com