Live data from Hacker News

China's Man-On-the-Side Attack on GitHub

netresec.com

141–150 of 323 posts

Re: China's Man-On-the-Side Attack on GitHub

#141
post #59

Earlier quoted context omitted.

Hi Djent, Would you mind sending an email to support@github.com with details on what you were doing when that happened? Thanks

It's happening for me constantly - just clicking the link from the discussion - I get a (very) slow page load, then the unicorn page. I'm assuming it's a timeout on the backend.

Last night same for me, browsing the Azure Kuda repo.

Re: China's Man-On-the-Side Attack on GitHub

#143

Earlier quoted context omitted.

>can't stop a little 300 person operation. Police forces can infiltrate world-wide gangs. What's stopping China from infiltrating Github if this DDoS doesn't work out?

Is there any evidence of China infiltrating Microsoft or other major OS vendors?

While I don't know of any cases relating to Microsoft, there have been a number of Chinese spies found in American companies (defence, industrial components, medicine). There's a summary on en.m.wikipedia.org/wiki/Chinese_Intelligence_Operations_in_the_United_States

Re: China's Man-On-the-Side Attack on GitHub

#144

Earlier quoted context omitted.

The difference between the U.S. and China/Russia is that the people in China/Russia know the media is controlled by the powers that be. Here, our press is also "defined by the vision of the oligarchy and information is carefully controlled to produce a desired set of beliefs." We just believe that it's free. See: http://en.wikipedia.org/wiki/Manufacturing_Consent

It is rather stupid to equate the degree of media manipulation in the West vs. China and Russia.

I didn't equate them. I said mind control is worse in the West. And, I cited a detailed analysis of the topic.

Re: China's Man-On-the-Side Attack on GitHub

#145

Can I black-hole all of China in my hosts file? Off the top of my head I'm not going to miss anything, and I'd hate to be an unwitting participant in future attacks.

Using dnsmasq¹: $ echo 'address=/.baidu.com/127.0.0.1' >> /etc/dnsmasq.conf

hosts file blocking is more difficult since you must list each subdomain.

¹everyone should

Re: China's Man-On-the-Side Attack on GitHub

#146
In china, there's lots of similar thing, e.g. your android phone download a app from some site, the ISP(or others in your network path) can detect this(maybe by url) and return a modified version(e.g. add it's own ad or maybe complete a competitor's product of the original app).

Re: China's Man-On-the-Side Attack on GitHub

#147
Netresec should be able to gradually increase the TTL of their packets going to Baidu to see which hop or link is doing the hijack.

They mention someone did this earlier with the iCloud hijack by using mtr and tcptraceroute, but it looks like these tools won't work as-is this time because the Github man-on-the-side attack waits for the HTTP GET request. It's probably stateless and if so could be triggered by a lone ACK with a proper HTTP GET inside. As long as they're not behind a stateful firewall, replaying their ACK at various TTLs to find the smallest TTL that triggers the hijack would probably do the trick.

If the hijackers are clever they could make it look like the compromised hop is further away than it actually is, but not closer. Even so, this could be useful information and I'd love to see the result if anyone tries it.

Edit: changed trace method so that it'd actually work.

Re: China's Man-On-the-Side Attack on GitHub

#148
post #89

Earlier quoted context omitted.

During an ongoing attack? I wonder why not...

Right. Not looking for specifics. My curiosity would be satisfied by something like "we've reached out to Baidu and they've done X and Y. Meanwhile, traffic has decreased so we've unblocked the affected repos." Just a bit more transparency on the situation.

It's not baidu.com that serves that malicious code, it gets inserted on its way through the Great Fire Wall.

Re: China's Man-On-the-Side Attack on GitHub

#149
post #120
post #36

Earlier quoted context omitted.

The injection has been stopped and Baidu's script checks if there exists a referer.

What do you mean "has been" stopped? There's no definitively stopping this without HTTPS, which I'm pretty sure hasn't magically "happened" in China in the last couple days. The GFW may have ceased its attack, but there's no check you can possibly add into an asset delivered over HTTP which can't be undone by the GFW. As long as there's a script being delivered over HTTP, the GFW can intercept that script request and…

There don't even have to be scripts being served -- as long as HTML is being served over HTTP they can inject their own scripts.
Post reply on HN