Jump to content

Phishing: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Undid revision 312883116 by Abc518 (talk) Didn't mean to rollback (HG Lagged) Also fixed spelling error.
Line 132: Line 132:
{{Unreferenced section|date=January 2009}}
{{Unreferenced section|date=January 2009}}
{{Essay-like|section|date=February 2009}}
{{Essay-like|section|date=February 2009}}
People have a [[fight-or-flight|built-in reaction]] to things that seem important. Subjects lines worded to arouse anxiety usually prompt immediate action. An email with the subject: "'''to restore access to your bank account ...'''" will usually get instant attention and prompt most people to click to read what happened.
People have a [[fight-or-flight|built-in reaction]] to things that seem important such as hardcore anal sex. Subjects lines worded to arouse anxiety usually prompt immediate action. An email with the subject: "'''to restore access to your bank account ...'''" will usually get instant attention and prompt most people to click to read what happened.


There has been extensive research on the subject.<ref>http://www.securityfocus.com/infocus/1860</ref>
There has been extensive research on the subject.<ref>http://www.securityfocus.com/infocus/1860</ref>

Revision as of 13:44, 14 September 2009

Not to be confused with fishing, pish, or Phish.
An example of a phishing e-mail, disguised as an official e-mail from a (fictional) bank. The sender is attempting to trick the recipient into revealing confidential information by "confirming" it at the phisher's website. Note the misspelling of the words received and discrepancy. Such mistakes are common in most phishing emails. Also note that although the URL of the bank's webpage appears to be legitimate, it actually links to the phisher's webpage.

In the field of computer security, phishing is the criminally fraudulent process of attempting to acquire sensitive information such as usernames, passwords and credit card details by masquerading as a trustworthy entity in an electronic communication. Communications purporting to be from popular social web sites, auction sites, online payment processors or IT administrators are commonly used to lure the unsuspecting public. Phishing is typically carried out by e-mail or instant messaging,[1] and it often directs users to enter details at a fake website whose look and feel are almost identical to the legitimate one. Even when using server authentication, it may require tremendous skill to detect that the website is fake. Phishing is an example of social engineering techniques used to fool users,[2] and exploits the poor usability of current web security technologies.[3] Attempts to deal with the growing number of reported phishing incidents include legislation, user training, public awareness, and technical security measures.

A phishing technique was described in detail in 1987, and the first recorded use of the term "phishing" was made in 1996. The term is a variant of fishing,[4] probably influenced by phreaking,[5][6] and alludes to baits used to "catch" financial information and passwords.

History and current status of phishing

A phishing technique was described in detail in 1987, in a paper and presentation delivered to the International HP Users Group, Interex.[7] The first recorded mention of the term "phishing" is on the alt.online-service.America-online Usenet newsgroup on January 2, 1996,[8] although the term may have appeared earlier in the print edition of the hacker magazine 2600.[9]

Early phishing on AOL

Phishing on AOL was closely associated with the warez community that exchanged pirated software and the hacking scene that perpetrated credit card fraud and other online crimes. After AOL brought in measures in late 1995 to prevent using fake, algorithmically generated credit card numbers to open accounts, AOL crackers resorted to phishing for legitimate accounts[10] and exploiting AOL.

A phisher might pose as an AOL staff member and send an instant message to a potential victim, asking him to reveal his password.[11] In order to lure the victim into giving up sensitive information the message might include imperatives like "verify your account" or "confirm billing information". Once the victim had revealed the password, the attacker could access and use the victim's account for fraudulent purposes or spamming. Both phishing and warezing on AOL generally required custom-written programs, such as AOHell. Phishing became so prevalent on AOL that they added a line on all instant messages stating: "no one working at AOL will ask for your password or billing information".

After 1997, AOL's policy enforcement with respect to phishing and warez became stricter and forced pirated software off AOL servers. AOL simultaneously developed a system to promptly deactivate accounts involved in phishing, often before the victims could respond. The shutting down of the warez scene on AOL caused most phishers to leave the service, and many phishers—often young teens—grew out of the habit.[12]

Transition from AOL to financial institutions

The capture of AOL account information may have led phishers to misuse credit card information, and to the realization that attacks against online payment systems were feasible. The first known direct attempt against a payment system affected E-gold in June 2001, which was followed up by a "post-9/11 id check" shortly after the September 11 attacks on the World Trade Center.[13] Both were viewed at the time as failures, but can now be seen as early experiments towards more fruitful attacks against mainstream banks. By 2004, phishing was recognized as a fully industrialized part of the economy of crime: specializations emerged on a global scale that provided components for cash, which were assembled into finished attacks.[14][15]

Recent phishing attempts

A chart showing the increase in phishing reports from October 2004 to June 2005

Phishers are targeting the customers of banks and online payment services. E-mails, supposedly from the Internal Revenue Service, have been used to glean sensitive data from U.S. taxpayers.[16] While the first such examples were sent indiscriminately in the expectation that some would be received by customers of a given bank or service, recent research has shown that phishers may in principle be able to determine which banks potential victims use, and target bogus e-mails accordingly.[17] Targeted versions of phishing have been termed spear phishing.[18] Several recent phishing attacks have been directed specifically at senior executives and other high profile targets within businesses, and the term whaling has been coined for these kinds of attacks.[19]

