Ransomware Tracker by ExposureDrift
Dashboard / Victims / Microsoft

Microsoft was listed on 26 July 2026 by the ExfilSquad ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). ExfilSquad listed 15 organizations that month and 15 in total.

  • Listed 115 days ago.
  • 948 organizations were listed by all groups in July 2026, see the month.
  • 140 in Technology that month.
  • 317 in US that month.

Updated 2026-11-18 11:12 UTC. Data: public leak-site listings. How we work.

Microsoft corporate emblem
Listed by ExfilSquad Disclosed: 2026-07-26 10:22 UTC

Microsoft

microsoft.com Technology US

Threat Group Post & Evidence

Listed by
ExfilSquad 15 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

DATA SUMMARY: 8M~ records containing: significant PII, employee and customer contact information, authentication data, password hashes, portal identities, corporate account information, business leads, facilities management records, internal service tickets, and access permissions.

Kinds of data mentioned

  • Passwords and credentials

    “…significant PII, employee and customer contact information, authentication data, password hashes, portal identities, corporate account information, business leads, facilities management…”

  • Customer or client data

    “DATA SUMMARY: 8M~ records containing: significant PII, employee and customer contact information, authentication data, password hashes, portal identities, corporate account…”

  • Employee and HR records

    “DATA SUMMARY: 8M~ records containing: significant PII, employee and customer contact information, authentication data, password hashes, portal identities,…”

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with Microsoft (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask Microsoft directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what Microsoft can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, passwords and credentials, employee and hr records.

Within 30 days

  • Keep watching Microsoft A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Microsoft

First 24 hours

  • Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: passwords and credentials, customer or client data.

Within 3 days

  • Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 4 critical panel(s) reachable from the internet.
  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 3 non-production host(s) that are public.
  • Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain microsoft.com
Industry Vertical Technology
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

50/100 • GUARDED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Technology and communications
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 10/25 pts
Baseline: no size or sensitive data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
100/100 • CRITICAL
Last Audited: 2026-11-14 16:23 UTC Passive Recon
Total Network Assets 54
15 hosts • 39 unique IPs
0 cloud-hosted • 7 SaaS
Subdomain Assets 15
Critical Panels 4 (VPN/Admin/SSO)
Non-Prod / UAT 3 Staging/Dev
SaaS Ecosystem 7 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A+ (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Microsoft 365 / Exchange Online
DNS Authority Microsoft Azure DNS
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by ExfilSquad

All →
Wesco International
Manufacturing 2026-07-26 23:50 UTC
Analog Devices
Technology 2026-07-26 10:26 UTC
Bonava
Manufacturing 2026-07-26 10:26 UTC
City of Atlanta
Government & Defense 2026-07-26 10:25 UTC
City of Houston
Government & Defense 2026-07-26 10:25 UTC
Viavi Solutions
Technology 2026-07-26 10:25 UTC