Ransomware Tracker by ExposureDrift
Dashboard / Victims / Milburn

Milburn was listed on 23 September 2025 by the akira ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). akira listed 54 organizations that month and 1678 in total.

  • Listed 422 days ago.
  • 621 organizations were listed by all groups in September 2025, see the month.
  • 51 in Healthcare that month.
  • 318 in US that month.

Updated 2026-11-19 06:01 UTC. Data: public leak-site listings. How we work.

Milburn corporate emblem
Listed by akira Disclosed: 2025-10-03 11:16 UTC

Milburn

milburn.com Healthcare US

Threat Group Post & Evidence

Listed by
Akira 1,678 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.

Milburn is a General Demolition contractor out of Chicago, Illino is. They deploy the latest in demolition technology and equipment with a fleet of Bobcat skid steers and Brokk remote demolition r obots that can tackle everything from structural slab demolition to full interior strip-outs. We are ready to upload more than 16GB data. There are lots of ess ential corporate documents such as: financial data (audit, paymen t details,financial reports, invoices), (passports, driver's lice nse, SSNs , emails, medical information, medical cards) Confident ial information and other documents with detailed personal inform ation.

Amounts as written

  • 16GB

Kinds of data mentioned

  • Accounting and ledgers

    “…There are lots of ess ential corporate documents such as: financial data (audit, paymen t details,financial reports, invoices), (passports, driver's lice nse, SSNs , emails,…”

  • Identity documents

    “…financial data (audit, paymen t details,financial reports, invoices), (passports, driver's lice nse, SSNs , emails, medical information, medical cards) Confident ial information…”

  • Email and communications

    “…details,financial reports, invoices), (passports, driver's lice nse, SSNs , emails, medical information, medical cards) Confident ial information and other documents with detailed…”

  • Medical or patient records

    “…details,financial reports, invoices), (passports, driver's lice nse, SSNs , emails, medical information, medical cards) Confident ial information and other documents with detailed personal…”

Plain-English summary AI-written

The group says it is ready to upload more than 16GB of corporate documents, including financial records and personal information such as identification, email, and medical details.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

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 Milburn (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 Milburn 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 Milburn 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: email and communications, identity documents.
  • Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: accounting and ledgers.
  • If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.

Within 30 days

  • Keep watching Milburn 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 Milburn

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: identity documents, email and communications.
  • Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: accounting and ledgers.

Within 3 days

  • Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
  • 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: identity documents.
  • Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 16GB. Treat group figures as unverified.
  • 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. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
  • Check the ways akira is reported to get in Check these first; they are how the group is reported to work in general.
    • Likely ways in include exploiting SonicWall CVE-2024-40766, stolen VPN credentials, password spraying and flaws in Veeam Backup & Replication. (update of 13 Nov 2025)
    Source: #StopRansomware: Akira Ransomware (AA24-109A) Why: From the public advisory below. It describes the group, not how Milburn was entered.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Healthcare organizations and ask them whether they were affected. Why: akira listed 10 other Healthcare organization(s) in the last 90 days.
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 milburn.com
Industry Vertical Healthcare
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

100/100 • CRITICAL

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 30/30 pts
Healthcare and life sciences
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
63/100 • HIGH
Last Audited: 2026-11-14 17:28 UTC Passive Recon
Total Network Assets 12
3 hosts • 9 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 3
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 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 Custom Mail Gateway (co)
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by akira

All →
Bench Equity
Financial Services 2026-11-18 15:10 UTC
Audiotec
Technology 2026-11-18 15:10 UTC
Flagship Cruises & Events
Hospitality 2026-11-18 14:11 UTC
Optimil Machinery
Manufacturing 2026-11-17 13:40 UTC
The Mandrel Group
Manufacturing 2026-11-16 13:25 UTC
Galorath
Professional Services 2026-11-13 14:19 UTC