Social networking sites are now a prime target of phishing, since the personal details in such sites can be used in identity theft;[20] in late 2006 a computer worm took over pages on MySpace and altered links to direct surfers to websites designed to steal login details.[21] Experiments show a success rate of over 70% for phishing attacks on social networks.[22]

The RapidShare file sharing site has been targeted by phishing to obtain a premium account, which removes speed caps on downloads, auto-removal of uploads, waits on downloads, and cooldown times between downloads.[23]

Attackers who broke into TD Ameritrade's database (containing all 6.3 million customers' social security numbers, account numbers and email addresses as well as their names, addresses, dates of birth, phone numbers and trading activity) also wanted the account usernames and passwords, so they launched a follow-up spear phishing attack.[24]

Almost half of phishing thefts in 2006 were committed by groups operating through the Russian Business Network based in St. Petersburg.[25]

Phishing techniques

Social engineering

People have a built-in reaction to things that seem important such as hardcore anal sex. Subjects lines worded to arouse anxiety usually prompt immediate action. An email with the subject: "to restore access to your bank account ..." will usually get instant attention and prompt most people to click to read what happened.

There has been extensive research on the subject.[26]

It is so pervasive that even corporate and government sites are actively informing their users on the issue.[27]

Most methods of phishing use some form of technical deception designed to make a link in an e-mail (and the spoofed website it leads to) appear to belong to the spoofed organization. Misspelled URLs or the use of subdomains are common tricks used by phishers. In the following example URL, http://www.yourbank.example.com/, it appears as though the URL will take you to the example section of the yourbank website; actually this URL points to the "yourbank" (i.e. phishing) section of the example website. Another common trick is to make the anchor text for a link appear to be valid, when the link actually goes to the phishers' site. The following example link, //wiki.riteme.site/wiki/Genuine, appears to take you to an article entitled "Genuine"; clicking on it will in fact take you to the article entitled "Deception". In the lower left hand corner of most browsers you can preview and verify where the link is going to take you. [28]

An old method of spoofing used links containing the '@' symbol, originally intended as a way to include a username and password (contrary to the standard).[29] For example, the link http://www.google.com@members.tripod.com/ might deceive a casual observer into believing that it will open a page on www.google.com, whereas it actually directs the browser to a page on members.tripod.com, using a username of www.google.com: the page opens normally, regardless of the username supplied. Such URLs were disabled in Internet Explorer,[30] while Mozilla Firefox[31] and Opera present a warning message and give the option of continuing to the site or cancelling.

A further problem with URLs has been found in the handling of Internationalized domain names (IDN) in web browsers, that might allow visually identical web addresses to lead to different, possibly malicious, websites. Despite the publicity surrounding the flaw, known as IDN spoofing[32] or homograph attack,[33] phishers have taken advantage of a similar risk, using open URL redirectors on the websites of trusted organizations to disguise malicious URLs with a trusted domain.[34][35][36]

Filter evasion

Phishers have used images instead of text to make it harder for anti-phishing filters to detect text commonly used in phishing e-mails.[37]

Website forgery

Once a victim visits the phishing website the deception is not over. Some phishing scams use JavaScript commands in order to alter the address bar.[38] This is done either by placing a picture of a legitimate URL over the address bar, or by closing the original address bar and opening a new one with the legitimate URL.[39]

An attacker can even use flaws in a trusted website's own scripts against the victim.[40] These types of attacks (known as cross-site scripting) are particularly problematic, because they direct the user to sign in at their bank or service's own web page, where everything from the web address to the security certificates appears correct. In reality, the link to the website is crafted to carry out the attack, although it is very difficult to spot without specialist knowledge. Just such a flaw was used in 2006 against PayPal.[41]

A Universal Man-in-the-middle Phishing Kit, discovered by RSA Security, provides a simple-to-use interface that allows a phisher to convincingly reproduce websites and capture log-in details entered at the fake site.[42]

To avoid anti-phishing techniques that scan websites for phishing-related text, phishers have begun to use Flash-based websites. These look much like the real website, but hide the text in a multimedia object.[43]

Phone phishing

Not all phishing attacks require a fake website. Messages that claimed to be from a bank told users to dial a phone number regarding problems with their bank accounts.[44] Once the phone number (owned by the phisher, and provided by a Voice over IP service) was dialed, prompts told users to enter their account numbers and PIN. Vishing (voice phishing) sometimes uses fake caller-ID data to give the appearance that calls come from a trusted organization.[45]

Other techniques

Another attack used successfully is to forward the client to a bank's legitimate website, then to place a popup window requesting credentials on top of the website in a way that it appears the bank is requesting this sensitive information.[46]

Damage caused by phishing

The damage caused by phishing ranges from denial of access to e-mail to substantial financial loss. It is estimated that between May 2004 and May 2005, approximately 1.2 million computer users in the United States suffered losses caused by phishing, totaling approximately US$929 million. United States businesses lose an estimated US$2 billion per year as their clients become victims.[47] In 2007 phishing attacks escalated. 3.6 million adults lost US $ 3.2 billion in the 12 months ending in August 2007.[48] Microsoft claims these estimates are grossly exaggerated and puts the annual phishing loss in the US at $60 million.[49] In the United Kingdom losses from web banking fraud—mostly from phishing—almost doubled to £23.2m in 2005, from £12.2m in 2004,[50] while 1 in 20 computer users claimed to have lost out to phishing in 2005.[51]

