Scenario: Joe turns on his home computer to access personal online banking. When he enters as if he has never visited the site before. When he examines the website URL closer, he finds that the site…

Question

Options

• ADos attack
• BDHCP spoofing
• CARP cache poisoning
• DDNS hijacking

• A
  14% (8)
• B
  4% (2)
• C
  7% (4)
• D
  75% (42)

Explanation

DNS Hijacking Explained

Why D is Correct: DNS hijacking occurs when an attacker manipulates DNS resolution to redirect a user to a fraudulent website instead of the legitimate one. Joe's experience - being treated as a first-time visitor, an insecure site, and an altered URL - are classic indicators that his DNS requests were intercepted and rerouted to a spoofed banking site designed to steal credentials.

Why the Distractors are Wrong:

• A (DoS Attack): A Denial of Service attack blocks access to a service entirely - Joe would simply be unable to reach the site, not redirected to a fake one.
• B (DHCP Spoofing): While DHCP spoofing can lead to DNS hijacking by assigning a rogue DNS server, it is the underlying network attack, not what Joe is directly experiencing at the browser level.
• C (ARP Cache Poisoning): ARP poisoning manipulates MAC-to-IP mappings on a local network, and while it can facilitate traffic interception, it doesn't specifically alter web addresses or redirect domain lookups.

Memory Tip: Think DNS = Domain Name System = "Dirty Name Swap" - attackers swap the legitimate domain name's destination for a malicious one, which is exactly why the URL looks different to Joe.

No community discussion yet for this question.