Russell Wilson just put target on Giants' back with stunning injury reveal

Did Russell Wilson just get the Giants in trouble?
New York Giants v Philadelphia Eagles - NFL 2025
New York Giants v Philadelphia Eagles - NFL 2025 | Mitchell Leff/GettyImages

The New York Giants season is over, and now the hunt is on for a new head coach. General manager Joe Schoen is staying put and will lead the search for a head coach. Surely, that was expected to be the only news to come out of Monday, right?

Well, quarterback Russell Wilson stirred up a bit of controversy while speaking with reporters. Wilson admitted that he suffered a grade 2 hamstring strain days before the team's Week 2 game against the Dallas Cowboys. Wilson played in that game, and it had fans and experts wondering if the Giants knew about it the injury and still allowed him to play.

The ProFootballTalk X account shared an article about the Giants potentially being investigated by the NFL due in part to Wilson's admission that he played through an injury that wasn't disclosed to the NFL or the Cowboys before the game.

Wilson responded to the tweet, saying the Giants were not at fault because they had no clue about his injury. Wilson said that he didn't want to tell anyone about the injury.

"Not the Giants' fault! They didn’t know bc I didn’t want to tell anyone bc of the circumstances. I just had to play through it to try and go ball that day! Thought we were going to Win that wild crazy game," wrote Wilson.

Russell Wilson admits he withheld hamstring tear from Giants early in season

These are the comments Wilson made regarding the injury while speaking with reporters on Monday:

"You know, I played that [Week 2] game, you know, I tore my hamstring on Friday in practice — the last play of practice. And I had a grade two [tear]. I couldn’t tell anybody. I had to go and play on it just because I knew the circumstance, I had to play on it, no matter what. I actually ended up going to the Dallas Mavericks’ facility, training. And, you know, kept it quiet, just trying to get treatment on it and just knowing that I probably couldn’t run from the goal line to the 10-yard line if I wanted to, but I feel like, you know, I got to play this game," said Wilson, h/t ProFootballTalk.

Here is an excerpt of what Mike Florio of ProFootball Talk wrote in his article about Wilson and his hidden injury, in the article linked above:

"Still, Wilson admits he had an injury that wasn’t disclosed. He acknowledges he kept it a secret. The question is whether he kept it a secret from the team and, if not, whether the team kept it a secret from the league, from the Cowboys, and from the general public.

"Someone had to know. He went to the Mavericks’ training facility for treatment. Someone there knew. The league will want to know whether anyone from the Giants knew."

It is ironic that Wilson's best game in a Giants uniform arrived days after he tore his hamstring in practice. Facing off against a Cowboys' defense that struggled all year, Wilson threw for 450, three touchdowns, and one interception while completing 30-of-41 pass attempts in the Giants' 40-37 overtjme loss to the Cowboys.

Ultimately, Wilson wasn't able to have a similar performance the next game against the Kansas City Chiefs, where he threw for 160 yards, zero touchdowns, and two interceptions while completing just 18-of-32 throws in the 22-9 loss. This was Wilson's last start for the Giants, as he was benched in favor of rookie Jaxson Dart. Since that change was made, Dart showed he is the future at the quarterback position, while Wilson was mostly delegated to third-sting duties.

Now, the Giants will try and hire a head coach that will build a team and get the most out of Dart. As for Wilson, he is set to be a free agent. Given that Jameis Winston is under contract for next season, Wilson's time with the Giants may be over. One has to wonder if Wilson's comments will ultimately lead to league discipline towards the Giants. We should find out sooner rather than later whether an investigation will take place.

Loading recommendations... Please wait while we load personalized content recommendations