The stance adopted by the UK banking body APACS is that "customers must also take sensible precautions ... so that they are not vulnerable to the criminal."[52] Similarly, when the first spate of phishing attacks hit the Irish Republic's banking sector in September 2006, the Bank of Ireland initially refused to cover losses suffered by its customers (and it still insists that its policy is not to do so[53]), although losses to the tune of €11,300 were made good.[54]

Anti-phishing

There are several different techniques to combat phishing, including legislation and technology created specifically to protect against phishing.

Social responses

One strategy for combating phishing is to train people to recognize phishing attempts, and to deal with them. Education can be effective, especially where training provides direct feedback.[55] One newer phishing tactic, which uses phishing e-mails targeted at a specific company, known as spear phishing, has been harnessed to train individuals at various locations, including United States Military Academy at West Point, NY. In a June 2004 experiment with spear phishing, 80% of 500 West Point cadets who were sent a fake e-mail were tricked into revealing personal information.[56]

People can take steps to avoid phishing attempts by slightly modifying their browsing habits. When contacted about an account needing to be "verified" (or any other topic used by phishers), it is a sensible precaution to contact the company from which the e-mail apparently originates to check that the e-mail is legitimate. Alternatively, the address that the individual knows is the company's genuine website can be typed into the address bar of the browser, rather than trusting any hyperlinks in the suspected phishing message.[57]

Nearly all legitimate e-mail messages from companies to their customers contain an item of information that is not readily available to phishers. Some companies, for example PayPal, always address their customers by their username in e-mails, so if an e-mail addresses the recipient in a generic fashion ("Dear PayPal customer") it is likely to be an attempt at phishing.[58] E-mails from banks and credit card companies often include partial account numbers. However, recent research[59] has shown that the public do not typically distinguish between the first few digits and the last few digits of an account number—a significant problem since the first few digits are often the same for all clients of a financial institution. People can be trained to have their suspicion aroused if the message does not contain any specific personal information. Phishing attempts in early 2006, however, used personalized information, which makes it unsafe to assume that the presence of personal information alone guarantees that a message is legitimate.[60] Furthermore, another recent study concluded in part that the presence of personal information does not significantly affect the success rate of phishing attacks,[61] which suggests that most people do not pay attention to such details.

The Anti-Phishing Working Group, an industry and law enforcement association, has suggested that conventional phishing techniques could become obsolete in the future as people are increasingly aware of the social engineering techniques used by phishers.[62] They predict that pharming and other uses of malware will become more common tools for stealing information.

Everyone can help educate the public by encouraging safe practices, and by avoiding dangerous ones. Unfortunately, even well-known players are known to incite users to hazardous behaviour, e.g. by requesting their users to reveal their passwords for third party services, such as email.[63]


Technical responses

Anti-phishing measures have been implemented as features embedded in browsers, as extensions or toolbars for browsers, and as part of website login procedures. The following are some of the main approaches to the problem.

Helping to identify legitimate websites

Most websites targeted for phishing are secure websites[citation needed], meaning that SSL with strong cryptography is used for server authentication, where the website's URL is used as identifier. In theory it should be possible for the SSL authentication to be used to confirm the site to the user, and this was SSL v2's design requirement and the meta of secure browsing. But in practice, this is easy to trick.

The superficial flaw is that the browser's security user interface (UI) is insufficient to deal with today's strong threats. There are three parts to secure authentication using TLS and certificates: indicating that the connection is in authenticated mode, indicating which site the user is connected to, and indicating which authority says it is this site. All three are necessary for authentication, and need to be confirmed by/to the user.[citation needed]

Secure Connection. The standard display for secure browsing from the mid-1990s to mid-2000s was the padlock, which is easily missed by the user.[citation needed] Mozilla fielded a yellow URL bar in 2005 as a better indication of the secure connection.[citation needed] Unfortunately, this innovation was then reversed due to the EV certificates, which replaced certain high-value certificates with a green display, and other certificates with a white display.[citation needed]

Which Site. The user is expected to confirm that the domain name in the browser's URL bar was in fact where they intended to go. URLs can be too complex to be easily parsed. Users often do not know or recognise the URL of the legitimate sites they intend to connect to, so that the authentication becomes meaningless.[3] A condition for meaningful server authentication is to have a server identifier that is meaningful to the user; many ecommerce sites will change the domain names within their overall set of websites, adding to the opportunity for confusion. Simply displaying the domain name for the visited website[64] as some anti-phishing toolbars do is not sufficient.

An alternate approach is the petname extension for Firefox which lets users type in their own labels for websites, so they can later recognize when they have returned to the site. If the site is not recognised, then the software may either warn the user or block the site outright. This represents user-centric identity management of server identities.[65] Some suggest that a graphical image selected by the user is better than a petname.[66]

With the advent of EV certificates, browsers now typically display the organisation's name in green, which is much more visible and is hopefully more consistent with the user's expectations.[citation needed] Unfortunately, browser vendors have chosen to limit this prominent display only to EV certificates, leaving the user to fend for himself with all other certificates.

Who is the Authority. The browser needs to state who the authority is that makes the claim of who the user is connected to.[citation needed] At the simplest level, no authority is stated, and therefore the browser is the authority, as far as the user is concerned. The browser vendors take on this responsibility by controlling a root list of acceptable CAs. This is the current standard practice.

