• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • HomePage
  • About
  • Structure
  • Schedule
    • First Half of the Semester
      • Week 1: Overview of Course
      • Week 2: TCP/IP and Network Architecture
      • Week 3: Reconnaissance
      • Week 4: Vulnerability scanning
      • Week 5: System and User enumeration
      • Week 6: Sniffers
      • Week 7: NetCat, Hellcat
    • Second Half of the Semester
      • Week 8: Social Engineering, Encoding, and Encryption
      • Week 9: Malware
      • Week 10: Web application hacking, Intercepting Proxies, and URL Editing
      • Week 11: SQL injection
      • Week 12: Web Services
      • Week 13: Evasion Techniques
      • Week 14: Review of all topics and wrap up discussion
  • Assignments
    • Analysis Reports
    • Quizzes & Tests
  • Webex
  • Harvard Coursepack
  • Gradebook

ITACS 5211: Introduction to Ethical Hacking

Wade Mackay

Update on Mirai (Krebs DDOS)

October 11, 2016 by Jason A Lindsley 2 Comments

Last week, Noah posted about an here about a DDoS attack that was triggered by a botnet that compromised enough Internet of Things devices to generate 600 Gigabits per second of bogus internet traffic.

Fast forward one week and the code for this DDoS is now publicly available, has a catchy name (Mirai), and has compromised devices in as many as 177 countries.  It is very simple code that targets insecure routers and devices with simple default passwords.

I was at a Cybersecurity panel discussion last week and one of the presenters said that he discovered that one of his zwave devices was recently compromised and was hogging all of the bandwidth on his network.  It made me think of this story and start to wonder about my own network.  So far things seem normal on my network, but has anyone else experienced any of the Mirai symptoms?

 

http://motherboard.vice.com/read/internet-of-things-mirai-malware-reached-almost-all-countries-on-earth

Filed Under: Uncategorized, Week 07: NetCat and HellCat Tagged With:

Reader Interactions

Comments

  1. Noah J Berson says

    October 11, 2016 at 11:37 pm

    The motivations behind selling or releasing a hack are very different. We’ve seen users try to auction off tools for bitcoins in order to profit. Releasing a hack seems like a sign of anger and wanting to see how much damage the hack can do. Hopefully the next step is reverse-engineering and finding a way to patch the vulnerabilities. I think this will be very hard to stop the botnets themselves as a lot of people won’t even know that their DVRs and security cameras are pinging a website over and over. Also, the poster mentioned the DDoS Industry and that they’re already retiring after making their money, which confirms that there is a lot of money in illegal activities.

    Log in to Reply
  2. BIlaal Williams says

    October 19, 2016 at 12:41 pm

    Also, releasing the source code once the Feds are on to you ensures that the source code is in many different places which makes it harder for the authorities to pinpoint. So far I haven’t experienced any symptoms, but I definitely feel that access to the source code is a good way to see how these DDoS attacks work.

    Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Primary Sidebar

Weekly Discussions

  • Uncategorized (133)
  • Week 01: Overview (1)
  • Week 02: TCP/IP and Network Architecture (8)
  • Week 03: Reconnaisance (25)
  • Week 04: Vulnerability Scanning (19)
  • Week 05: System and User Enumeration (15)
  • Week 06: Sniffers (9)
  • Week 07: NetCat and HellCat (11)
  • Week 08: Social Engineering, Encoding and Encryption (12)
  • Week 09: Malware (14)
  • Week 10: Web Application Hacking (12)
  • Week 11: SQL Injection (11)
  • Week 12: Web Services (10)
  • Week 13: Evasion Techniques (7)
  • Week 14: Review of all topics (5)

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in