Masked thieves target LA mansions including tennis star's home
Summarised from 2 outlets · Updated 20 Nov, 06:38 · Archive
Two masked intruders broke into US Open champion Sloane Stephens' Sherman Oaks mansion on Tuesday night but fled empty-handed when residents confronted them.
Two masked intruders broke into US Open tennis champion Sloane Stephens' $9.3 million Sherman Oaks mansion on Tuesday night around 9:24pm. The suspects used a crowbar to shatter a glass door to gain entry. Residents inside confronted the intruders, forcing them to flee without taking anything. Stephens was not home at the time, but according to the Daily Mail, housesitters were present and dogs started barking as the suspects entered, waking the occupants. One person inside reportedly shouted 'Get the gun', prompting the intruders to run from the scene.
Around two hours later, another mansion in the Hollywood Hills on Mulholland Drive was targeted by burglars. No one was home at that property, but the homeowners watched the break-in remotely via security cameras. It remains unclear whether anything was stolen in that incident.
Police located the suspects' vehicle and pursued it, but the chase ended after three minutes when the BMW collided with a retaining wall in Gardena. All three burglary suspects were taken into custody, police said.

How it is being reported
- Tennis star Sloane Stephens' Los Angeles mansion targeted by masked burglarsMasked intruders broke into two multi-million dollar mansions in Los Angeles on Tuesday night, including one belonging to tennis star Sloane Stephens.Daily Mail · 20 Nov, 06:17
- Masked thieves invade US Open champ’s $9.3M LA mansionA couple of masked crooks raided the lavish home of US Open tennis champion Sloane Stephens on Tuesday night.New York Post · 18 Nov, 18:50
In this story: Sloane Stephens · Los Angeles · Sherman Oaks · Hollywood Hills · Gardena
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)