Former NFL star Le’Veon Bell is under fire after being accused of hypocrisy following anti-trans comments he made online.
Known for sharing his political views, Bell recently explained to followers why he supports Donald Trump, writing on X (formerly Twitter), “I don’t want my daughter to have to compete or share a locker room with men.”
Bell’s remarks sparked backlash, particularly from a transgender sex worker named Lex, who claims Bell privately messaged her despite his public stance. “Outing all DL men, including celebrities that ever hit me up and post about Trump,” Lex announced to her followers, referring to men she says secretly contact her while publicly opposing trans rights.
Expressing her frustration with celebrity men, Lex posted, “Nervous to post what I did, but I have dealt with so many celebrity men over the years and protected them… but to see them being so vile like they don’t fantasize about us constantly.”
Lex then revealed what she alleges are direct messages from the former football player. In the DMs, Bell supposedly asked if she visits L.A. and requested her number, showing a striking contrast to his public anti-trans rhetoric. To back her claims, Lex shared a screenshot allegedly showing a message from Bell, captioned, “Spewing this rhetoric when… and yes, this was on my NSFW page; he knew I was a doll.”
Reflecting on the impact of her reveal, Lex added, “The m@ga outing was deserved. I don’t know if it’s okay to post the rest seeing how big this got.”
Not everyone was supportive of Lex’s actions. One user criticized her, commenting, “You exposed a man’s DM msg bc you disagree w his political/social statement, and now you’re playing victim when ppl call you out. Stop it.” Lex responded, clarifying, “Not playing victim; I simply just don’t care to talk about it anymore lmfao.”
At the time of writing this article, Bell has not publicly addressed Lex’s accusations.
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