You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Part 4 Ongoing Allegations... September to December 2016<br />
September 15, 2016 Server Company Provides Analysis of <strong>Hack</strong>er Locations<br />
While nearly all of the servers claimed to be involved in the Russian <strong>Hack</strong>ing attacks<br />
were not in Russia and have failed to provide any analysis from their server logs (I really<br />
wonder why this is because all servers have server logs), one Russian company that was<br />
caught up in the cyber attack did take the time to analyze their logs and issue a press<br />
release with their findings. Since this is what every server company should have done, I<br />
will quote from an English translation of their press release which was written in Russian.<br />
This company has since been attacked as being owned by Russian criminals and I want<br />
to make it clear that I have no way of verifying their report. I am simply quoting them to<br />
show the public what could be done if a server company wanted to help us discover the<br />
truth – namely they should all publish their logs. Also I am certain that the FBI can get a<br />
warrant for all logs of all servers in the US. The fact that the FBI has not done this (or has<br />
not released information about the logs if they have done this) is a strong indication that<br />
the FBI is not really interested in providing the public with additional information about the<br />
locations of communications from the hackers to the servers. Here is the source<br />
document which will be translated for you if you visit the page with a Chrome Browser.<br />
https://chronopay.com/blog/2016/09/15/chronopay-pomogaet-king-servers-com/<br />
Here is an edited version of their press release (I edited to make it shorter by eliminating<br />
text that was not related to the server logs. I also bolded the important parts):<br />
“King Servers (https://www.king-servers.com), which owns servers from which the hacker<br />
allegedly performed attacks on the United States Democratic Party, states the absence of<br />
any «Russian trace» in this cybercrime nor its own involvement...King Servers, owned<br />
indeed by Russian nationals, provides VPS and VDS rental services of the equipment,<br />
physically located in the Netherlands. Earlier, after the FBI alert<br />
(https://s.yimg.com/dh/ap/politics/images/boe_flash_aug_2016_final.pdf) and analysis<br />
from Threat Connect (https://threatconnect.com/blog/state-board -election -rabbit-hole /),<br />
the world's leading media were spreading information about the discovery of the socalled<br />
«Russian trace» in the attacks on the United States democratic party in<br />
Illinois. The «Russian trace» was mostly presented as the use of King Servers services,<br />
stating that the company belongs to Russian citizens. As of September 15, neither King<br />
Servers received any complaints or appeals for any server misuse or abuse, nor any<br />
public authority did any attempts for servers withdrawal. Due to that King Servers found<br />
out about the issue related to that attack only on September 15, at 7 am Moscow time,<br />
and immediately shut down identified servers.<br />
The analysis of the internal data allows King Services to confidently refute any<br />
conclusions about the involvement of the Russian special services in this<br />
attack. Attackers rented two servers using probably fabricated personal and identification<br />
data. After the attack servers were wiped out. However, King Servers maintains logs of<br />
accessing administrative control panel. After log analysis, King Servers obtained a<br />
list of about 60 of all possible IP addresses of «hackers», none of which belongs to<br />
any Russian ip range. Attackers were logging into administrative control panel<br />
mainly from Scandinavian countries (Norway, Sweden) and from the European<br />
Union (Italy).<br />
<strong>Hack</strong> <strong>Everything…</strong> A Detailed Timeline of the DNC <strong>Hack</strong> Page 49