The problem with this is that not all certification authorities (CAs) employ equally good nor applicable checking, regardless of attempts by browser vendors to control the quality.[citation needed] Nor do all CAs subscribe to the same model and concept that certificates are only about authenticating ecommerce organisations. Certificate Manufacturing is the name given to low-value certificates that are delivered on a credit card and an email confirmation; both of these are easily perverted by fraudsters[citation needed]. Hence, a high-value site may be easily spoofed by a valid certificate provided by another CA. This could be because the CA is in another part of the world, and is unfamiliar with high-value ecommerce sites, or it could be that no care is taken at all. As the CA is only charged with protecting its own customers, and not the customers of other CAs, this flaw is inherent in the model.

The solution to this is that the browser should show, and the user should be familiar with, the name of the authority. This presents the CA as a brand, and allows the user to learn the handful of CAs that she is likely to come into contact within her country and her sector. The use of brand is also critical to providing the CA with an incentive to improve their checking, as the user will learn the brand and demand good checking for high-value sites.

This solution was first put into practice in early IE7 versions, when displaying EV certificates.[67] In that display, the issuing CA is displayed. This was an isolated case, however. There is resistance to CAs being branded on the chrome, resulting in a fallback to the simplest level above: the browser is the user's authority.[citation needed]

Fundamental flaws in the security model of secure browsing

Experiments to improve the security UI have resulted in benefits, but have also exposed fundamental flaws in the security model. The underlying causes for the failure of the SSL authentication to be employed properly in secure browsing are many and intertwined.

Security before threat. Because secure browsing was put into place before any threat was evident, the security display lost out in the "real estate wars" of the early browsers. The original design of Netscape's browser included a prominent display of the name of the site and the CA's name, but these were dropped in the first release.[citation needed] Users are now highly experienced in not checking security information at all.

Click-thru syndrome. However, warnings to poorly configured sites continued, and were not down-graded. If a certificate had an error in it (mismatched domain name, expiry), then the browser would commonly launch a popup to warn the user. As the reason was generally misconfiguration, the users learned to bypass the warnings, and now, users are accustomed to treat all warnings with the same disdain, resulting in Click-thru syndrome.[citation needed] For example, Firefox 3 has a 4-click process for adding an exception, but it has been shown to be ignored by an experienced user in a real case of MITM.[citation needed] Even today, as the vast majority of warnings will be for misconfigurations not real MITMs, it is hard to see how click-thru syndrome will ever be avoided.

Lack of interest. Another underlying factor is the lack of support for virtual hosting. The specific causes are a lack of support for Server Name Indication in TLS webservers, and the expense and inconvenience of acquiring certificates.[citation needed] The result is that the use of authentication is too rare to be anything but a special case. This has caused a general lack of knowledge and resources in authentication within TLS, which in turn has meant that the attempts by browser vendors to upgrade their security UIs have been slow and lacklustre.

Lateral communications. The security model for secure browser includes many participants: user, browser vendor, developers, CA, auditor, webserver vendor, ecommerce site, regulators (e.g., FDIC), and security standards committees.[citation needed] There is a lack of communication between different groups that are committed to the security model. E.g., although the understanding of authentication is strong at the protocol level of the IETF committees, this message does not reach the UI groups.[citation needed] Webserver vendors do not prioritise the Server Name Indication (TLS/SNI) fix, not seeing it as a security fix but instead a new feature.[citation needed] In practice, all participants look to the others as the source of the failures leading to phishing, hence the local fixes are not prioritised.

Matters improved slightly with the CAB Forum, as that group includes browser vendors, auditors and CAs.[citation needed] But the group did not start out in an open fashion, and the result suffered from commercial interests of the first players, as well as a lack of parity between the participants[citation needed]. Even today, CAB forum is not open, and does not include representation from small CAs, end-users, ecommerce owners, etc.[citation needed]

Standards gridlock. Vendors commit to standards, which results in an outsourcing effect when it comes to security. Although there have been many and good experiments in improving the security UI, these have not been adopted because they are not standard, or clash with the standards. Threat models can re-invent themselves in around a month; Security standards take around 10 years to adjust[citation needed].

Venerable CA model. Control mechanisms employed by the browser vendors over the CAs have not been substantially updated; the threat model has[citation needed]. The control and quality process over CAs is insufficiently tuned to the protection of users and the addressing of actual and current threats.[citation needed] Audit processes are in great need of updating[citation needed]. The recent EV Guidelines documented the current model in greater detail, and established a good benchmark, but did not push for any substantial changes to be made.[citation needed]

Browsers alerting users to fraudulent websites

Another popular approach to fighting phishing is to maintain a list of known phishing sites and to check websites against the list. Microsoft's IE7 browser, Mozilla Firefox 2.0, Safari 3.2, and Opera all contain this type of anti-phishing measure.[68][69][70][71] Firefox 2 used Google anti-phishing software. Opera 9.1 uses live blacklists from PhishTank and GeoTrust, as well as live whitelists from GeoTrust. Some implementations of this approach send the visited URLs to a central service to be checked, which has raised concerns about privacy.[72] According to a report by Mozilla in late 2006, Firefox 2 was found to be more effective than Internet Explorer 7 at detecting fraudulent sites in a study by an independent software testing company.[73]

