News for hackers. Stuff that matters.
Re:Technical report on DNC hack [pdf] by cloakandswagger on Thursday December 29, 2016 @05:34PM (#13280782)
That's the real absurdity of this debacle to me.

Many of the whitepapers that I read about the DNC hack listed the attack's "sophistication" as proof that it came from a state actor, yet it was the most routine, simple attack conceivable. No rootkits, no 0 days, just simple phishing and social engineering.

Re:Technical report on DNC hack [pdf] by EthanHeilman on Thursday December 29, 2016 @07:43PM (#13281594)
The report just didn't get into that much detail but they did say:

"the code delivers Remote Access Tools (RATs) and evades detection using a range of techniques."

A "range of techniques" includes things like rootkits.

>No rootkits,

The attackers did use stealthy persistence techniques often called 'rootkits".

"the SeaDaddy implant developed in Python and compiled with py2exe and another Powershell backdoor with persistence accomplished via Windows Management Instrumentation (WMI) system,[..] The Powershell backdoor is ingenious in its simplicity and power" [0]

>no 0 days

The same group used six 0-days in 2015. Either they didn't need to use them in this attack or they used them and deleted the evidence. Senit is APT28 see quote below:

"One of the striking characteristics of the Sednit group is its ability to come up with brand-new 0-day vulnerabilities regularly. In 2015, the group exploited no fewer than six 0-day vulnerabilities" [1]

>yet it was the most routine, simple attack conceivable.

The attack involved multiple pieces of custom written software and carefully researched spearfishing, the attackers spent time and effort to hide their tracks, maintain persistence and exfil data without detection. This level of effort and time does not qualify as routine, some intelligence agencies can't even write their own RATs.

[0]: https://www.crowdstrike.com/blog/bears-midst-intrusion-democ...

[1]: http://www.welivesecurity.com/wp-content/uploads/2016/10/ese...

Re:Technical report on DNC hack [pdf] by smsm42 on Thursday December 29, 2016 @07:52PM (#13281636)
Can't one just buy a RAT?

Also, the WMI think they describe doesn't look like rootkit, more like cron analogue for Windows. I.e. on Unix it would be like installing a command inside crontab. That's not what is usually called a rootkit - a tool that is designed to conceals its presence (and other tools presence) from regular OS tools.

Re:Technical report on DNC hack [pdf] by EthanHeilman on Thursday December 29, 2016 @08:16PM (#13281756)
You can buy RATs. The several RATs used in this campaign were never for sale.

For example the RAT named X-Agent was one of several used in the DNC hack. It has never been put up for sale and it was used in previous Russian intelligence operations (for example tracking Ukraine artillery[0]).

>That's not what is usually called a rootkit

It doesn't appear that anyone has reverse engineered the PC version of X-Agent but the android variant (which may be very different from the one used in the DNC hack) does take some steps to hide itself. Granted nothing suggests anything like kernel syscall hooking but those sorts of rootkit techniques are overrated because they leave obvious and detectable patterns of compromise.

[0]: https://blog.trendmicro.com/trendlabs-security-intelligence/...

Re:Technical report on DNC hack [pdf] by candiodari on Friday December 30, 2016 @12:05AM (#13282645)
So essentially someone hacked the DNC, and it's "advanced" because some custom software was written just for this particular target ?

I've written custom software (which was a lot harder to find than some python WMI hooks) for hacking a lot lower profile organisations. I've consulted for organisations that were hacked by Chinese hackers for bitcoin ransom that had custom software written too. I mean, high profile target, more effort can be expected. It does not mean the government is involved (although a lot of hacking groups seem to have government sidelines in China, though it does not appear to be their primary activity. I mean unless the Chinese government is itself into bitcoin ransoming).

But more seriously, if a component of our government that is this central to our democracy can be hacked by sending emails "open this exe", then ... I mean seriously. Sorry to say, but if that works, you deserve what happens. Is this really the level of competency in the people that are currently organising the government ?

Also the main thing this report does is validate that the information leaked to the press is indeed true (I figured as much, I mean why put so much effort into fighting fake news unless the real target information is not fake ?).

So Hillary and the DNC is in fact in the pocket of wall street. She DID use the DNC organisation to sabotage Bernie Sanders. There are in fact foreign donors to Hillary and the DNC that are illegal under rules that Hillary's government department is supposed to enforce ... this report mostly confirms that this is indeed the view that the top of the DNC has.

Re:Technical report on DNC hack [pdf] by EthanHeilman on Friday December 30, 2016 @09:56AM (#13284624)
The sophistication is not evidence of government involvement, the lack of sophistication is not evidence that a government was not involved.

Certainly malware which costs serious resources to develop, like stuxnet, says something about the capabilities of the attacker. Given that at the high end of the resource spectrum it is mostly governments, resources required are suggestive of a government, but resources are not conclusive in and of themselves.

The attribution of the DNC hack to APT28 and APT29 was not based on its sophistication but on the similarity to the methods used, tradecraft fingerprints, and the sharing of C&C servers to past attacks.

Re:Technical report on DNC hack [pdf] by candiodari on Friday December 30, 2016 @12:15PM (#13285532)
Apparently John McAfee disagrees with you:

https://www.youtube.com/watch?v=aDTKKmBjlwE#t=5m40s

Re:Technical report on DNC hack [pdf] by EthanHeilman on Friday December 30, 2016 @01:24PM (#13286069)
Watched, didn't hear anything that contradicts what I wrote. Can you be more specific?

The closest I can find is when McAfee says: "If it looks like the Russians it isn't the Russians." I said "It looks like the Russians." These statements don't contradict each other.

We do disagree on attribution, but I haven't discussed that in this thread. He is radically skeptical about ever attributing any state sponsored hacking, although in the same interview he does attribute Stuxnet to the US/Israel and the OPM hack to China.

Re:Technical report on DNC hack [pdf] by spinlock on Friday December 30, 2016 @01:40AM (#13282953)
Let's keep the discussion to the technical aspects of the attack. The democrat vs republican antagonism doesn't belong on hacker news.
Re:Technical report on DNC hack [pdf] by thebedyoumade on Friday December 30, 2016 @09:09AM (#13284396)
Then hacker news doesn't belong in human company.
Re:Technical report on DNC hack [pdf] by Redoubts on Friday December 30, 2016 @01:25AM (#13282915)
> Is this really the level of competency in the people that are currently organizing the government ?

  Garrett Graff 
  ... Hillary seems to actually be a very persnickety technology user. She is 
  not very comfortable with most technology, only liked to use a BlackBerry and,
  more specifically, only liked to use a specific type of increasingly older and
  more out-of-date BlackBerry.

  She doesn't know how to use a desktop computer. She--

  Sean Cole 
  Wait, wait, wait. Back up. Back up. She doesn't know how to use a
  desktop computer.

  Garrett Graff 
  Hillary Clinton, the Democratic presidential nominee in 2016,
  does not know how to use a desktop computer, according to multiple sources
  interviewed by the FBI.

  Sean Cole 
  How is that possible?

  Garrett Graff 
  The short answer is, I don't know...

https://www.thisamericanlife.org/radio-archives/episode/601/...
Re:Technical report on DNC hack [pdf] by cenkemuygurt on Friday December 30, 2016 @01:33PM (#13286122)
Just to add to this, Crowdstrike is on the DNC's payroll. Any conclusions they provide should either be met with skepticism or discredited to a degree.
Re:Technical report on DNC hack [pdf] by stefantalpalaru on Friday December 30, 2016 @06:29PM (#13288424)
The Crowdstrike co-founder and CTO is also a Senior Fellow at a think tank that seems particularly giddy about the new Cold War: http://www.atlanticcouncil.org/about/experts/list/dmitri-alp...
Re:Technical report on DNC hack [pdf] by mynameisvinn124 on Thursday December 29, 2016 @06:05PM (#13281010)
"Many breach announcements this year pointed to a “sophisticated attacker” as a narrative of their issue. This usually is followed up by criticism when an initial means of their compromise is revealed.

Most breaches begin with spear phishing, commodity exploits, a leaked key, or some other obvious or preventable detail. However, this is almost never the “sophisticated” aspect of a breach worth talking about. It’s easy to point at an embarrassing vector and dismiss the rest of an attack. Thus, do not judge an adversary by the vector they’ve chosen.

An adversary may show you what “sophistication” means after advancing from their beachhead."

* https://medium.com/starting-up-security/learning-from-a-year...

Re:Technical report on DNC hack [pdf] by cloakandswagger on Thursday December 29, 2016 @06:11PM (#13281048)
Valid point, but I should clarify my original comment: I don't find either aspect of the attack--the entry or the payload--to be particularly sophisticated.

Everything I've read indicates the bulk of work was done by Powershell scripts, along with a backdoor process running in the open. If you told me that the backdoor was a kernel level rootkit or something similar then I could get onboard, but as it stands I don't think the attack's complexity is a solid argument for "Russia did it"

Re:Technical report on DNC hack [pdf] by codedokode on Thursday December 29, 2016 @06:43PM (#13281246)
The main arguments might be not technical. The political emails are pretty boring stuff for an outsider so it should be some government or politician bothering to get them.

I also remember that some gmail accounts of people from DNC staff were hacked. Gmail probably has logged what IP addresses were used when logging in with stolen passwords and they could be used as a hint too (though most probably they point to cheap VPS bought by some anonymous person or Tor node, I doubt anyone would use a stolen password from their real IP address).

Re:Technical report on DNC hack [pdf] by unclepresent on Friday December 30, 2016 @10:52AM (#13284918)
nobody except complete amateurs is using its own computer to do hacking. there are thousands if not millions of compromized computers in aws cloud and similar hosting services that in turn work as robot-hackers to compromise other sites. it is like a self building hacking network where each cell works to infect other cells. so atack, if it was any atack (as document does not have any evidence that it was one) was unlikely be runnig from a real IP but from a random AWS instance registered by some junior software developer from India who bought it to deploy a pet project that was hacked without him even knowing this weeks ago before the event.
Re:Technical report on DNC hack [pdf] by fleitz on Thursday December 29, 2016 @07:04PM (#13281375)
Who else could have forced the DNC to rig the primaries? It's very clear from the collusion between CNN and the Hillary campaign that state level actors were involved.
Re:Technical report on DNC hack [pdf] by lern_too_spel on Thursday December 29, 2016 @07:38PM (#13281551)
Please don't spread fake news about primary rigging, even if tongue-in-cheek. Stick to discussing the article.
Re:Technical report on DNC hack [pdf] by 464192002d7fe1c on Thursday December 29, 2016 @08:09PM (#13281724)
How is primary rigging fake news? Its very obvious from reading the wiki leaks emails that the DNC was brazenly biased towards Hillary and against Sanders.
Re:Technical report on DNC hack [pdf] by praxulus on Thursday December 29, 2016 @08:35PM (#13281843)
Because there's absolutely no evidence that it was rigged? Just because the DNC preferred the lifelong Democrat to the lifelong independent (who could have guessed that?) doesn't mean they couldn't still have operated a fair primary.
Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @12:40AM (#13282766)
The emails show that Sanders was more or less a token opponent kept on a leash and kept in line. Remember also how they cut Sanders out of the DNC voting data. There were no big name Democrats running against Hillary.

They also sucked all the money from the state level campaigns into Hillary's campaign, hurting the entire party when they lost after spending so much money trying to force Hillary through.

https://wikileaks.org/podesta-emails/emailid/22224

https://wikileaks.org/dnc-emails/emailid/11056

https://wikileaks.org/dnc-emails/emailid/5477

https://wikileaks.org/podesta-emails/emailid/24440

https://wikileaks.org/podesta-emails/emailid/10669#efmAO0APK...

https://wikileaks.org/podesta-emails/emailid/5688

https://wikileaks.org/dnc-emails/emailid/9999%20

https://wikileaks.org/podesta-emails/emailid/5423

https://wikileaks.org/dnc-emails/emailid/7643

https://wikileaks.org/podesta-emails/emailid/44131

Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @11:44AM (#13285286)
What specifically did the DNC do to keep Sanders on a leash? My memory of the primaries is far different, with Sanders suing the DNC over access to NGP VAN (which the DNC had cut off until the Sanders campaign showed they had deleted their copies of Clinton's data), loudly complaining about the DNC following the existing rules at the Nevada Convention (http://www.politifact.com/nevada/statements/2016/may/18/jeff...), and generally loudly making unfounded allegations of rigging. Sanders was clearly unleashed, if not unhinged (though the cranky old progressive personality is what I like about him, in much the same way that libertarians are drawn to cranky old Ron Paul).

> They also sucked all the money from the state level campaigns into Hillary's campaign.

You're misreading the Politico article about the Hillary Victory Fund. In that article, the DNC said it was using the initial money to set up common infrastructure for the state parties to use. The money that was supposed to go to the state parties did eventually go to the state parties as you can see here: https://www.opensecrets.org/jfc/summary.php?id=C00586537. To refresh your memory, the first [FEC maximum contribution amount] donated by an individual to the Hillary Victory Fund would go to her primary campaign, the next [max amount] would go to her general election campaign, the next [max amount] would go to the DNC, and the rest would be distributed among the state parties.

Also, I'm curious: whom would you consider a big name Democrat worthy of challenging Clinton not as a token opponent?

Re:Technical report on DNC hack [pdf] by fleitz on Friday December 30, 2016 @11:56AM (#13285361)
Donna Brazille and DWS were respectively fired from CNN and resigned over the corruption.
Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @12:02PM (#13285424)
Donna Brazille wasn't DNC chair until after the primaries were over, so how would she be an example of the DNC rigging the primaries for Clinton?

Wasserman-Schultz resigned to get out of the spotlight, which she believed would put more attention on Clinton for the general election.

We have the DNC's full email history here. Surely if they rigged the primary for Clinton, there would be at least one email showing it.

Re:Technical report on DNC hack [pdf] by astronautjones on Saturday December 31, 2016 @03:05AM (#13290088)
Donna Brazille was fired for leaking debate questions to the HRC campaign
Re:Technical report on DNC hack [pdf] by lern_too_spel on Saturday December 31, 2016 @11:44AM (#13291754)
> Donna Brazille wasn't DNC chair until after the primaries were over, so how would she be an example of the DNC rigging the primaries for Clinton?
Re:Technical report on DNC hack [pdf] by fleitz on Monday January 02, 2017 @12:03AM (#13299167)
Because she sent the emails to the Hillary Campaign. And then was surprise surprise, appointed to the DNC Chair.

You know instead of the Hillary campaign saying, no no, you shouldn't appoint her, we have evidence that she is corrupt, here's the evidence.

And then after the evidence came to light the DNC was like, oh that's fine.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Monday January 02, 2017 @02:02AM (#13299547)
Once again, how is that evidence of the DNC rigging the primaries for Clinton against Sanders? Do you admit that no such evidence exists?
Re:Technical report on DNC hack [pdf] by fleitz on Monday January 02, 2017 @07:46PM (#13305754)
No I don't, to me the emails and the resignations are both evidence and an admission of guilt, to you it might not be.

I hope that Hillary and the DNC are able to get their day in court so the evidence can be heard by a jury of their peers rather than the court of public opinion.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Tuesday January 03, 2017 @11:41AM (#13310380)
> To me the emails and the resignations are both evidence and an admission of guilt.

Be specific. Which emails are evidence of guilt? None of the emails I've seen have shown any evidence of the DNC rigging the primaries. Why would the resignations be evidence of guilt if the stated reasons for resignation are just as plausible?

Do you realize how much you sound like a conspiracy theorist?

Re:Technical report on DNC hack [pdf] by oh_sigh on Friday December 30, 2016 @12:40AM (#13282767)
"Rigging", at least as I read it, doesn't imply cheating - it can just imply that the system is unbalanced or all candidates are not on a level playing field.

For example, if I had to compete against someone in a drawing competition, and one of the judges was the parent of my competitor, and that judge has gone out of his way to train and groom his child for years for this competition, I may lament that the contest is rigged, even if the judge doesn't stuff the ballot box.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @12:52AM (#13282813)
Why is there both a judge and a ballot box in your analogy? In the primaries, there were only ballot boxes, and Clinton got almost 30% more ballots from normal people outside of the DNC than Sanders. It was a landslide so large that the media had to construct a horse race story just to try to keep it interesting.

The DNC had "groomed" Clinton insofar as she had run in the primaries before and was familiar with the rules. She didn't receive any special treatment from the DNC during the primaries as far as their emails showed.

Re:Technical report on DNC hack [pdf] by oh_sigh on Friday December 30, 2016 @01:09AM (#13282870)
Because the judges put their votes in a ballot box. Or because stuffing a ballot box is an idiomatic phrase.
Re:Technical report on DNC hack [pdf] by grzm on Friday December 30, 2016 @12:45AM (#13282785)
Rigging implies fraud, deception, or dishonesty, not just unbalanced.

https://www.merriam-webster.com/dictionary/rigged

See sense 3

1. to manipulate or control usually by deceptive or dishonest means <rig an election>

2. to fix in advance for a desired result <rig the contest>

Editted to add second part of sense 3.

Re:Technical report on DNC hack [pdf] by oh_sigh on Friday December 30, 2016 @01:09AM (#13282866)
Why did you skip the second part of sense 3, which is "to fix in advance for a desired result"?
Re:Technical report on DNC hack [pdf] by grzm on Friday December 30, 2016 @01:20AM (#13282901)
I don't see that it adds anything to contradict the idea that rigging is only something "unbalanced" and not connoting deceit. "Fix in advance" is an example of fraud. I have no issue with including it in my comment, and have updated it to do so.

I'm not sure why you would think otherwise, though if you're implying that the example of extra, specialized training you provided above is an example of "fix in advance", I disagree. To "fix in advance" would mean that the outcome is predetermined, such as by bribes. This sense of fix is here:

https://www.merriam-webster.com/dictionary/fix

7b. to influence the actions, outcome, or effect of by improper or illegal methods <the race had been fixed>

If you have some other meaning implied by your comment, please explain. I find I'm a terrible mind reader.

Re:Technical report on DNC hack [pdf] by travmatt on Thursday December 29, 2016 @09:54PM (#13282156)
But your facts and reasoning regretfully interrupts the circle jerk of the Bernie bros who are convinced their democratic socialist was on the brink of revolutionizing the American political system and finally delivering us to a Denmarkian utopia.

Never mind the fact that Sanders was treated much more gently by the Clinton campaign than Obama was in '08, the only salient fact is that minority voters should have yielded their preference for a man who has spent 30+ years in Washington and yet has largely failed to build any power base.

Re:Technical report on DNC hack [pdf] by epmaybe on Thursday December 29, 2016 @11:44PM (#13282577)
I'm confused by the last sentence. Are you suggesting that more minority voters went for Sanders over Clinton in the primaries? I had thought the exact opposite.
Re:Technical report on DNC hack [pdf] by travmatt on Friday December 30, 2016 @12:06AM (#13282651)
It's sarcasm... the paranoid Sanders voters screaming that the election was rigged often 'forget' (find unacceptable/truly are clueless) that minority voters are the 800lb gorilla of the Democratic Party. In 08 they wanted Obama, and that's who it got. In 16 they wanted hrc and that's who it got. They throw around Clinton's pop vote win as if it showed our system is broken, all while genuinely believing she beat Sanders by cheating, conveniently ignoring the fact that she beat him by a larger margin.
Re:Technical report on DNC hack [pdf] by epmaybe on Friday December 30, 2016 @12:35AM (#13282748)
I have no doubt that Hillary Clinton would have won the primary regardless of the DNC "meddling" in the primary, but I do feel that they would have a more unified DNC had there not been news of the DNC backing HRC before the primaries had even finished.
Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @12:41AM (#13282771)
What "meddling" did the DNC do in the primary? How were they were backing her before the primaries finished?
Re:Technical report on DNC hack [pdf] by belorn on Friday December 30, 2016 @10:00AM (#13284650)
> In a May 2016 email chain, the DNC chief financial officer (CFO) Brad Marshall told the DNC chief executive officer, Amy Dacy, that they should have someone from the media ask Sanders if he is an atheist prior to the West Virginia primary.[46][47]

> high-ranking DNC officials discussed the possibility of making Sanders' religion a campaign issue in southern states

Did they do so? If so, thats clear meddling. If not, its shows intent of meddling.

> Paustenbach suggested that a past incident could be used to promote a "narrative for a story, which is that Bernie never had his act together, that his campaign was a mess."

Again, suggestion to do acts of meddling but not clear if they went through with it.

> Wasserman Schultz resigned as DNC chair after the leak, and was replaced by Donna Brazile and the Democratic National Committee issued an apology to Sanders.[52] Speaking on CNN, Sanders responded to the email leak: "...it is an outrage and sad that you would have people in important positions in the DNC trying to undermine my campaign.

Regardless if the intended meddling happed or not, it is clear that even the party itself know that they were in the wrong.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @11:14AM (#13285058)
> Did they do it?

They did not bring up Sanders's religion, so there was no meddling there.

> Paustenbach suggested that a past incident could be used to promote a "narrative for a story, which is that Bernie never had his act together, that his campaign was a mess."

This is out of context. Sanders was attacking the DNC in the media for following pre-agreed-upon rules in Nevada. They were discussing how to respond to those frankly ridiculous attacks. http://www.politifact.com/nevada/statements/2016/may/18/jeff...

> Regardless if the intended meddling happed or not, it is clear that even the party itself know that they were in the wrong.

To recap, we have their full email history here, yet we still can't find a single instance of them acting to rig the primaries against Sanders. Wasserman-Schultz resigned to get out of the spotlight, which she believed would put more attention on Clinton for the general election.

Re:Technical report on DNC hack [pdf] by epmaybe on Friday December 30, 2016 @12:59AM (#13282840)
I was referring to the emails that showed clear favoritism for Clinton over Sanders. I put meddling in quotations because it wasn't necessarily actual instances, but rather the way the DNC treated one of their candidates that left a sour taste in many Sanders supporters mouths.

That led to a lot of acquaintances of mine that supported Sanders to continue bashing Clinton after the primaries were already over, when it would have been really helpful for the Democratic party to have been unified throughout all of that.

Re:Technical report on DNC hack [pdf] by travmatt on Friday December 30, 2016 @08:06AM (#13284168)
I think that's the exact delusion I'm referring to. I think many Sanders supporters genuinely believe that since they have a clear preference for a candidate, that their preference is the only valid option and other people simply aren't allowed to make their own choice.

Again, I refer to them as delusional because the '16 primary fight was about 1/3 as dirty as the '08 primaries, and somehow Sanders supporters feel being treated gently isn't good enough, what they expected was a clear majority of democratic voters to simply hand over the reins of the Democratic Party. They truly expected politics to revolutionize itself because of Sanders presidential run, and somehow tricks would not be a part of politics instantly and forevermore.

I think my big takeaway regarding the primaries is that most 'progressive' Sanders voters simply wanted to hurt the American establishment, and if they couldn't do it with Bernie they wanted to cry, pick up their ball, and go home.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Thursday December 29, 2016 @08:54PM (#13281929)
Biased? Yes, the DNC would obviously prefer a Democrat to an independent. Rigged? There was no evidence of any rigging outside of fake news.
Re:Technical report on DNC hack [pdf] by jessaustin on Friday December 30, 2016 @12:42AM (#13282775)
Here you're using a common everyday definition of the verb "rig". Observe that this definition excludes e.g. publicizing a political candidate's banal episodes of tawdriness to the scrutiny of voters, so it's not the definition in wide use in USA news media over the last month or so.
Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @10:59AM (#13284953)
I'm using rig in a broad sense. The DNC didn't publicize banal episodes of tawdriness to the scrutiny of voters. If you're talking about the NGP VAN data access, that hit the news on 12/17/2015 when Michael Briggs (Sanders's communications aide) talked about it to BuzzFeed, and the story blew up on 12/18 when the Sanders campaign filed a lawsuit against the DNC over temporarily shutting down their access to the system until they could show that they had deleted any copies they might have had of the Clinton campaign's data.
Re:Technical report on DNC hack [pdf] by jessaustin on Friday December 30, 2016 @02:35PM (#13286718)
That's the point. Rigging an election consists of stuffing ballot boxes or intimidating voters or something like that. Phishing John Podesta is the sort of thing that used to be called "opposition research" (assuming arguendo that the phishing party actually cared who won).
Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @05:12PM (#13287937)
I'm sorry, but I don't see what phishing Podesta has to do with fleitz's claim that the DNC rigged the primaries.
Re:Technical report on DNC hack [pdf] by jessaustin on Friday December 30, 2016 @06:49PM (#13288511)
Perhaps you've missed the last month of news media output; congratulations! There has been a great deal of innuendo about hackers rigging our election under V. Putin's direct command. Here's the top of Google News just now when I checked: [0] This fine polemic starts with a lamentation of Podesta's email security, mumbles through some baseless speculation about fake news and voting machine hacks, then admits to that baselessness before winding up to this breezy pronouncement: "The bottom line is that as dangerous as actual attempts to compromise voter outcome are, the perception that voting results are flawed is also capable of delegitimizing the democratic process. If citizens believe the vote has been rigged, then why bother voting at all?"

One might note that this author stops short of saying rather than merely insinuating that "publishing emails" constitutes "rigging an election", but he sure wrote a lot of words in that effort.

[0] http://www.cnbc.com/2016/12/29/russia-election-hack-obama-re...

Re:Technical report on DNC hack [pdf] by lern_too_spel on Saturday December 31, 2016 @11:48AM (#13291773)
I haven't missed that at all. It just has absolutely nothing to do with fleitz's claim that the DNC rigged the primaries.

Maybe you are not an American. Do you know what the primaries are?

Re:Technical report on DNC hack [pdf] by jessaustin on Saturday December 31, 2016 @06:12PM (#13293706)
Does the definition of "rig" change from the primaries to the general?
Re:Technical report on DNC hack [pdf] by lern_too_spel on Sunday January 01, 2017 @11:07AM (#13296120)
We were discussing fleitz's claim that the DNC rigged the primaries for Clinton. I assert that they didn't. I'm still not sure what you're claiming or whom you think you are disagreeing with.
Re:Technical report on DNC hack [pdf] by marxmarv on Friday December 30, 2016 @12:25AM (#13282716)
Imaginary friends don't have legitimate interests.
Re:Technical report on DNC hack [pdf] by avn2109 on Thursday December 29, 2016 @07:36PM (#13281546)
>> "An adversary may show you what “sophistication” means after advancing from their beachhead."

Sure, that's obviously true in general, but given the current absence of evidence of "sophistication," there is no reason to assume its presence.

Re:Technical report on DNC hack [pdf] by smsm42 on Thursday December 29, 2016 @07:53PM (#13281648)
Journalists routinely do that - underline that whatever malfeasance is done, the perpetrator is not a usual random criminal but especially heinous one and thus this story is worth your attention.

With computer crime it's especially obvious because most journalists don't know enough to understand what's hard and what's not, so they take the word of law enforcement, and law enforcement has big motivation to make it sound as bad as possible, since it enhances their significance and their success for catching one. "I've caught a sophisticated hacker" sounds better than "I've found a 13-year old kid that sent someone an email saying 'give me your password' and the poor shmoe was silly enough to do just that".

So there won't be a lot of reports about catching unsophisticated hackers. Usually it's always "highly sophisticated" ones.

OTOH, I think the actual (claimed) proof was using of certain bit.ly account etc. not sophistication per se.

Also, it looks like there were at least 3 attacks on the DNC, and phishing was only involved in one. Maybe the whitepapers talked about the other ones.

Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @12:54AM (#13282822)
This is the spear phishing email that we have every reason to believe got Podesta that happened not long before the dump ends:

https://wikileaks.org/podesta-emails/emailid/34899

This is the stats page for the bit.ly phishing link from that email showing two clicks in the right time frame:

https://bitly.com/1PibSU0+

It's not rocket science to dump the emails out of a Gmail account:

https://support.google.com/accounts/answer/3024190?hl=en

But the Podesta leaks aren't the same as the DNC leaks, which Wikileaks has long claimed came from an insider who was upset by their treatment of Bernie. It's also interesting to note that even if the DNC was hacked, that doesn't actually prove where the information given to Wikileaks came from.

Given how careless they are in other regards, I have to think that any insider that wants it can get their data. Just read the PDF on this email to see how Colin Powell & Hillary Clinton treat OPSEC: https://wikileaks.org/clinton-emails/emailid/30324

"When I asked why not they gave me all kinds of nonsense about how they gave out signals that could be read by spies, etc. Same reason they tried to keep mobile phones out of the suite. I had numerous meetings with them. We even opened one up for them to try to explain to me why it was more dangerous than say, a remote control for one of the many tvs in the suite. Or something embedded in my shoe heel. They never satisfied me and NSA/CIA wouldn't back off. So, we just went about our business and stopped asking. I had an ancient version of a PDA and used it. In general, the suite was so sealed that it is hard to get signals in or out wirelessly."

Also, the DNC has long been planning to reach for the Putin angle:

"Best approach is to slaughter Donald for his bromance with Putin, but not go too far betting on Putin re Syria. Brent"

https://wikileaks.org/podesta-emails/emailid/25651

Re:Technical report on DNC hack [pdf] by heartbreak on Thursday December 29, 2016 @05:44PM (#13280860)
The sophistication cited by CrowdStrike was the actions taken on the DNC servers, not the initial penetration.
Re:Technical report on DNC hack [pdf] by ethbro on Thursday December 29, 2016 @07:00PM (#13281346)
Exactly, why burn zero-days when you're targeting a technologically unsophisticated adversary with a huge organizational attack surface?

Sure, HDD firmware hacks are cool, but in terms of R&D time far less efficient if you're willing to spam attempts to get in the front door. And I'd say they chose the appropriate level of sophistication given the success of the penetration.

The DNC isn't exactly an air-gapped Iranian nuclear centrifuge.

Re:Technical report on DNC hack [pdf] by CountSessine on Thursday December 29, 2016 @07:44PM (#13281599)
Exactly, why burn zero-days when you're targeting a technologically unsophisticated adversary with a huge organizational attack surface?

Then how is this evidence of a 'state-sponsored actor'?

And how did the narrative of this story ever get derailed from what it should have been, which was, "The DNC, and John Podesta in particular who had both his gmail and his Twitter accounts hacked, are incompetent", to "this is Russian interference in a US election"?

Re:Technical report on DNC hack [pdf] by xapata on Thursday December 29, 2016 @08:05PM (#13281704)
That some people are unfamiliar with computer security is not news. I have known a fair number of big-shot executives and politicians, all of whom I'd expect would click on suspicious links in their email (if they read the email) and double-click on attachments.

The news is why that particular person was targeted.

Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @01:00AM (#13282844)
> The news is why that particular person was targeted.

For which no proof is being presented. Lots of stuff about hacking tools, nothing really about identifying hackers. Lots of anonymous high level sources offering vague assurances and excuses for why we can't present info...

Re:Technical report on DNC hack [pdf] by xapata on Tuesday January 03, 2017 @03:09PM (#13312576)
I can think of two general possibilities. Either (1) there is a conspiracy to mislead the public or (2) showing the proof would reduce our security in some way. I find the latter explanation more plausible.
Re:Technical report on DNC hack [pdf] by CWuestefeld on Friday December 30, 2016 @05:31PM (#13288059)
this is Russian interference in a US election

Although the media and many in politics are saying this, it's plainly false. There is no serious claim that the Russians interfered in our election.

The claims are that the Russians interfered in a presidential campaign. There's a huge difference between the process of campaigning, versus the election process of casting and counting votes.

Sowing this confusion is useful on at least two levels. Most obviously, it serves to undermine the legitimacy of the incoming President. But it's also useful in setting stage for future debate about campaign finance laws. It's important in that debate to keep separate the ideas of election - which the government must protect to ensure its faithfulness to the voters - versus the idea of campaigning, which the government may never interfere with, which is the primary purpose of the First Amendment.

Re:Technical report on DNC hack [pdf] by couchand on Monday January 02, 2017 @03:07AM (#13299739)
It requires some serious mental gymnastics to split those hairs.
Re:Technical report on DNC hack [pdf] by smsm42 on Thursday December 29, 2016 @07:55PM (#13281657)
There are a lot of people who would benefit from the latter conclusion and not a lot of people who would benefit from the former.
Re:Technical report on DNC hack [pdf] by xapata on Thursday December 29, 2016 @08:06PM (#13281707)
> not a lot of people

There are many Republicans.

Re:Technical report on DNC hack [pdf] by smsm42 on Thursday December 29, 2016 @08:12PM (#13281743)
Republicans as such don't have a lot of motivation to prove DNC incompetence by them being hacked, now that Republicans won the election - that would be much larger claim that DNC is less than competent than being hacked.
Re:Technical report on DNC hack [pdf] by xapata on Friday December 30, 2016 @01:31AM (#13282933)
Your assertion does not persuade me.
[dead]
Re:Technical report on DNC hack [pdf] by cloakandswagger on Thursday December 29, 2016 @09:40PM (#13282100)
I'd prefer something a bit sturdier than circumstantial evidence if we're going to accuse a nuclear superpower of cyber warfare.
Re:Technical report on DNC hack [pdf] by ethbro on Friday December 30, 2016 @06:59AM (#13283939)
And sometimes defectors drink polonium-210 and die from radiation poisoning.

The world doesn't come with nice "I did it" notes. You make the best decisions you can with the information you have.

Re:Technical report on DNC hack [pdf] by randyrand on Thursday December 29, 2016 @05:51PM (#13280900)
Could you elaborate? Once you have a password shouldn't it be as easy as just downloading all the emails? Any email client should have the functionality built in.

edit: seeing some reports they used "sophisticated" SQL injection... okay...I mean for a lay person it seems sophisticated, sure. But for anyone in the industry it's one of the oldest and easiest tricks in the book.

I really suspect news sources are knowingly exaggerating about the sophistication of this "hack" in order to make up-play Russia's role and downplay the DNC's culpability.

Re:Technical report on DNC hack [pdf] by cloakandswagger on Thursday December 29, 2016 @05:56PM (#13280941)
You can read about the backdoors they used here:

https://www.crowdstrike.com/blog/bears-midst-intrusion-democ...

The summary: One used Powershell modules and Windows Scheduler to run scripts. Another used a combination of Twitter and public sites like Github/Dropbox for command and control.

In my opinion, neither is impressively sophisticated, and a skilled application developer could whip up something similar in a week or two. Using popular sites like Twitter/Dropbox for C&C has been common for years, and you can purchase similar backdoors/RATs for less than $100.

edit: Another interesting point from the link above: the two exploits stole exactly the same info once inside the DNC network. This would obviously be a big no-no for a sophisticated state actor as it doubles your chance of being compromised, but the author explains it away by claiming that Russia's intelligence agencies are disorganized and adversarial.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Thursday December 29, 2016 @07:45PM (#13281603)
Your "summary" leaves out the key points. The SeaDaddy, X-Agent, and X-Tunnel tools used in these attacks have only been used by two groups, using the same control servers each time, on European, American, and World Anti-Doping Agency targets that the Russians had strong motive to attack, with some of the attacks being attributed to Russia by multiple other means.

If it turned out that Russia was not behind these attacks, the scale of the bad publicity for Crowdstrike, Fidelis, Palo Alto Networks, etc. would nearly put them out of business. Unlike you, they have skin in the game and don't make these claims lightly.

Re:Technical report on DNC hack [pdf] by elif on Thursday December 29, 2016 @09:25PM (#13282052)
The problem with relying upon motive and established MO exclusively is that anyone is therefore capable of framing whomever they like.

This is the next generation of warfare, attribution is simply impossible. Even if there existed actual forensic evidence it could not be relied upon.

Reacting to purported attacks at face value will leave you like a 1-layer chess player, potentially acting on behalf of your adversary.

Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @12:36AM (#13282749)
As I said above, the attribution does not rely solely on motive. All private security firms that analyzed the attack have attributed it to Russia, and they would not stake their reputations on such a flimsy argument.
Re:Technical report on DNC hack [pdf] by unclepresent on Friday December 30, 2016 @11:21AM (#13285109)
all private security firms ? name one, please
Re:Technical report on DNC hack [pdf] by lern_too_spel on Friday December 30, 2016 @11:57AM (#13285374)
I named three in my first comment above. There are also Mandiant (FireEye) and SecureWorks. Previous attacks with the same malware were attributed to Russia by Threatconnect and Microsoft, who calls the "Fancy Bear" group "Strontium."
Re:Technical report on DNC hack [pdf] by stefantalpalaru on Saturday December 31, 2016 @03:46AM (#13290205)
> X-Tunnel

That one is more likely to be used by the Chinese: https://www.invincea.com/2016/07/tunnel-of-gov-dnc-hack-and-...

Re:Technical report on DNC hack [pdf] by lern_too_spel on Monday January 09, 2017 @11:23AM (#13357457)
That document is yet another example of laughably poor security analysis.

The Chinese implementation of the XTunnel protocol is in Java (the GitHub project is written in Java, and you can see an embedded JRE in your blog post's link to the Chinese tool in the strings here: https://cynomix.invincea.com/sample/e2101519714f8a4056a9de18...). The FancyBear implementation is not (no embedded JRE here: https://cynomix.invincea.com/sample/f09780ba9eb7f7426f93126b...).

If you want to see how professionals do it, take a look at https://www.eset.com/int/about/newsroom/research/dissection-....

Re:Technical report on DNC hack [pdf] by cmdrfred on Thursday December 29, 2016 @06:06PM (#13281014)
I have personally written that exact tool while learning Python. A RAT using Twitter for C & C. Uses PGP for encryption and verification. The twitter handles for the C & C change based on a hash of Googles lastest Doodle so you can access it without fear of account deletion.

TIL I'm as good as a state level intelligence team.

Hey CIA/NSA we know you are reading this, my contact info is in my profile. Hire me.

Re:Technical report on DNC hack [pdf] by politician on Thursday December 29, 2016 @06:19PM (#13281093)
Tomorrow: "Cyberhacker admits to Russian hacker tools"

> Yesterday, an Internet cyber hacker using the alias "cmdrfred" claimed on "HackerNews", an elite underground hacker site, that he or she personally built the hacking tools used by Russia to breach the DNC email servers and change the outcome of the recent election.

> "I have personally written that exact tool [it] uses ... encryption ... so you can access [the DNC] without fear."

> "I'm as good as a state level intelligence team."

> cmdrfred went on to taunt American intelligence agencies while admitting that he was aware that elite anti-cyberhacking teams from the NSA and CIA were monitoring his operations.

> The owner of HackerNews Paul Graham -- venture capitalist, flamboyant playboy, and known Russian sympathizer -- could not be reached for comment.

Re:Technical report on DNC hack [pdf] by jocro on Thursday December 29, 2016 @07:16PM (#13281426)
> TIL I'm as good as a state level intelligence team.

Not to totally ignore the pithiness, but I feel like your comment touches on something I see a ton here (and elsewhere): an offhand dismissal of the 'state level' intelligence capacity.

At the end of the day, the systems were exploited. That more sophisticated methods went unused should be a measure of efficiency and not necessarily execution. Why break out the trick play if your opponent can't keep from you running it up the middle?

Re:Technical report on DNC hack [pdf] by avn2109 on Thursday December 29, 2016 @07:39PM (#13281566)
True. But the absence of sophistication constitutes evidence neither in favor nor against the "State Actor" hypothesis.
Re:Technical report on DNC hack [pdf] by billions on Thursday December 29, 2016 @08:10PM (#13281734)
Until a Russian name or IP address is provided, the accusations fail to hold water. An incomplete proof is equivalent to "'cause we said so"
Re:Technical report on DNC hack [pdf] by stordoff on Friday December 30, 2016 @12:04AM (#13282642)
If you are targeting a US political entity, using a staging server in Russia probably isn't the worst idea, so unless the IP address directly ties to the Russian government/intelligence services, it's still only weak evidence of Russia's involvement.
Re:Technical report on DNC hack [pdf] by empath75 on Thursday December 29, 2016 @09:13PM (#13282004)
Spoofing ips is absurdly easy.
Re:Technical report on DNC hack [pdf] by cmdrfred on Thursday December 29, 2016 @09:32PM (#13282072)
I agree that IP addresses aren't good evidence but it isn't really possible to spoof TCP in practice.

http://security.stackexchange.com/questions/55279/how-easy-i...

Re:Technical report on DNC hack [pdf] by cmdrfred on Thursday December 29, 2016 @07:55PM (#13281655)
>hat more sophisticated methods went unused should be a measure of efficiency and not necessarily execution. Why break out the trick play if your opponent can't keep from you running it up the middle?

I question how efficient it is to get caught red handed in the cookie jar of the worlds only super power.

Sure Vladimir Putin could invite President Obama to a state dinner and then proceed to blow his head off with an AK-47 but that would lack the subterfuge I expect from "state level actors". If this is indeed the Russians, they are as laughably incompetent as our elected officials in regards to infosec and thus a threat to no one.

Re:Technical report on DNC hack [pdf] by debaserab2 on Thursday December 29, 2016 @08:54PM (#13281931)
Publicly assassinating the president of a country is slightly different then pilfering clumsily guarded emails of campaigning politicians. One starts world wars. The other doesn't.
Re:Technical report on DNC hack [pdf] by Natsu on Friday December 30, 2016 @01:00AM (#13282843)
I'd like to believe that it won't.
Re:Technical report on DNC hack [pdf] by frozenport on Thursday December 29, 2016 @06:55PM (#13281322)
RNC got hacked but nothing was leaked.
Re:Technical report on DNC hack [pdf] by leesalminen on Thursday December 29, 2016 @07:19PM (#13281441)
Source?
Re:Technical report on DNC hack [pdf] by c4mden on Thursday December 29, 2016 @08:37PM (#13281852)
“We now have high confidence that they hacked the D.N.C. and the R.N.C., and conspicuously released no documents” from the Republican organization, one senior administration official said, referring to the Russians. http://www.nytimes.com/2016/12/09/us/obama-russia-election-h...
Re:Technical report on DNC hack [pdf] by ericlavigne on Thursday December 29, 2016 @09:21PM (#13282041)
The article is very unclear. Here's another quote in the same article that says the hacks against the RNC failed. The NY Times is basically telling us that they received conflicting reports from different anonymous and similarly credible sources.

"One senior government official, who had been briefed on an F.B.I. investigation into the matter, said that while there were attempts to penetrate the Republican committee’s systems, they were not successful."