Sunday, Mar 12, 2017 06:00 AM EDT
WikiLeaks' new trove suggests the CIA could easily fake a Russian hack. It's no smoking gun, but it's disturbing Danielle Ryan

WikiLeaks' new trove suggests the CIA could easily fake a Russian hack. It's no smoking gun, but it's disturbing Danielle Ryan
Enlarge(Credit: AP/Kirsty Wigglesworth/Reuters/Lucas Jackson/Salon/Mireia Triguero Roura)
Russia hacked the election. Russia didn’t hack the election. Russia sort of, maybe, possibly hacked the election.
Is your head spinning from this story yet?
The latest WikiLeaks disclosures concerning the CIA’s hacking abilities has further complicated the hall of mirrors that is the Russian hacking story. The “Vault 7″ leaks are believed to be authentic and reveal a few uncomfortable truths about the overreach of U.S. intelligence agencies.
Reactions to the leaks have varied from those who think they could be more significant than the Edward Snowden revelations to those who think it’s all a bit of a non-story. Basically, it’s a pretty clear split between those who regard WikiLeaks’ editor Julian Assange as a trustworthy whistleblower and those who regard him as a tool of the Kremlin.
Among other things, the leaks revealed that the U.S. government is essentially paying out to exploit the vulnerabilities in software without telling companies and, disturbingly, that they could be using your iPhone or Samsung TV as a microphone — even when it’s supposedly switched off.
One of the most interesting disclosures concerns how the CIA can cover its tracks by leaving electronic trails suggesting the hacking is being done in different places — notably, in Russia. In fact, according to WikiLeaks, there’s an entire department dedicated to this. Its job is to “misdirect attribution” by leaving false fingerprints. If you’ve been at all skeptical about the recent levels of Russia-related hysteria, promoted heavily by U.S. intelligence agencies, alarm bells are probably going off in your head.
Keeping these tactics in mind, the evidence presented to prove that Russia hacked the Democratic National Committee in an effort to throw the presidential election to Donald Trump becomes flimsier than it was before. And it was pretty flimsy to begin with.
Recall, for example, that cybersecurity firm CrowdStrike conveniently concluded within one day that the Russian government was behind the attack on the DNC servers. I say conveniently, because the DNC paid for CrowdStrike’s services — and it’s fair to say the DNC had an unhealthy fixation on all things Russia for the duration of the election cycle.
The evidence provided by CrowdStrike included the fact that malware found on DNC servers was the same as malware believed to be used by Russian intelligence units, that metadata files included information in Cyrillic text, and that emails had been sent using the Russian email service Yandex. In other words, it was nothing the CIA couldn’t have done itself in order to “misdirect attribution.” What’s more, CrowdStrike actually admitted that it deliberately left out evidence that didn’t support its claims that Russia was responsible.
FireEye, a competitor of CrowdStrike, made similar claims on thin evidence. The hackers, they explained, “appeared to cease operations on Russian holidays, and their work hours seem to align with the UTC +3 time zone, which contains cities such as Moscow and St. Petersburg.”
In a thorough and thought-provoking piece on Russian hacking, investigative journalist Yasha Levine picks this “evidence” apart:
Russia hacked the election. Russia didn’t hack the election. Russia sort of, maybe, possibly hacked the election.
Is your head spinning from this story yet?
The latest WikiLeaks disclosures concerning the CIA’s hacking abilities has further complicated the hall of mirrors that is the Russian hacking story. The “Vault 7″ leaks are believed to be authentic and reveal a few uncomfortable truths about the overreach of U.S. intelligence agencies.
Reactions to the leaks have varied from those who think they could be more significant than the Edward Snowden revelations to those who think it’s all a bit of a non-story. Basically, it’s a pretty clear split between those who regard WikiLeaks’ editor Julian Assange as a trustworthy whistleblower and those who regard him as a tool of the Kremlin.
Among other things, the leaks revealed that the U.S. government is essentially paying out to exploit the vulnerabilities in software without telling companies and, disturbingly, that they could be using your iPhone or Samsung TV as a microphone — even when it’s supposedly switched off.
One of the most interesting disclosures concerns how the CIA can cover its tracks by leaving electronic trails suggesting the hacking is being done in different places — notably, in Russia. In fact, according to WikiLeaks, there’s an entire department dedicated to this. Its job is to “misdirect attribution” by leaving false fingerprints. If you’ve been at all skeptical about the recent levels of Russia-related hysteria, promoted heavily by U.S. intelligence agencies, alarm bells are probably going off in your head.
Keeping these tactics in mind, the evidence presented to prove that Russia hacked the Democratic National Committee in an effort to throw the presidential election to Donald Trump becomes flimsier than it was before. And it was pretty flimsy to begin with.
Recall, for example, that cybersecurity firm CrowdStrike conveniently concluded within one day that the Russian government was behind the attack on the DNC servers. I say conveniently, because the DNC paid for CrowdStrike’s services — and it’s fair to say the DNC had an unhealthy fixation on all things Russia for the duration of the election cycle.
The evidence provided by CrowdStrike included the fact that malware found on DNC servers was the same as malware believed to be used by Russian intelligence units, that metadata files included information in Cyrillic text, and that emails had been sent using the Russian email service Yandex. In other words, it was nothing the CIA couldn’t have done itself in order to “misdirect attribution.” What’s more, CrowdStrike actually admitted that it deliberately left out evidence that didn’t support its claims that Russia was responsible.
FireEye, a competitor of CrowdStrike, made similar claims on thin evidence. The hackers, they explained, “appeared to cease operations on Russian holidays, and their work hours seem to align with the UTC +3 time zone, which contains cities such as Moscow and St. Petersburg.”
In a thorough and thought-provoking piece on Russian hacking, investigative journalist Yasha Levine picks this “evidence” apart:


