
Amid the ongoing controversy surrounding Kim Sae Ron and Kim Soo Hyun, a new report claims that the late actress was married at the time of her death in February 2025.
The YouTube channel Entertainment President, led by journalist Lee Jin Ho, alleges that her family is attempting to suppress details of her marriage to shift blame onto Kim Soo Hyun.
The former couple’s dating scandal has rocked the Korean entertainment industry, with accusations that Soo Hyun dated Sae Ron when she was a minor. However, Lee Jin Ho suggests that Sae Ron was married to another man and living in New York when she passed away.
Photo: Koreaboo
In addition, leaked voice recordings between Kim Sae Ron and a former agency staff member reveal that she was allegedly blackmailed into marriage after an unplanned pregnancy and abortion.
“I was also not going to marry my current boyfriend, and was actually about to break up with him. But then, I suddenly got pregnant,” Kim allegedly said in the recording. When asked about her status, she confirmed, “No, I got an abortion. But because of that, we ended up getting married.”
The recordings suggest her husband exerted control over her life, restricting her access to social media and messaging apps. Kim reportedly deleted KakaoTalk and primarily used Telegram at his insistence.
The YouTube channel Garo Sero Research Institute previously reported that contrary to the information revealed in the leaked recordings, Kim Sae Ron told her family that it was Kim Soo Hyun who instructed her to change her phone, delete KakaoTalk, and use Telegram for communication.
Lee Jin Ho’s report claims that Kim Sae Ron’s family is suppressing key details details while accusing Kim Soo Hyun of misconduct. The growing controversy continues to fuel speculation about the truth behind her final months.
As the situation unfolds, neither Kim Soo Hyun nor Kim Sae Ron’s family has publicly addressed the latest allegations.
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