The DNC — Does Not Compute
From last year's hack that maybe didn't actually happen to the criminal IT employees, Democrats have a problem.
For over a year now, we have heard countless leftist accusations about Russia being the primary perpetrator of interference in the 2016 election. To date, there has been little, if any, actual evidence that Russia interfered with the election. However, that’s what the Leftmedia still push because it’s a narrative they want to be true — especially in the case of their beloved Democrat National Committee and all those who have ties to it.
Frankly, the narrative that the Russians interfered, the Russians hacked, the Russians stole and on and on about Russia is an overplayed broken record that has probably tuned more people out to news media than any other story this year. One would think that if Russia truly did have a hand in our election outcome that there would be some evidence. In the case of the supposed hack of the DNC email and records system last year, there has been no evidence found.
There have been numerous cyber experts and intelligence personnel involved with trying to find Russian involvement with the DNC email hack to no avail. With so much time and effort spent on this issue it seems more likely, as Hot Air’s Jazz Shaw puts it, “The absence of evidence might be reasonably interpreted as evidence of absence.”
Furthermore, The Nation — a leftist rag, not a conservative media outlet — recently released a new and detailed report pointing to far more evidence that what happened with the DNC email and records system was not a hack by the Russians, but rather a leak or an inside job from someone who had access to the DNC’s system.
The group of forensic experts and former national security advisers who have been working to get to the bottom of this found that “there was no hack of the Democratic National Committee’s system on July 5 last year — not by the Russians, not by anyone else.” The report further adds, “Hard science now demonstrates it was a leak — a download executed locally with a memory key or a similarly portable data-storage device. In short, it was an inside job by someone with access to the DNC’s system.”
Ok, great, so who did it? Well, we don’t know for sure yet and at this point all anyone can do is speculate. But perhaps that’s why the DNC refused to let the FBI investigate…
But the hack isn’t the only IT problem Democrats face. Remember Imran Awan and company? Senator Chuck Grassley, chairman of the Senate Judiciary Committee, has requested copies of immigration files from six Pakistani suspects including Awan, his wife, two brothers and two close friends.
These individuals are suspected of stealing equipment from Congress and accessing government computers without permission. Awan was arrested last month as he was trying to board a flight to leave the country — after wiring $283,000 to his Pakistani account. Answering the question of how they got here is a pretty important one.
What’s interesting is that Imran Awan was an IT staffer hired by former DNC chairwoman Debbie Wasserman Schultz. She is now playing hard defense and is portraying herself as a victim of “right-wing media” attacks rooted in anti-Muslim bigotry toward Awan and his associates.
She kept Awan on staff until July 25, one day after he was arrested. Yet his brothers were fired six months earlier. So, Wasserman Schultz intentionally kept Awan on staff for a heretofore unknown reason.
What we do know is that the DNC is in shambles right now. If it ever turns out that Awan & Co. were connected to the DNC email leak, then Wasserman Schultz will have a lot of explaining to do. At this point, there’s no evidence of that, but it’s certainly interesting to see the two stories juxtaposed. We suppose that’s what happens when a bunch of political hacks are hacked.