An approach introduced in mid-2006 involves switching to a special DNS service that filters out known phishing domains: this will work with any browser,[74] and is similar in principle to using a hosts file to block web adverts.

To mitigate the problem of phishing sites impersonating a victim site by embedding its images (such as logos), several site owners have altered the images to send a message to the visitor that a site may be fraudulent. The image may be moved to a new filename and the original permanently replaced, or a server can detect that the image was not requested as part of normal browsing, and instead send a warning image.[75][76]

Augmenting password logins

The Bank of America's website[77][78] is one of several that ask users to select a personal image, and display this user-selected image with any forms that request a password. Users of the bank's online services are instructed to enter a password only when they see the image they selected. However, a recent study suggests few users refrain from entering their password when images are absent.[79][80] In addition, this feature (like other forms of two-factor authentication) is susceptible to other attacks, such as those suffered by Scandinavian bank Nordea in late 2005,[81] and Citibank in 2006.[82]

A similar system, in which an automatically-generated “Identity Cue” consisting of a colored word within a colored box is displayed to each website user, is in use at other financial institutions.[83]


Security skins[84][85] are a related technique that involves overlaying a user-selected image onto the login form as a visual cue that the form is legitimate. Unlike the website-based image schemes, however, the image itself is shared only between the user and the browser, and not between the user and the website. The scheme also relies on a mutual authentication protocol, which makes it less vulnerable to attacks that affect user-only authentication schemes.

Eliminating phishing mail

Specialized spam filters can reduce the number of phishing e-mails that reach their addressees' inboxes. These approaches rely on machine learning and natural language processing approaches to classify phishing e-mails.[86][87]

Monitoring and takedown

Several companies offer banks and other organizations likely to suffer from phishing scams round-the-clock services to monitor, analyze and assist in shutting down phishing websites.[88] Individuals can contribute by reporting phishing to both volunteer and industry groups,[89] such as PhishTank.[90] Individuals can also contribute by reporting phone phishing attempts to Phone Phishing,[91] Federal Trade Commission.[92]

On January 26, 2004, the U.S. Federal Trade Commission filed the first lawsuit against a suspected phisher. The defendant, a Californian teenager, allegedly created a webpage designed to look like the America Online website, and used it to steal credit card information.[93] Other countries have followed this lead by tracing and arresting phishers. A phishing kingpin, Valdir Paulo de Almeida, was arrested in Brazil for leading one of the largest phishing crime rings, which in two years stole between US$18 million and US$37 million.[94] UK authorities jailed two men in June 2005 for their role in a phishing scam,[95] in a case connected to the U.S. Secret Service Operation Firewall, which targeted notorious "carder" websites.[96] In 2006 eight people were arrested by Japanese police on suspicion of phishing fraud by creating bogus Yahoo Japan Web sites, netting themselves 100 million yen ($870,000 USD).[97] The arrests continued in 2006 with the FBI Operation Cardkeeper detaining a gang of sixteen in the U.S. and Europe.[98]

In the United States, Senator Patrick Leahy introduced the Anti-Phishing Act of 2005 in Congress on March 1, 2005. This bill, if it had been enacted into law, would have subjected criminals who created fake web sites and sent bogus e-mails in order to defraud consumers to fines of up to $250,000 and prison terms of up to five years.[99] The UK strengthened its legal arsenal against phishing with the Fraud Act 2006,[100] which introduces a general offence of fraud that can carry up to a ten year prison sentence, and prohibits the development or possession of phishing kits with intent to commit fraud.[101]

Companies have also joined the effort to crack down on phishing. On March 31, 2005, Microsoft filed 117 federal lawsuits in the U.S. District Court for the Western District of Washington. The lawsuits accuse "John Doe" defendants of obtaining passwords and confidential information. March 2005 also saw a partnership between Microsoft and the Australian government teaching law enforcement officials how to combat various cyber crimes, including phishing.[102] Microsoft announced a planned further 100 lawsuits outside the U.S. in March 2006,[103] followed by the commencement, as of November 2006, of 129 lawsuits mixing criminal and civil actions.[104] AOL reinforced its efforts against phishing[105] in early 2006 with three lawsuits[106] seeking a total of $18 million USD under the 2005 amendments to the Virginia Computer Crimes Act,[107][108] and Earthlink has joined in by helping to identify six men subsequently charged with phishing fraud in Connecticut.[109]

In January 2007, Jeffrey Brett Goodin of California became the first defendant convicted by a jury under the provisions of the CAN-SPAM Act of 2003. He was found guilty of sending thousands of e-mails to America Online users, while posing as AOL's billing department, which prompted customers to submit personal and credit card information. Facing a possible 101 years in prison for the CAN-SPAM violation and ten other counts including wire fraud, the unauthorized use of credit cards, and the misuse of AOL's trademark, he was sentenced to serve 70 months. Goodin had been in custody since failing to appear for an earlier court hearing and began serving his prison term immediately.[110][111][112][113]

See also

