The reason Donald Trump suspected Andrew McCabe was a false story that he refused to publicly refute.
For how long has Trump suspected Andrew McCabe? It seems the answer goes back at least to February of 2017 and a false story in the New York Times. McCabe told the White House that the FBI knew the story was bogus. The story alleged the FBI had evidence of collusion between the Russian government and the Trump campaign.
But even though he knew the story was false, he refused to say so publicly.
And it looks like McCabe is about to be fired!
The Washington Times reports, “White House first became suspicious of McCabe in wake of debunked New York Times story.”
The doubts revolved around a since-debunked February 2017 New York Times story that reported that U.S. intelligence owned numerous intercepts and phone records of Trump campaign officials communicating with Russian intelligence.
As recounted in his new book, “Media Madness,” Fox News reporter Howard Kurtz wrote that then-Chief of Staff Reince Priebus was conducting an intelligence meeting when Mr. McCabe called him aside.
“We want you to know that everything in this New York Times story is bull——,” Mr. Kurtz quotes Mr. McCabe as saying.
The White House was being pounded by the media over the story. The previous month, BuzzFeed posted the infamous Christopher Steele dossier that alleged an “extensive conspiracy” between Moscow and the Trump campaign to interfere in the 2016 election. That charge remains unproven publicly.
Mr. Priebus asked if the FBI would shoot it down. The answer came back, “No,” because then the FBI would have to start commenting on news stories.
“Give me a break,” Priebus said. “I’m getting crushed all over the place, and you won’t say publicly what you told me privately?”
What happened next raised Trump suspicions.
Suddenly CNN broadcast a story casting Mr. Priebus as the bad guy trying to convince the reluctant FBI to knock down an anti-Trump story.
The views expressed in this opinion article are solely those of their author and are not necessarily either shared or endorsed by EagleRising.com