TODAY’S PAPER | September 16, 2026 | EPAPER

Meghan Markle's personal mobile number leaked in school WhatsApp group amid security concerns

The Duchess of Sussex joined the group before Prince Archie and Princess Lilibet were due to begin at a UK school


Pop Culture & Art September 16, 2026 1 min read
Photo: Reuters

Meghan Markle reportedly sparked a security alert after her personal mobile number was leaked in a WhatsApp group for school parents, according to The Sun.

The Duchess of Sussex joined the group the night before Prince Archie and Princess Lilibet were due to begin at a UK school.

In messages shared by the outlet, two mothers welcomed Markle, with one writing, “Welcome to Meghan who has Archie joining tomo.”

Markle replied, “Hi moms! Thanks for the warm welcome ❤️ So happy to be a part of this community xx.”

The conversation was later screenshotted by someone in the group, with the messages and Markle’s phone number subsequently shared multiple times.

The reported leak comes after Markle and Prince Harry moved their children from the UK school just two days after classes began, amid concerns about security arrangements.

Hello! Magazine reported that heavy traffic around the school was placing pressure on the couple’s small security team.

“The decision for the children to move school was taken following a discussion with the family’s security team about the practicalities of their current arrangements,” a representative for the couple told the outlet.

An insider said security checks had been completed before term began, but the family had been unable to test the school run.

“It’s a real shame, because they absolutely adored the school, the kids and their parents,” the source said.

Meanwhile, the Telegraph reported that Harry and Markle are set to receive new official risk assessments following their return to the UK.

The assessments will consider their new daily routines.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