References

  1. ^ Tan, Koon. "Phishing and Spamming via IM (SPIM)". Internet Storm Center. Retrieved December 5, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  2. ^ Microsoft Corporation. "What is social engineering?". Retrieved August 22, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  3. ^ a b Jøsang, Audun; et al. "Security Usability Principles for Vulnerability Analysis and Risk Assessment" (PDF). Proceedings of the Annual Computer Security Applications Conference 2007 (ACSAC'07). {{cite web}}: Explicit use of et al. in: |author= (help); Unknown parameter |accessyear= ignored (|access-date= suggested) (help)CS1 maint: multiple names: authors list (link)
  4. ^ "Spam Slayer: Do You Speak Spam?". PCWorld.com. Retrieved August 16, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  5. ^ ""phishing, n." OED Online, March 2006, Oxford University Press". Oxford English Dictionary Online. Retrieved August 9, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  6. ^ "Phishing". Language Log, September 22, 2004. Retrieved August 9, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  7. ^ Felix, Jerry and Hauck, Chris (1987). "System Security: A Hacker's Perspective". 1987 Interex Proceedings. 1: 6. {{cite journal}}: Unknown parameter |month= ignored (help)CS1 maint: multiple names: authors list (link)
  8. ^ ""phish, v." OED Online, March 2006, Oxford University Press". Oxford English Dictionary Online. Retrieved August 9, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  9. ^ Ollmann, Gunter. "The Phishing Guide: Understanding and Preventing Phishing Attacks". Technical Info. Retrieved July 10, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  10. ^ "Phishing". Word Spy. Retrieved September 28, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  11. ^ Stutz, Michael (January 29, 1998). "AOL: A Cracker's Paradise?". Wired News.
  12. ^ "History of AOL Warez". {{cite web}}: Unknown parameter | accessmonthday= ignored (help); Unknown parameter |accessyear= ignored (|access-date= suggested) (help)
  13. ^ "GP4.3 - Growth and Fraud - Case #3 - Phishing". Financial Cryptography. December 30, 2005.
  14. ^ "In 2005, Organized Crime Will Back Phishers". IT Management. December 23, 2004.
  15. ^ "The economy of phishing: A survey of the operations of the phishing market". First Monday. 2005. {{cite web}}: Unknown parameter |month= ignored (help)
  16. ^ "Suspicious e-Mails and Identity Theft". Internal Revenue Service. Retrieved July 5, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  17. ^ "Phishing for Clues". Indiana University Bloomington. September 15, 2005.
  18. ^ "What is spear phishing?". Microsoft Security At Home. Retrieved July 10, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  19. ^ Goodin, Dan (April 17, 2008). "Fake subpoenas harpoon 2,100 corporate fat cats". The Register.
  20. ^ Kirk, Jeremy (June 2, 2006). "Phishing Scam Takes Aim at [[MySpace.com]]". IDG Network. {{cite news}}: URL–wikilink conflict (help)
  21. ^ "Malicious Website / Malicious Code: MySpace XSS QuickTime Worm". Websense Security Labs. Retrieved December 5, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  22. ^ Tom Jagatic and Nathan Johnson and Markus Jakobsson and Filippo Menczer. "Social Phishing" (PDF). To appear in the CACM (October 2007). Retrieved June 3, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  23. ^ "1-Click Hosting at RapidTec - Warning of Phishing!". Retrieved December 21, 2008. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  24. ^ "Torrent of spam likely to hit 6.3 million TD Ameritrade hack victims". Archived from the original on 2009-05-05.
  25. ^ Shadowy Russian Firm Seen as Conduit for Cybercrime, by Brian Krebs, Washington post, October 13, 2007
  26. ^ http://www.securityfocus.com/infocus/1860
  27. ^ http://www.michigan.gov/cybersecurity/0,1607,7-217-34396-111902--,00.html
  28. ^ http://www.hsbcusa.com/security/recognize_fraud.html
  29. ^ Berners-Lee, Tim. "Uniform Resource Locators (URL)". IETF Network Working Group. Retrieved January 28, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  30. ^ Microsoft. "A security update is available that modifies the default behavior of Internet Explorer for handling user information in HTTP and in HTTPS URLs". Microsoft Knowledgebase. Retrieved August 28, 2005. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  31. ^ Fisher, Darin. "Warn when HTTP URL auth information isn't necessary or when it's provided". Bugzilla. Retrieved August 28, 2005. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  32. ^ Johanson, Eric. "The State of Homograph Attacks Rev1.1". The Shmoo Group. Retrieved August 11, 2005. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  33. ^ Evgeniy Gabrilovich and Alex Gontmakher (2002). "The Homograph Attack" (PDF). Communications of the ACM. 45(2): 128. {{cite journal}}: Unknown parameter |month= ignored (help)
  34. ^ Leyden, John (August 15, 2006). "Barclays scripting SNAFU exploited by phishers". The Register.
  35. ^ Levine, Jason. "Goin' phishing with eBay". Q Daily News. Retrieved December 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  36. ^ Leyden, John (December 12, 2007). "Cybercrooks lurk in shadows of big-name websites". The Register.
  37. ^ Mutton, Paul. "Fraudsters seek to make phishing sites undetectable by content filters". Netcraft. Retrieved July 10, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  38. ^ Mutton, Paul. "Phishing Web Site Methods". FraudWatch International. Retrieved December 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  39. ^ "Phishing con hijacks browser bar". BBC News. April 8, 2004.
  40. ^ Krebs, Brian. "Flaws in Financial Sites Aid Scammers". Security Fix. Retrieved June 28, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  41. ^ Mutton, Paul. "PayPal Security Flaw allows Identity Theft". Netcraft. Retrieved June 19, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  42. ^ Hoffman, Patrick (January 10, 2007). "RSA Catches Financial Phishing Kit". eWeek.
  43. ^ Miller, Rich. "Phishing Attacks Continue to Grow in Sophistication". Netcraft. Retrieved December 19, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  44. ^ Gonsalves, Antone (April 25, 2006). "Phishers Snare Victims With VoIP". Techweb.
  45. ^ "Identity thieves take advantage of VoIP". Silicon.com. March 21, 2005.
  46. ^ "Internet Banking Targeted Phishing Attack" (PDF). Metropolitan Police Service. 2005-06-03. Retrieved 2009-03-22.
  47. ^ Kerstein, Paul (July 19, 2005). "How Can We Stop Phishing and Pharming Scams?". CSO.
  48. ^ McCall, Tom (December 17, 2007). "Gartner Survey Shows Phishing Attacks Escalated in 2007; More than $3 Billion Lost to These Attacks". Gartner.
  49. ^ "A Profitless Endeavor: Phishing as Tragedy of the Commons" (PDF). Microsoft. Retrieved November 15, 2008. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  50. ^ "UK phishing fraud losses double". Finextra. March 7, 2006.
  51. ^ Richardson, Tim (May 3, 2005). "Brits fall prey to phishing". The Register.
  52. ^ Miller, Rich. "Bank, Customers Spar Over Phishing Losses". Netcraft. Retrieved December 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  53. ^ "Latest News".
  54. ^ "Bank of Ireland agrees to phishing refunds – vnunet.com".
  55. ^ Ponnurangam Kumaraguru, Yong Woo Rhee, Alessandro Acquisti, Lorrie Cranor, Jason Hong and Elizabeth Nunge (2006). "Protecting People from Phishing: The Design and Evaluation of an Embedded Training Email System" (PDF). Technical Report CMU-CyLab-06-017, CyLab, Carnegie Mellon University. Retrieved November 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help); Unknown parameter |month= ignored (help)CS1 maint: multiple names: authors list (link)
  56. ^ Bank, David (August 17, 2005). "'Spear Phishing' Tests Educate People About Online Scams". The Wall Street Journal.
  57. ^ "Anti-Phishing Tips You Should Not Follow". HexView. Retrieved June 19, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  58. ^ "Protect Yourself from Fraudulent Emails". PayPal. Retrieved July 7, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  59. ^ Markus Jakobsson, Alex Tsow, Ankur Shah, Eli Blevis, Youn-kyung Lim. "What Instills Trust? A Qualitative Study of Phishing" (PDF). USEC '06.{{cite web}}: CS1 maint: multiple names: authors list (link)
  60. ^ Zeltser, Lenny (March 17, 2006). "Phishing Messages May Include Highly-Personalized Information". The SANS Institute.
  61. ^ Markus Jakobsson and Jacob Ratkiewicz. "Designing Ethical Phishing Experiments". WWW '06.
  62. ^ Kawamoto, Dawn (August 4, 2005). "Faced with a rise in so-called pharming and crimeware attacks, the Anti-Phishing Working Group will expand its charter to include these emerging threats". ZDNet India.
  63. ^ "Social networking site teaches insecure password practices". blog.anta.net. 2008-11-09. ISSN 1797-1993. Retrieved 2008-11-09.
  64. ^ Brandt, Andrew. "Privacy Watch: Protect Yourself With an Antiphishing Toolbar". PC World – Privacy Watch. Retrieved September 25, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  65. ^ Jøsangm Audun and Pope, Simon. "User Centric Identity Management" (PDF). Proceedings of AusCERT 2005. {{cite web}}: Unknown parameter |accessyear= ignored (|access-date= suggested) (help)CS1 maint: multiple names: authors list (link)
  66. ^ "Phishing - What it is and How it Will Eventually be Dealt With" by Ian Grigg 2005
  67. ^ "Brand matters (IE7, Skype, Vonage, Mozilla)" Ian Grigg
  68. ^ Franco, Rob. "Better Website Identification and Extended Validation Certificates in IE7 and Other Browsers". IEBlog. Retrieved May 20, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  69. ^ "Bon Echo Anti-Phishing". Mozilla. Retrieved June 2, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  70. ^ "Safari 3.2 finally gains phishing protection". Ars Technica. November 13, 2008. Retrieved November 15, 2008. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  71. ^ "Gone Phishing: Evaluating Anti-Phishing Tools for Windows". 3Sharp. September 27, 2006. Retrieved 2006-10-20.
  72. ^ "Two Things That Bother Me About Google's New Firefox Extension". Nitesh Dhanjani on O'Reilly ONLamp. Retrieved July 1, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  73. ^ "Firefox 2 Phishing Protection Effectiveness Testing". Retrieved January 23, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  74. ^ Higgins, Kelly Jackson. "DNS Gets Anti-Phishing Hook". Dark Reading. Retrieved October 8, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  75. ^ Krebs, Brian (August 31, 2006). "Using Images to Fight Phishing". Security Fix.
  76. ^ Seltzer, Larry (August 2, 2004). "Spotting Phish and Phighting Back". eWeek.
  77. ^ Bank of America. "How Bank of America SiteKey Works For Online Banking Security". Retrieved January 23, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  78. ^ Brubaker, Bill (July 14, 2005). "Bank of America Personalizes Cyber-Security". Washington Post.
  79. ^ Stone, Brad (February 5, 2007). "Study Finds Web Antifraud Measure Ineffective". New York Times. Retrieved February 5, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  80. ^ Stuart Schechter, Rachna Dhamija, Andy Ozment, Ian Fischer (2007). "The Emperor's New Security Indicators: An evaluation of website authentication and the effect of role playing on usability studies" (PDF). IEEE Symposium on Security and Privacy, May 2007. Retrieved February 5, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help); Unknown parameter |month= ignored (help)CS1 maint: multiple names: authors list (link)
  81. ^ "Phishers target Nordea's one-time password system". Finextra. October 12, 2005.
  82. ^ Krebs, Brian (July 10, 2006). "Citibank Phish Spoofs 2-Factor Authentication". Security Fix.
  83. ^ Graham Titterington. "More doom on phishing". Ovum Research, April 2006.
  84. ^ Schneier, Bruce. "Security Skins". Schneier on Security. Retrieved December 3, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  85. ^ Rachna Dhamija, J.D. Tygar (2005). "The Battle Against Phishing: Dynamic Security Skins" (PDF). Symposium On Usable Privacy and Security (SOUPS) 2005. Retrieved February 5, 2007. {{cite web}}: Unknown parameter |dateformat= ignored (help); Unknown parameter |month= ignored (help)
  86. ^ Madhusudhanan Chandrasekaran, Krishnan Narayanan, Shambhu Upadhyaya (2006). "Phishing E-mail Detection Based on Structural Properties" (PDF). NYS Cyber Security Symposium. {{cite web}}: Unknown parameter |month= ignored (help)CS1 maint: multiple names: authors list (link)
  87. ^ Ian Fette, Norman Sadeh, Anthony Tomasic (2006). "Learning to Detect Phishing Emails" (PDF). Carnegie Mellon University Technical Report CMU-ISRI-06-112. {{cite web}}: Unknown parameter |month= ignored (help)CS1 maint: multiple names: authors list (link)
  88. ^ "Anti-Phishing Working Group: Vendor Solutions". Anti-Phishing Working Group. Retrieved July 6, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  89. ^ McMillan, Robert (March 28, 2006). "New sites let users find and report phishing". LinuxWorld.
  90. ^ Schneier, Bruce (2006-10-05). "PhishTank". Schneier on Security. Retrieved 2007-12-07.
  91. ^ "Phone Phishing". Phone Phishing. Retrieved Feb 25, 2009. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  92. ^ "Federal Trade Commission". Federal Trade Commission. Retrieved Mar 6, 2009. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  93. ^ Legon, Jeordan (January 26, 2004). "'Phishing' scams reel in your identity". CNN.
  94. ^ Leyden, John (March 21, 2005). "Brazilian cops net 'phishing kingpin'". The Register.
  95. ^ Roberts, Paul (June 27, 2005). "UK Phishers Caught, Packed Away". eWEEK.
  96. ^ "Nineteen Individuals Indicted in Internet 'Carding' Conspiracy". Retrieved November 20, 2005. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  97. ^ "8 held over suspected phishing fraud". The Daily Yomiuri. May 31, 2006.
  98. ^ "Phishing gang arrested in USA and Eastern Europe after FBI investigation". Retrieved December 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  99. ^ "Phishers Would Face 5 Years Under New Bill". Information Week. March 2, 2005.
  100. ^ "Fraud Act 2006". Retrieved December 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  101. ^ "Prison terms for phishing fraudsters". The Register. November 14, 2006.
  102. ^ "Microsoft Partners with Australian Law Enforcement Agencies to Combat Cyber Crime". Retrieved August 24, 2005. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  103. ^ Espiner, Tom (March 20, 2006). "Microsoft launches legal assault on phishers". ZDNet.
  104. ^ Leyden, John (November 23, 2006). "MS reels in a few stray phish". The Register.
  105. ^ "A History of Leadership - 2006".
  106. ^ "AOL Takes Fight Against Identity Theft To Court, Files Lawsuits Against Three Major Phishing Gangs". Retrieved March 8, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  107. ^ "HB 2471 Computer Crimes Act; changes in provisions, penalty". Retrieved March 8, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  108. ^ Brulliard, Karin (April 10, 2005). "Va. Lawmakers Aim to Hook Cyberscammers". Washington Post.
  109. ^ "Earthlink evidence helps slam the door on phisher site spam ring". Retrieved December 14, 2006. {{cite web}}: Unknown parameter |dateformat= ignored (help)
  110. ^ Prince, Brian (January 18, 2007). "Man Found Guilty of Targeting AOL Customers in Phishing Scam". PCMag.com.
  111. ^ Leyden, John (January 17, 2007). "AOL phishing fraudster found guilty". The Register.
  112. ^ Leyden, John (June 13, 2007). "AOL phisher nets six years' imprisonment". The Register.
  113. ^ Gaudin, Sharon (June 12, 2007). "California Man Gets 6-Year Sentence For Phishing". InformationWeek.

Template:Link fa wi:Phishing

Retrieved from "https://wiki.riteme.site/w/index.php?title=Phishing&oldid=313850437"