Rampage Jackson cuts off contact with son Raja after Syko Stu attack at California wrestling event

Rampage Jackson says he stopped speaking to son Raja after Syko Stu wrestling attack, citing dishonor.


Pop Culture & Art September 04, 2025 1 min read
-Zuffa LLC

Former UFC light heavyweight champion Quinton “Rampage” Jackson says he has cut off communication with his son Raja following a violent altercation involving professional wrestler Syko Stu, explaining that the fallout has strained their relationship.

The rift stems from an August 23 incident at KnokX Pro’s KnokXperience event in California, where Raja allegedly attacked Syko Stu — whose real name is Stuart Smith — during what was meant to be a scripted appearance. The off-script assault left Smith hospitalized with multiple injuries and has since prompted an ongoing police investigation.

Speaking on The Ariel Helwani Show Wednesday, Jackson, 47, admitted he has chosen to distance himself. “I don’t talk to Raja no more,” Jackson said. “I talked to him, I heard his story… then after I learned a whole lot of stuff about it.” He added, “He dishonored my name. I know he’s my son. I’m not cutting him off forever… I just can’t talk to him right now.”

Despite his disappointment, Jackson stressed that his feelings as a father remain complicated. “I still love him, he’s still my son,” he said, noting that tensions have grown since Raja became an adult. “Ever since he’s become an adult he don’t listen to s–t I say.”

Jackson explained that he initially defended Raja after the incident but later accepted that justice should take its course. He has hired an attorney for his son and is waiting for an arrest warrant to be issued. “I did my job as a father, to still take care of my son because I still love him, even though I’m upset at him,” Jackson told Helwani.

For now, Jackson says maintaining distance is the only way he can handle the situation.

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