2026 · Data breach

McGraw Hill

Breached 10 April 2026 · Published 16 April 2026 · mheducation.com

THE HUMAN IMPACT

Behind the exposed accounts

In April 2026, education company McGraw Hill confirmed a data breach following an extortion attempt .

Follow the story
A person using a laptop beside a desktop monitor
Logan Jeffrey / Unsplash · Personal research · context photograph, not an affected user
13,500,136Accounts exposed
67/100Severe severity
4Types of data
VerifiedBy HIBP

On 10 April 2026, McGraw Hill was breached. 13,500,136 accounts were exposed, including email addresses, names, phone numbers. MyRecon rates it 67/100, severe. That is about 50% of the population of Australia.

FOLLOW THE RECORD

How the story unfolded

Open a step to read the detail. Missing dates stay unknown.

  1. 01Reported breach date

    2026-04-10

    Read the HIBP source record

  2. 02Entry point

    Attributed to a Salesforce misconfiguration, the company stated the incident exposed "a limited set of data from a webpage hosted by Salesforce on its platform".

    Read the HIBP source record

  3. 03Discovery and disclosure

    A separate discovery or company-disclosure date is not established by this feed record.

    Read the HIBP source record

  4. 04Added to the breach catalogue

    2026-04-16. This is the catalogue date, not necessarily the disclosure date.

    Read the HIBP source record

  5. 05Reported outcome

    13,500,136 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Names, Phone numbers, Physical addresses.

    Read the HIBP source record

Were you part of this breach?

Only a result for this incident is shown. On submission, your email is sent through MyRecon to XposedOrNot for a breach lookup. MyRecon does not save this check to your history. Provider coverage can be incomplete.

Read the disclosure language and the outcome side by side. The company described "a limited set of data from a webpage hosted by Salesforce on its platform". More than 100GB was subsequently published, carrying 13.5 million distinct email addresses. Both statements can be technically accurate at the same time, one describes the surface that was exposed, the other describes what came through it, and that is exactly why a description of the entry point is not a measure of the damage.

The other thing worth noticing is whose data this is. Students and instructors did not choose McGraw Hill; an institution chose it for them, and the record that ended up in a 100GB archive was created as a condition of taking a course. That pattern runs through most education technology breaches, and it is why "stop using the service" is advice that does not apply here.

The story behind the breach

In April 2026, education company McGraw Hill confirmed a data breach following an extortion attempt . Attributed to a Salesforce misconfiguration, the company stated the incident exposed "a limited set of data from a webpage hosted by Salesforce on its platform".

More than 100GB of data was later publicly distributed, containing 13.5M unique email addresses across multiple files, with additional fields such as name, physical address and phone number appearing inconsistently across some records.

Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.

How did it happen?

Attributed to a Salesforce misconfiguration, the company stated the incident exposed "a limited set of data from a webpage hosted by Salesforce on its platform".

What was the motive?

In April 2026, education company McGraw Hill confirmed a data breach following an extortion attempt .

Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.

What was the outcome?

13,500,136 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.

The reported exposed data includes Email addresses, Names, Phone numbers, Physical addresses.

What was exposed, and why it matters

Email addresses

The address becomes a confirmed, active target, expect more phishing, better aimed.

Names

Turns an anonymous address into an identified person, which is what makes targeted phishing possible.

Phone numbers

Enables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.

Physical addresses

Where someone actually lives. Combined with a name this moves the risk off the internet.

What to do if you were in it

Your next steps

Tick off the actions you have taken. Progress lasts while this page is open.

0 actions completed

Questions people ask about this breach

Was my email address in the McGraw Hill breach?

Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.

What data was leaked in the McGraw Hill breach?

email addresses, names, phone numbers, physical addresses. Each one is explained above, along with what it means for the person it belongs to.

When did it happen, and when did it become public?

The breach is dated 10 April 2026. It was published to Have I Been Pwned on 16 April 2026, a gap of 6 days during which the data was already out.

Is the McGraw Hill breach real?

Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.

How many people were affected?

13,500,136 accounts. That is about 50% of the population of Australia. That is accounts rather than people, one person often has several.

Read next

Also in the archive

Case Files: how the landmark breaches actually happened →

Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.

← All breaches