As you've likely heard by now, Tristan Thompson was caught cheating on a 9-months-pregnant Khloe Kardashian this week.
Some details are still unclear, but everyone agrees that the thing for Tristan to do now is admit he was wrong, devote himself to changing his ways, and maybe even check into rehab.
Unfortunately, one person who doesn't see the value in that agenda is Tristan himself.
Shockingly, Tristan still claims he did not cheat on Khloe.
We're guessing she's not buying it, considering there's an ever-growing mountain of evidence indicating that Tristan has in fact been sleeping around.
Check out the full case against disgraced the Cleveland Cavs foward below...
An Ugly Pattern
Tristan doesn't have the greatest track record when it comes to fidelity. In fact, he left his pregnant girlfriend, Jordan Craig, in order to hook up with Khloe. But sources say he went to great lengths to convince the Kardashians he'd changed his ways. We now know it was all BS...
Yesterday, several reliable media outlets, including TMZ and People magazine, reported that Tristan cheated on Khloe at least twice in the past six months. The news came as Khloe was preparing to welcome a child with Thompson. Now that the couple's baby girl has enetered the world, the stakes couldn't be higher.
And how do we know Tristan has been unfaithful? Well, the outlets that made the original claims came bearing receipts, and it's getting harder and harder for Thompson to play innocent.
The First Incident
The first evidence of Tristan's infidelity is from back in October of 2017. Khloe would have been about three months pregnant at the time.
The Hookah Hookup
Video from the night in question shows Tristan getting intimate with two different women at a hookah lounge. One of the women puts her hand on Thompson's crotch. He later places his face on the other one's breasts.
And That's Not All...
We're sure that probably would have been enough to prompt Khloe to kick her baby daddy to the curb. However, it wasn't long before news of a second, more recent incident emerged...