TODAY’S PAPER | November 19, 2025 | EPAPER

D4vd reportedly named suspect in Celeste Rivas' death investigation

In September, Rivas' body was discovered in a Tesla registered to the singer


Pop Culture & Art November 19, 2025 1 min read
D4vd reportedly named suspect in Celeste Rivas' death investigation

More than two months after 15-year-old Celeste Rivas' body was found in a Tesla registered to his name, singer D4vd now has been named a suspect in connection to her death, an LAPD souce reports.

 

 

The source reportedly told NBC4 that D4vd has not been cooperative during the investigation and even alleged that he probably had help disposing the victim's body, who they believe likely died around spring.

An LAPD spokesperson said they could not confirm the reports, citing the ongoing investigation.

The singer, whose real name is David Anthony Burke, has yet to be charged and no arrests have been made in connection to the investigation. 

While he has yet to address the situation, after the case was opened in September, D4vd transferred ownership of two homes in Houston, Texas, to his mother, according to legal documents obtained by TMZ.

Rivas' body was discovered in the car at a Hollywood impound yard on September 8 when police were called to check the vehicle due to a “foul odor.” The body was later identified as the teen, who had been reported missing on April 5, 2024 from Lake Elsinore, California.

The Tesla had been parked near a home in the Hollywood Hills that D4vd had been staying in before starting his Withered World Tour which has since been cancelled. 

Detectives served a search warrant for the property in late September and reportedly recovered electronics and computers from the Sunset Blvd. home. 

The Los Angeles County Coroner previously told TMZ that Rivas' body was released to her family on September 23, however the cause or manner of her death had not yet been determined.

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