1 / 24

Borrowed from Brent ByungHoon Kang, GMU

Botnets. Borrowed from Brent ByungHoon Kang, GMU. Borrowed from Brent ByungHoon Kang, GMU. A Network of Compromised Computers on the Internet. IP locations of the Waledac botnet . . Borrowed from Brent ByungHoon Kang, GMU. Botnets.

louisa
Télécharger la présentation

Borrowed from Brent ByungHoon Kang, GMU

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Botnets Borrowed from Brent ByungHoon Kang, GMU

  2. Borrowed from Brent ByungHoon Kang, GMU A Network of Compromised Computers on the Internet IP locations of the Waledacbotnet.

  3. Borrowed from Brent ByungHoon Kang, GMU Botnets • Networks of compromised machines under the control of hacker, “bot-master” • Used for a variety of malicious purposes: • Sending Spam/Phishing Emails • Launching Denial of Service attacks • Hosting Servers (e.g., Malware download site) • Proxying Services (e.g., FastFlux network) • Information Harvesting (credit card, bank credentials, passwords, sensitive data.)

  4. Borrowed from Brent ByungHoon Kang, GMU Botnet with Central Control Server After resolving the IP address for the IRC server, bot-infected machines CONNECT to the server, JOIN a channel, then wait for commands.

  5. Borrowed from Brent ByungHoon Kang, GMU Botnet with Central Control Server The botmaster sends a command to the channel. This will tell the bots to perform an action.

  6. Borrowed from Brent ByungHoon Kang, GMU Botnet with Central Control Server The IRC server sends (broadcasts) the message to bots listening on the channel.

  7. Borrowed from Brent ByungHoon Kang, GMU Botnet with Central Control Server The bots perform the command. In this example: attacking / scanning CNN.COM.

  8. Borrowed from Brent ByungHoon Kang, GMU Botnet Sophistication Fueled by Underground Economy • Unfortunately, the detection, analysis and mitigation of botnets has proven to be quite challenging • Supported by a thriving underground economy • Professional quality sophistication in creating malware codes • Highly adaptive to existing mitigation efforts such as taking down of central control server.

  9. Borrowed from Brent ByungHoon Kang, GMU Emerging Decentralized Peer to Peer Multi-layered Botnets • Traditional botnet communication • Central IRC server for Command & Control (C&C) • Single point of mitigation: • C&C Server can be taken down or blacklisted • Botnets with peer to peer C&C • No single point of failure. • E.g., Waldedac, Storm, and Nugache • Multi-layered Architecture to obfuscate and hide control servers in upper tiers.

  10. Borrowed from Brent ByungHoon Kang, GMU Expected Use of DHT P2P Network Publish and Search • Botmasterpublishes commands under the key. • Bots are searching for this key periodically • Bots download the commands • =>Asynchronous C&C

  11. Borrowed from Brent ByungHoon Kang, GMU Multi-Layered Command and Control Architecture Through P2P • Each Supernode (server) publishes its location (IP address) under the key 1 and key 2 • Subcontrollers search for key 1 • Subnodes (workers) search for key 2 • to open connection • to the Supernodes • => Synchronous C&C

  12. Borrowed from Brent ByungHoon Kang, GMU Current Approaches to Botnet • Virus Scanner at Local Host • Polymorphic binaries against signature scanning • Not installed even though it is almost free • Rootkit • Network Intrusion Detection Systems • Keeping states for network flows • Deep packet inspection is expensive • Deployed at LAN, and not scalable to ISP-level • Requires Well-Trained Net-Security SysAdmin

  13. Borrowed from Brent ByungHoon Kang, GMU Conficker infections are still increasing after one year!!! There are millions of computers on the Internet that do not have virus scanner nor IDS

  14. Borrowed from Brent ByungHoon Kang, GMU Botnet Enumeration Approach • Used for spam blocking, firewall configuration, DNS rewriting, and alerting sys-admins regarding local infections. • Fundamentally differs from existing Intrusion Detection System (IDS) approaches • IDS protects local hosts within its perimeter (LAN) • An enumerator would identify both local as well as remote infections • Identifying remote infections is crucial • There are numerous computers on the Internet that are not under the protection of IDS-based systems.

  15. Borrowed from Brent ByungHoon Kang, GMU How to Enumerate Botnet • Need to know the method and protocols for how a bot communicates with its peers • Using sand-box technique • Run bot binary in a controlled environment • Network behaviors are captured/analyzed • Investigating the binary code itself • Reversing the binary into high level codes • C&C Protocol knowledge and operation details can be accurately obtained

  16. Borrowed from Brent ByungHoon Kang, GMU Simple Crawler Approach • Given network protocol knowledge, crawlers: • collect list of initial bootstrap peers into queue • choose a peer node from the queue • send to the node look-up or get-peer requests • add newly discovered peers to the queue • repeat 2-5 until no more peer to be contacted • Can’t enumerate a node behind NAT/Firewall • Would miss bot-infected hosts at home/office!

  17. Borrowed from Brent ByungHoon Kang, GMU Passive P2P Monitor (PPM) • Given P2P protocol knowledge that bot uses • A collection of “routing-only” nodes that • Act as peer in the P2P network, but • Controlled by us, the defender • PPM nodes can observe the traffic from the peer infected hosts • PPM node can be contacted by the infected hosts behind NAT/Firewall

  18. Borrowed from Brent ByungHoon Kang, GMU Crawler and Passive P2P Monitor (PPM) PPM Crawler PPM PPM

  19. Borrowed from Brent ByungHoon Kang, GMU Crawler vs. PPM: # of IPs found

  20. Botnet Enumeration Challenges • DHCP • NATs • Non-uniform bot distribution • Churn • Most estimates put size of largest botnets at tens of millions of bots • Actual size may be much smaller if we account for all of the above

  21. Fast Flux • Botnets use a lot of newly-created domains for phishing and malware delivery • Fast flux: changing name-to-IP mapping very quickly, using various IPs to thwart defense attempts to bring down botnet • Single-flux: changing name-to-IP mapping for individual machines, e.g., a Web server • Double-flux: changing name-to-IP mapping for DNS nameserver too • Proxies on compromised nodes fetch content from backend servers

  22. Fast Flux • Advantages for the attacker: • Simplicity: only one back end server is needed to deliver content • Layers of protection through disposable proxy nodes • Very resilient to attempts for takedown

  23. Fast Flux Detection • Look for domain names where mapping to IP changes often • May be due to load balancing • May have other (non-botnet) cause, e.g., adult content delivery • Easy to fabricate domain names • Look for DNS records with short-lived domain names, with lots of A records, lots of NS records and diverse IP addresses (wrt AS and network access type) • Look for proxy nodes by poking them

  24. Poking Botnets is Dangerous • They have been known to fight back • DDoS IPs that poke them (even if low workers are scanned) • They have been known to fabricate data for honeynets • Honeynet is a network of computers that sits in otherwise unused (dark) address space and is meant to be compromised by attackers

More Related