Ian Wright has revealed he has been subjected to vile online racist abuse while Gabriel Agbonlahor has also been targeted.
Former Arsenal and England striker Wright was sent a number of Instagram messages, with leading anti-racism charities condemning the conduct.
An Instagram user messaged Wright with racist taunts prompting the 56-year-old to take to Twitter.
He wrote: “I know I’m not meant to look at them but these messages still hit me so hard man. This is a child!!!
“This kid as a direct line into me & is able to send this without any worry.”
Show Racism the Red Card chief executive Ged Grebby condemned the abuse.
Grebby told the PA news agency: “Ian Wright has put his head above the parapet again and I saw him on Match of the Day with Gary Lineker a few weeks ago talking about the racist abuse he suffered as a player. I’m sure he will be more than happy to report it.
“There was an Asian reporter (Sima Kotecha) yesterday for the BBC and she was abused in the middle of Leicester.
“It shows racism is society’s problem and unfortunately it has been on the rise. People having been staying at home but it doesn’t stop them them abusing people on social media and this is a shocking example of that.”
Former Aston Villa forward Agbonlahor was also sent an abusive and racist message on Instagram and Kick It Out called for those who targeted him and Wright to be punished.
“We are appalled during this very trying time by the disgraceful abuse directed at Ian Wright and Gabriel Agbonlahor and their families,” a statement read.
“Racial hate speech and violent threats are totally unacceptable but have become sadly normalised on social media.
“Whilst we continue to collaborate with social media platforms to ensure a safer user experience for all, these cases should be investigated by law enforcement and the abusers should face criminal sanctions.”
Get the best features, fun and footballing frolics straight to your inbox every week.
Thank you for signing up to Four Four Two. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.