The mystery of the unfortunate guest who had a mishap in a bed at Gwyneth Paltrow's Hamptons home has been resolved, with insiders now identifying the individual involved in the scandal.
The Daily Mail disclosed that Derek Blasberg, a socialite and celebrity ‘hanger-on’, is the person responsible for the embarrassing incident.
Last week, the internet went wild after a blind item in a popular gossip newsletter alleged that Goop founder Gwyneth Paltrow, 51, had to clean up someone's “Ozempic-induced diarrhea” at her home.
However, insiders assert that media personality Derek Blasberg, 42—previously called “one of showbiz’s most well-connected men” —merely used the popular weight loss drug as a convenient excuse before allegedly leaving the property.
“It’s not Ozempic, that’s just what he told everyone,” the insider revealed, explaining how the secret spread through the Hamptons social scene.
“Gwyneth told Oprah, Jerry and Jessica Seinfeld, and Larry David,” they added.
“It’s shocking how many people know this story and how he has managed to keep it out of The Post… probably via his best friend [socialite Dasha Zhukova] - whose mom just married Rupert Murdoch.”
Blasberg is quite familiar with Paltrow's five-bedroom Long Island home, where she held her wedding to Brad Falchuk.
In 2022, the fashion expert shared a photo of himself with the actress, celebrating her 50th birthday at the expansive property.
When discussing their friendship with The Cut, Paltrow confessed she had initially wondered if Blasberg was just a professional socialite.
“When I first met him, I was a little dubious... I was like, ‘Are you are professional best friend of celebrities? And why are you everywhere at once? What's your deal?’”
“After ten seconds, I fell completely in love with him,” she contiued.
Blasberg is renowned for hosting lavish parties attended by celebrities, with his birthday celebrations often seen as a prelude to the Met Gala.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