Slashdot Mirror


Another 100 Gigabit DDoS Attack Strikes — This Time Unreflected

darthcamaro writes "In March of this year, we saw the first ever 100 Gigabit DDoS attack, which was possible due to a DNS Reflection Amplification attack. Now word is out that a new 100 Gigabit attack has struck using raw bandwidth, without any DNS Reflection. 'The most outstanding thing about this attack is that it did not use any amplification, which means that they had 100 Gigabits of available bandwidth on their own,' Incapsula co-founder Marc Gaffan said. 'The attack lasted nine hours, and that type of bandwidth is not cheap or readily available.'"

20 of 93 comments (clear)

  1. Is that all? by Anonymous Coward · · Score: 5, Funny

    It was probably just one guy in Tokyo using his $9/month internet package ...

    1. Re:Is that all? by goddidit · · Score: 5, Funny

      On his mobile, to be exact.

      --
      This .sig is exactly 120 characters long.
    2. Re:Is that all? by Cryacin · · Score: 5, Funny

      the guy mistyped the address on the page and hit refresh. Very Very quickly.

      --
      Science advances one funeral at a time- Max Planck
    3. Re:Is that all? by Yaotzin · · Score: 5, Funny

      ...For nine hours.

      --
      Error: No error occurred
    4. Re:Is that all? by wisnoskij · · Score: 5, Funny

      It was a Korean professional Starcraft player.

      --
      Troll is not a replacement for I disagree.
  2. Incapsula by Anonymous Coward · · Score: 5, Informative

    Seriously...this reads like a brochure for Incapsula's services lol

    1. Re:Incapsula by Joce640k · · Score: 5, Interesting

      They don't name the site, they don't name the attacker, the customers were "completely unaffected"....they could be making it up for all we know.

      --
      No sig today...
    2. Re:Incapsula by Anachragnome · · Score: 4, Interesting

      "....this reads like a brochure for Incapsula's services..."

      http://bgp.he.net/AS19551#_whois

      Well, I imagine most US server farms are hurting pretty bad right now, what with all the NSA luvin' going around over here. Now imagine a company that has all of it's servers in the US, Israel and Germany (with a few in Japan)--in light of recent revelations regarding NSA spying--and maybe you'll understand why Incapsula is paying for ads/articles all over the damn place, including /.

      They are fucked, and this marketing blitz is a Hail-Mary attempt to save their ass from the fire that Snowden just lit under it. Personally, I love a good BBQ.

    3. Re:Incapsula by lazybeam · · Score: 5, Informative

      We are an Incapsula customer and I can tell you we were NOT "completely unaffected". We experienced about an hour total of complete down time and several hours of slow response. Our servers were unloaded - no problems when bypassing Incapsula. So I guess they protected us from "that" but in the meantime all sites were unreachable. Though different ISPs had different levels of slowness at different times (trying our two different office connections and three different mobile networks).

      --
      --
      no sig for you. come back one year.
    4. Re:Incapsula by Joce640k · · Score: 4, Interesting

      We are an Incapsula customer and I can tell you we were NOT "completely unaffected".

      Maybe you could call Sean Michael Kerner at eWeek and tell them Marc Gaffan was lying.

      He's also on twitter: https://www.twitter.com/techjournalist

      --
      No sig today...
  3. Is this an ad? by Anonymous Coward · · Score: 5, Insightful

    TFA sure reads like one...

  4. I can't get one thing by ruir · · Score: 4, Insightful

    If they haven't identified the attacker how can they say with 100% certainty it only came from one source, and was un-reflected? For I all I know, you could have a botnet fabricating packets with the same characteristics simultaneously.

    1. Re:I can't get one thing by malacandrian · · Score: 5, Insightful

      That is the point of using a botnet to run a DDoS, yes. A single control signal issues a huge surge in traffic. That doesn't make it an amplified attack though. An amplified attack is when the zombies trick a third party (such as a DNS server) to reply to the victim with more information than you sent them. This can up the size of the attack 100-fold.

  5. no real verifiable info but plenty of product plug by YesIAmAScript · · Score: 5, Informative

    The worst example of advertisement through press release in recent memory.

    At least on slashdot.

    --
    http://lkml.org/lkml/2005/8/20/95
  6. Re:How much bandwidth is that? by Anonymous Coward · · Score: 4, Funny

    It's probably not "100 Gbps/sec" since the seconds cancel out and thus isn't a measure of bandwidth (a 12MB attack would be pretty lame). And since TFS said "bits," not "bytes," all of those options with a capital "B" are also unlikely. So, the answer to your question is "no."

  7. Re:How much bandwidth is that? by TubeSteak · · Score: 4, Informative

    The attack peaked at 100 Gigabits per second
    The webhost (actually a CDN) had 400 Gigabits of total bandwidth available + various DDOS protections in place.

    RTFA

    --
    [Fuck Beta]
    o0t!
  8. Re:How much bandwidth is that? by Anonymous Coward · · Score: 5, Funny

    Using the perl "english words have lower priority than real operators" convention (see "and" v/s "&&"), the / binds more tightly than the "per" operator, and thus, it's Gb / (s/s). And the seconds therefore cancel. ;)

  9. Re:100 GBit isn't large by wonkey_monkey · · Score: 5, Funny

    Thank you Captain Multiplication.

    --
    systemd is Roko's Basilisk.
  10. I know what happened by OhANameWhatName · · Score: 4, Funny

    other than Incapsula and its own service providers that were on the receiving end—no one seemed to notice

    Thanks a bunch for saving the internets Marc. I'll be sure not to notice again soon.

  11. Re:first by oldhack · · Score: 4, Funny

    If you were a Japanese dude with $9/month internet package, you could have been the first. Loser.

    --
    Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.