27 January 2006
- and some possible counter measures to prevent phishing attacks
![]() |
Most security organizations hold phishing to be one of the most prevalent threats against computer security during 2006. The Gartner Group estimates that the direct phishing-related loss to US banks and credit card issuers in 2003 was $ 1.2 billion.
Phishing is a complex phenomenon that includes social factors as well as technology. In brief, phishing can be explained as a kind of online identity theft in which confidential information is obtained from an individual or an organization.
Phishing includes
- deceptive attacks, in which users are tricked by fraudulent messages into giving out information
- malware attacks, in which malicious software causes data compromises
- DNS-based attacks, in which the look-up of host names is altered to send users to a fraudulent computer aka “pharming".
- The phisher prepares for attack
- A malicious payload arrives through some propagation vector
- The user takes an action that makes him or her vulnerable to an information compromise
- The user is prompted for confidential information, either by a remote web site or locally by a trojan
- The confidential information is transmitted from a phishing server to the phisher
- The confidential information is used to impersonate the user
- The phisher engages in fraud using the compromised information
Different forms of phishing
Phishing is perpetrated in many different ways. Phishers are technically innovative and are often able to invest in technology. Most phishing attacks are carried out as professional crime schemes. As financial institutions have increased their online presence, the economic value of compromising account information has increased dramatically.
Phishing thus includes many different types of attacks including:
1. Deceptive attacks, in which users are tricked by fraudulent messages into giving information.
The most common method for deceptive phishing today is email. In a typical scenario, a phisher sends deceptive emails, in bulk, with a “call to action" that demands the recipient to click on a link. Examples of a “call to action" include:
- A statement that there is a problem with the recipient’s account data with a financial institution or other businesses. The email asks the recipient to visit a web site to correct the problem, using a deceptive link in the email.
- A statement that the recipient’s account is at risk, and offering to enrol the recipient in an anti-fraud program
- A fictitious invoice for merchandise, often offensive merchandise, that the recipient did not order, with a link to cancel the fake order
- A fraudulent notice of an undesirable change made to the user’s account, with a link to “dispute" the unauthorized change
- A claim that a new service is being rolled out at a financial institution, and offering the recipient, as a current member, a limited time opportunity to get the service for free.
In many cases the phisher does not directly cause the economic damage, but resells the illicitly obtained information on a secondary market.
2. Malware attacks, in which malicious software causes data compromises.
This refers to any type of phishing that involves running malicious software on the user’s machine. In general this malware is spread either by social engineering or by exploiting a security vulnerability. A typical social engineering attack is to convince a user to open an email attachment or download a file from a web site often claiming the attachment has something to do with pornography, salacious celebrity photos or gossip.
Malware attacks can also take place in forms of keyloggers that install themselves either into a web browser or as a device driver, which monitor data input and send relevant data to the phisher’s computer. Web trojans are malicious programs that pop up over login screens to collect credentials.
3. DNS-based attacks, in which the look-up of host names is altered to send users to a fraudulent server.
This refers to any form of phishing that interferes with the integrity of the look-up process for a domain name. This includes host file poisoning, even though the host file is not properly part of the Domain Name System.
This form for phishing is often very sophisticated and is also referred to as “pharming".
How can phishing be prevented?
It is not an easy task to stay fully protected against phishing attacks, but there are some measures that can be taken in order to reduce the danger:
- Monitoring potentially malicious activity such as web site usage and domain registrations made by the users, detecting a phishing attack before it starts, and interrupting the phisher’s preparations. Pre-emptive domain registrations targeting likely spoof domain names may reduce the availability of the most deceptively named domains.
- Authenticating email messages so unauthenticated messages can be discarded. Once a phishing attack is under way, the first opportunity to prevent a phishing attack is to prevent a phishing payload, such as an email or security exploit from ever reaching users. Message authentication provides an assurance that an email was really sent by the party named as the sender. Once widely deployed, email authentication has the potential to prevent forgery of a return address and force a phisher to either reveal a suspicious looking return address, or register an official looking domain name.
- Detecting the unauthorized use of trademarks, logos and other proprietary imagery.
- Improving the security patching infrastructure to increase resistance to malware that utilizes vulnerabilities in installed software. Phishing attacks that involve malware are often installed via an exploit of a security vulnerability. One promising proposal for rapid distribution and application of patches, without leaking vulnerability information, is to distribute focused security patches for specific vulnerabilities encrypted using a separate symmetric key for each patch. The key will be kept secret by each vendor.
- Using personalized information to authenticate an email directly to a user
- Detecting a fraudulent web site and alerting the legitimate organization that is being an indirect victim of the scheme.
- Using mutual authentication protocols
- Establishing a trusted path between the user and a web site to ensure that information can be used only by its intended recipient
