Phishing is the fraudulent attempt to obtain sensitive information such as usernames, passwords and credit card details by disguising oneself as a trustworthy entity in an electronic communication.[1][2] Typically carried out by email spoofing[3] or instant messaging,[4] it often directs users to enter personal information at a fake website which matches the look and feel of the legitimate site.[5]

Phishing is an example of social engineering techniques being used to deceive users. Users are often lured by communications purporting to be from trusted parties such as social web sites, auction sites, banks, online payment processors or IT administrators.[6]

Attempts to deal with phishing incidents include legislation, user training, public awareness, and technical security measures (the latter being due to phishing attacks frequently exploiting weaknesses in current web security).[7]

The word itself is a neologism created as a homophone of fishing.


Phishing types

Spear phishing

Phishing attempts directed at specific individuals or companies have been termed spear phishing.[8] In contrast to bulk phishing, spear phishing attackers often gather and use personal information about their target to increase their probability of success.[9][10][11][12]

Threat Group-4127 (Fancy Bear) used spear phishing tactics to target email accounts linked to Hillary Clinton's 2016 presidential campaign. They attacked more than 1,800 Google accounts and implemented the domain to threaten targeted users.[13][14]


The term whaling refers to spear phishing attacks directed specifically at senior executives and other high-profile targets.[15] In these cases, the content will be crafted to target an upper manager and the person's role in the company. The content of a whaling attack email may be an executive issue such as a subpoena or customer complaint.[16]

Clone phishing

Clone phishing is a type of phishing attack whereby a legitimate, and previously delivered, email containing an attachment or link has had its content and recipient address(es) taken and used to create an almost identical or cloned email. The attachment or link within the email is replaced with a malicious version and then sent from an email address spoofed to appear to come from the original sender. It may claim to be a resend of the original or an updated version to the original. Typically this requires either the sender or recipient to have been previously hacked for the malicious third party to obtain the legitimate email.[17][18]

Most methods of phishing use some form of technical deception designed to make a link in an email (and the spoofed website it leads to) appear to belong to the spoofed organization.[19] Misspelled URLs or the use of subdomains are common tricks used by phishers. In the following example URL,, 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 displayed text for a link (the text between the tags) suggest a reliable destination, when the link actually goes to the phishers' site. Many desktop email clients and web browsers will show a link's target URL in the status bar while hovering the mouse over it. This behavior, however, may in some circumstances be overridden by the phisher.[20] Equivalent mobile apps generally do not have this preview feature.[21]

Internationalized domain names (IDN) can be exploited via IDN spoofing[22] or homograph attacks,[23] to create web addresses visually identical to a legitimate site, that lead instead to malicious version. 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.[24][25][26] Even digital certificates do not solve this problem because it is quite possible for a phisher to purchase a valid certificate and subsequently change content to spoof a genuine website, or, to host the phish site without SSL at all.[27]

Filter evasion

Phishers have sometimes used images instead of text to make it harder for anti-phishing filters to detect the text commonly used in phishing emails.[28] In response, more sophisticated anti-phishing filters are able to recover hidden text in images using OCR (optical character recognition).[29]

Website forgery

Some phishing scams use JavaScript commands in order to alter the address bar of the website they lead to.[30] This is done either by placing a picture of a legitimate URL over the address bar, or by closing the original bar and opening up a new one with the legitimate URL.[31]

An attacker can also potentially use flaws in a trusted website's own scripts against the victim.[32] 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, making it very difficult to spot without specialist knowledge. Such a flaw was used in 2006 against PayPal.[33]

To avoid anti-phishing techniques that scan websites for phishing-related text, phishers sometimes use Flash-based websites (a technique known as phlashing). These look much like the real website, but hide the text in a multimedia object.[34]

Covert redirect

Covert redirect is a subtle method to perform phishing attacks that makes links appear legitimate, but actually redirect a victim to an attacker's website. The flaw is usually masqueraded under a log-in popup based on an affected site's domain.[35] It can affect OAuth 2.0 and OpenID based on well-known exploit parameters as well. This often makes use of open redirect and XSS vulnerabilities in the third-party application websites.[36] Users may also be redirected to phishing websites covertly through malicious browser extensions.[37]

Normal phishing attempts can be easy to spot because the malicious page's URL will usually be different from the real site link. For covert redirect, an attacker could use a real website instead by corrupting the site with a malicious login popup dialogue box. This makes covert redirect different from others.[38][39]

For example, suppose a victim clicks a malicious phishing link beginning with Facebook. A popup window from Facebook will ask whether the victim would like to authorize the app. If the victim chooses to authorize the app, a "token" will be sent to the attacker and the victim's personal sensitive information could be exposed. These information may include the email address, birth date, contacts, and work history.[36] In case the "token” has greater privilege, the attacker could obtain more sensitive information including the mailbox, online presence, and friends list. Worse still, the attacker may possibly control and operate the user's account.[40] Even if the victim does not choose to authorize the app, he or she will still get redirected to a website controlled by the attacker. This could potentially further compromise the victim.[41]

This vulnerability was discovered by Wang Jing, a Mathematics Ph.D. student at School of Physical and Mathematical Sciences in Nanyang Technological University in Singapore.[42] Covert redirect is a notable security flaw, though it is not a threat to the Internet worth significant attention.[43]

Social engineering

Users can be encouraged to click on various kinds of unexpected content for a variety of technical and social reasons. For example, a malicious attachment might masquerade as a benign linked Google Doc.[44]

Alternatively users might be outraged by a fake news story, click a link and become infected.[45]

Voice 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.[46] 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.[47]

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 page in a way that makes many users think the bank is requesting this sensitive information.[48]
  • Tabnabbing takes advantage of tabbed browsing, with multiple open tabs. This method silently redirects the user to the affected site. This technique operates in reverse to most phishing techniques in that it does not directly take the user to the fraudulent site, but instead loads the fake page in one of the browser's open tabs.



A phishing technique was described in detail in a paper and presentation delivered to the 1987 International HP Users Group, Interex.[49]


The term "phishing" is said to have been coined by the well known spammer and hacker in the mid-90s, Khan C Smith.[50] The first recorded mention of the term is found in the hacking tool AOHell (according to its creator), which included a function for attempting to steal the passwords or financial details of America Online users.[51][52]

Early AOL phishing

Phishing on AOL was closely associated with the warez community that exchanged unlicensed software and the black hat hacking scene that perpetrated credit card fraud and other online crimes. AOL enforcement would detect words used in AOL chat rooms to suspend the accounts of individuals involved in counterfeiting software and trading stolen accounts. The term was used because "<><" is the single most common tag of HTML that was found in all chat transcripts naturally, and as such could not be detected or filtered by AOL staff. The symbol <>< was replaced for any wording that referred to stolen credit cards, accounts, or illegal activity. Since the symbol looked like a fish, and due to the popularity of phreaking it was adapted as "Phishing". AOHell, released in early 1995, was a program designed to hack AOL users by allowing the attacker to pose as an AOL staff member, and send an instant message to a potential victim, asking him to reveal his password.[53] In order to lure the victim into giving up sensitive information, the message might include imperatives such as "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. 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". A user using both an AIM account and an AOL account from an ISP simultaneously could phish AOL members with relative impunity as internet AIM accounts could be used by non-AOL internet members and could not be actioned (i.e., reported to AOL TOS department for disciplinary action).[54]. In late 1995, AOL crackers resorted to phishing for legitimate accounts after AOL brought in measures in late 1995 to prevent using fake, algorithmically generated credit card numbers to open accounts.[55] Eventually, AOL's policy enforcement forced copyright infringement off AOL servers, and AOL 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.[56]


  • 2001
  • 2003
    • The first known phishing attack against a retail bank was reported by The Banker in September 2003.[58]
  • 2004
    • 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.[59]
    • Phishing is recognized as a fully organized part of the black market. Specializations emerged on a global scale that provided phishing software for payment (thereby outsourcing risk), which were assembled and implemented into phishing campaigns by organized gangs.[60][61]
  • 2005
    • In the United Kingdom losses from web banking fraud—mostly from phishing—almost doubled to GB£23.2m in 2005, from GB£12.2m in 2004,[62] while 1 in 20 computer users claimed to have lost out to phishing in 2005.[63]
  • 2006
    • Almost half of phishing thefts in 2006 were committed by groups operating through the Russian Business Network based in St. Petersburg.[64]
    • Banks dispute with customers over phishing losses. 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."[65] 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,[66] although losses to the tune of 113,000 were made good.[67]
    • Phishers are targeting the customers of banks and online payment services. Emails, supposedly from the Internal Revenue Service, have been used to glean sensitive data from U.S. taxpayers.[68] 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 emails accordingly.[69]
    • Social networking sites are a prime target of phishing, since the personal details in such sites can be used in identity theft;[70] in late 2006 a computer worm took over pages on MySpace and altered links to direct surfers to websites designed to steal login details.[71]
  • 2007
    • 3.6 million adults lost US$3.2 billion in the 12 months ending in August 2007.[72] Microsoft claims these estimates are grossly exaggerated and puts the annual phishing loss in the US at US$60 million.[73]
    • Attackers who broke into TD Ameritrade's database and took 6.3 million email addresses (though they were not able to obtain social security numbers, account numbers, 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.[74]
  • 2008
    • 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 cool down times between uploads.[75]
    • Cryptocurrencies such as Bitcoin facilitate the sale of malicious software, making transactions secure and anonymous.
  • 2009
    • In January 2009, a phishing attack resulted in unauthorized wire transfers of US$1.9 million through Experi-Metal's online banking accounts.
    • In the 3rd Quarter of 2009, the Anti-Phishing Working Group reported receiving 115,370 phishing email reports from consumers with US and China hosting more than 25% of the phishing pages each.[76]


Unique phishing reports by year [77]
Year Campaigns
  • 2011
    • In March 2011, Internal RSA staff were successfully phished,[78] leading to the master keys for all RSA SecureID security tokens being stolen, then subsequently used to break into US defense suppliers.[79]
    • Chinese phishing campaigns targeted Gmail accounts of highly ranked officials of the United States and South Korean governments and militaries, as well as Chinese political activists.[80][81]
  • 2012
    • According to Ghosh, there were "445,004 attacks in 2012 as compared to 258,461 in 2011 and 187,203 in 2010”.
  • 2013
    • In August 2013, advertising service Outbrain suffered a spearphishing attack and SEA placed redirects into the websites of The Washington Post, Time, and CNN.[82]
    • In October 2013, emails purporting to be from American Express were sent to an unknown number of recipients.[83]
    • In November 2013, 110 million customer and credit card records were stolen from Target customers, through a phished subcontractor account.[84] CEO and IT security staff subsequently fired.[85]
    • By December 2013, Cryptolocker ransomware had infected 250,000 computers. According to Dell SecureWorks, 0.4% or more of those infected likely agreed to the ransom demand.[86]
  • 2014
    • In January 2014, the Seculert Research Lab identified a new targeted attack that used Xtreme RAT. This attack used spear phishing emails to target Israeli organizations and deploy the piece of advanced malware. Fifteen machines were compromised including ones belonging to the Civil Administration of Judea and Samaria.[87][88][89][90][91][92][93]
    • In August 2014, the iCloud leaks of celebrity photos was found to be based on phishing e-mails sent to the victims that looked like they came from Apple or Google, warning the victims that their accounts might be compromised and asking for their account details.[94]
    • In November 2014, phishing attacks on ICANN gained administrative access to the Centralized Zone Data System; also gained was data about users in the system - and access to ICANN's public Governmental Advisory Committee wiki, blog, and whois information portal.[95]
  • 2015
  • 2016
  • In February, Austrian aerospace firm FACC AG was defrauded of 42 million euros ($47 million) through a BEC attack - and subsequently fired both the CFO and CEO.[104]
  • 2017
    • In 2017, 76% of organizations experienced phishing attacks. Nearly half of information security professionals surveyed said that the rate of attacks increased from 2016.
    • In the first half of 2017 businesses and residents of Qatar were hit with more than 93,570 phishing events in a three-month span.[118]
    • A phishing email to Google and Facebook users successfully induced employees into wiring money – to the extent of US$100 million – to overseas bank accounts under the control of a hacker. He has since been arrested by the US Department of Justice.[119]
    • In August 2017, customers of Amazon faced the Amazon Prime Day phishing attack, when hackers sent out seemingly legitimate deals to customers of Amazon. When Amazon's customers attempted to make purchases using the "deals", the transaction would not be completed, prompting the retailer's customers to input data that could be compromised and stolen.[120]
  • 2018
    • In 2018, the company, which developed the EOS.IO blockchain, was attacked by a phishing group who sent phishing emails to all customers, aimed at intercepting the user's cryptocurrency wallet key; and a later attack targeted airdrop tokens.[121]
Total number of unique phishing reports (campaigns) received, according to APWG[77]
Year Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Total
2005 12,845 13,468 12,883 14,411 14,987 15,050 14,135 13,776 13,562 15,820 16,882 15,244 173,063
2006 17,877 17,163 18,480 17,490 20,109 28,571 23,670 26,150 22,136 26,877 25,816 23,787 268,126
2007 29,930 23,610 24,853 23,656 23,415 28,888 23,917 25,624 38,514 31,650 28,074 25,683 327,814
2008 29,284 30,716 25,630 24,924 23,762 28,151 24,007 33,928 33,261 34,758 24,357 23,187 335,965
2009 34,588 31,298 30,125 35,287 37,165 35,918 34,683 40,621 40,066 33,254 30,490 28,897 412,392
2010 29,499 26,909 30,577 24,664 26,781 33,617 26,353 25,273 22,188 23,619 23,017 21,020 313,517
2011 23,535 25,018 26,402 20,908 22,195 22,273 24,129 23,327 18,388 19,606 25,685 32,979 284,445
2012 25,444 30,237 29,762 25,850 33,464 24,811 30,955 21,751 21,684 23,365 24,563 28,195 320,081
2013 28,850 25,385 19,892 20,086 18,297 38,100 61,453 61,792 56,767 55,241 53,047 52,489 491,399
2014 53,984 56,883 60,925 57,733 60,809 53,259 55,282 54,390 53,661 68,270 66,217 62,765 704,178
2015 49,608 55,795 115,808 142,099 149,616 125,757 142,155 146,439 106,421 194,499 105,233 80,548 1,413,978
2016 99,384 229,315 229,265 121,028 96,490 98,006 93,160 66,166 69,925 51,153 64,324 95,555 1,313,771
2017 96,148 100,932 121,860 87,453 93,285 92,657 99,024 99,172 98,012 61,322 86,547 85,744 1,122,156
2018 89,250 89,010 84,444 91,054 82,547 90,882 93,078 89,323 88,156 87,619 64,905 87,386 1,040,654

"APWG Phishing Attack Trends Reports". Retrieved May 5, 2019.


There are anti-phishing websites which publish exact messages that have been recently circulating the internet, such as FraudWatch International and Millersmiles. Such sites often provide specific details about the particular messages.[122][123]

As recently as 2007, the adoption of anti-phishing strategies by businesses needing to protect personal and financial information was low.[124] Now there are several different techniques to combat phishing, including legislation and technology created specifically to protect against phishing. These techniques include steps that can be taken by individuals, as well as by organizations. Phone, web site, and email phishing can now be reported to authorities, as described below.

User training

People can be trained to recognize phishing attempts, and to deal with them through a variety of approaches. Such education can be effective, especially where training emphasises conceptual knowledge[125] and provides direct feedback.[126][127]

Many organisations run regular simulated phishing campaigns targeting their staff to measure the effectiveness of their training.

People can take steps to avoid phishing attempts by slightly modifying their browsing habits.[128] 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 email apparently originates to check that the email 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.[129]

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 emails, so if an email addresses the recipient in a generic fashion ("Dear PayPal customer") it is likely to be an attempt at phishing.[130] Furthermore, PayPal offers various methods to determine spoof emails and advises users to forward suspicious emails to their domain to investigate and warn other customers. However it is unsafe to assume that the presence of personal information alone guarantees that a message is legitimate,[131] and some studies have shown that the presence of personal information does not significantly affect the success rate of phishing attacks;[132] which suggests that most people do not pay attention to such details.

Emails from banks and credit card companies often include partial account numbers. However, recent research[133] 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.

The Anti-Phishing Working Group produces regular report on trends in phishing attacks.[134]

Technical approaches

A wide range of technical approaches are available to prevent phishing attacks reaching users or to prevent them from successfully capturing sensitive information.

Filtering out phishing mail

Specialized spam filters can reduce the number of phishing emails that reach their addressees' inboxes. These filters use a number of techniques including machine learning[135] and natural language processing approaches to classify phishing emails,[136][137] and reject email with forged addresses.[3]

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. One such service is the Safe Browsing service.[138] Web browsers such as Google Chrome, Internet Explorer 7, Mozilla Firefox 2.0, Safari 3.2, and Opera all contain this type of anti-phishing measure.[6][139][140][141][142] Firefox 2 used Google anti-phishing software. Opera 9.1 uses live blacklists from Phishtank, cyscon 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.[143] 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.[144]

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,[145] 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.[146][147]

Augmenting password logins

The Bank of America website[148][149] is one of several that asks users to select a personal image (marketed as SiteKey) and displays 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, several studies suggest that few users refrain from entering their passwords when images are absent.[150][151] 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,[152] and Citibank in 2006.[153]

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.[154]

Security skins[155][156] 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.

Still another technique relies on a dynamic grid of images that is different for each login attempt. The user must identify the pictures that fit their pre-chosen categories (such as dogs, cars and flowers). Only after they have correctly identified the pictures that fit their categories are they allowed to enter their alphanumeric password to complete the login. Unlike the static images used on the Bank of America website, a dynamic image-based authentication method creates a one-time passcode for the login, requires active participation from the user, and is very difficult for a phishing website to correctly replicate because it would need to display a different grid of randomly generated images that includes the user's secret categories.[157]

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.[158] Individuals can contribute by reporting phishing to both volunteer and industry groups,[159] such as cyscon or PhishTank.[160] Individuals can also contribute by reporting phone phishing attempts to Phone Phishing, Federal Trade Commission.[161] Phishing web pages and emails can be reported to Google.[162][163] The Internet Crime Complaint Center noticeboard carries phishing and ransomware alerts.

Transaction verification and signing

Solutions have also emerged using the mobile phone[164] (smartphone) as a second channel for verification and authorization of banking transactions.

Multi-factor authentication

Organisations can implement two factor or multi-factor authentication (MFA), which requires a user to use at least 2 factors when logging in. (For example, a user must both present a smart card and a password). This mitigates some risk, in the event of a successful phishing attack, the stolen password on its own cannot be reused to further breach the protected system. However, there are several attack methods which can defeat many of the typical systems.[165] MFA schemes such as WebAuthn address this issue by design.

Email content redaction

Organizations that prioritize security over convenience can require users of its computers to use an email client that redacts URLs from email messages, thus making it impossible for the reader of the email to click on a link, or even copy a URL. While this may result in an inconvenience, it does almost completely eliminate email phishing attacks.

Limitations of technical responses

An article in Forbes in August 2014 argues that the reason phishing problems persist even after a decade of anti-phishing technologies being sold is that phishing is "a technological medium to exploit human weaknesses" and that technology cannot fully compensate for human weaknesses.[166]

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.[167] 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.[168] UK authorities jailed two men in June 2005 for their role in a phishing scam,[169] in a case connected to the U.S. Secret Service Operation Firewall, which targeted notorious "carder" websites.[170] 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 (US$870,000).[171] The arrests continued in 2006 with the FBI Operation Cardkeeper detaining a gang of sixteen in the U.S. and Europe.[172]

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 emails in order to defraud consumers to fines of up to US$250,000 and prison terms of up to five years.[173] The UK strengthened its legal arsenal against phishing with the Fraud Act 2006,[174] 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.[175]

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.[176] Microsoft announced a planned further 100 lawsuits outside the U.S. in March 2006,[177] followed by the commencement, as of November 2006, of 129 lawsuits mixing criminal and civil actions.[178] AOL reinforced its efforts against phishing[179] in early 2006 with three lawsuits[180] seeking a total of US$18 million under the 2005 amendments to the Virginia Computer Crimes Act,[181][182] and Earthlink has joined in by helping to identify six men subsequently charged with phishing fraud in Connecticut.[183]

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 emails 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.[184][185][186][187]

See also


  • Ghosh, Ayush (2013). "Seclayer: A plugin to prevent phishing attacks". IUP Journal of Information Technology. 9 (4): 52–64. SSRN 2467503.
  • Others/Notes
  1. Ramzan, Zulfikar (2010). "Phishing attacks and countermeasures". In Stamp, Mark; Stavroulakis, Peter (eds.). Handbook of Information and Communication Security. Springer. ISBN 978-3-642-04117-4.
  2. Van der Merwe, A J, Loock, M, Dabrowski, M. (2005), Characteristics and Responsibilities involved in a Phishing Attack, Winter International Symposium on Information and Communication Technologies, Cape Town, January 2005.
  3. "Landing another blow against email phishing (Google Online Security Blog)". Retrieved June 21, 2012.
  4. Dudley, Tonia. "Stop That Phish". Retrieved 6 November 2019.
  5. "What is Phishing?". 2016-08-14.
  6. "Safe Browsing (Google Online Security Blog)". Retrieved June 21, 2012.
  7. Jøsang, Audun; et al. (2007). "Security Usability Principles for Vulnerability Analysis and Risk Assessment" (PDF). Proceedings of the Annual Computer Security Applications Conference 2007 (ACSAC'07).
  8. "Spear phishing". Windows IT Pro Center. Retrieved March 4, 2019.
  9. Stephenson, Debbie (2013-05-30). "Spear Phishing: Who's Getting Caught?". Firmex. Retrieved July 27, 2014.
  10. "NSA/GCHQ Hacking Gets Personal: Belgian Cryptographer Targeted". Info Security magazine. 3 February 2018. Retrieved 10 September 2018.
  11. Leyden, John (4 April 2011). "RSA explains how attackers breached its systems". The Register. Retrieved 10 September 2018.
  12. Winterford, Brett (7 April 2011). "Epsilon breach used four-month-old attack". Retrieved 10 September 2018.
  13. "Threat Group-4127 Targets Google Accounts". Retrieved 2017-10-12.
  14. Nakashima, Ellen; Harris, Shane (July 13, 2018). "How the Russians hacked the DNC and passed its emails to WikiLeaks". The Washington Post. Retrieved February 22, 2019.
  15. "Fake subpoenas harpoon 2,100 corporate fat cats". The Register. Archived from the original on January 31, 2011. Retrieved April 17, 2008.
  16. "What Is 'Whaling'? Is Whaling Like 'Spear Phishing'?". About Tech. Archived from the original on October 18, 2011. Retrieved March 28, 2015.
  17. "Invoice scams affecting New Zealand businesses". NZCERT. Retrieved 1 July 2019.
  18. Parker, Tamsyn (18 August 2018). "House invoice scam leaves couple $53k out of pocket". NZ Herald. Retrieved 1 July 2019.
  19. "Get smart on Phishing! Learn to read links!". Archived from the original on December 11, 2016. Retrieved December 11, 2016.
  20. Cimpanu, Catalin (June 15, 2016). "Hidden JavaScript Redirect Makes Phishing Pages Harder to Detect". Softpedia News Center. Softpedia. Retrieved May 21, 2017. Hovering links to see their true location may be a useless security tip in the near future if phishers get smart about their mode of operation and follow the example of a crook who recently managed to bypass this browser built-in security feature.
  21. "Protection against Ransomware and Malware". 4 January 2019. Retrieved 13 September 2019.
  22. Johanson, Eric. "The State of Homograph Attacks Rev1.1". The Shmoo Group. Archived from the original on August 23, 2005. Retrieved August 11, 2005.
  23. Evgeniy Gabrilovich & Alex Gontmakher (February 2002). "The Homograph Attack" (PDF). Communications of the ACM. 45 (2): 128. doi:10.1145/503124.503156.
  24. Leyden, John (August 15, 2006). "Barclays scripting SNAFU exploited by phishers". The Register.
  25. Levine, Jason. "Goin' phishing with eBay". Q Daily News. Retrieved December 14, 2006.
  26. Leyden, John (December 12, 2007). "Cybercrooks lurk in shadows of big-name websites". The Register.
  27. "Black Hat DC 2009". May 15, 2011.
  28. Mutton, Paul. "Fraudsters seek to make phishing sites undetectable by content filters". Netcraft. Archived from the original on January 31, 2011.
  29. "The use of Optical Character Recognition OCR software in spam filtering". PowerShow.
  30. Mutton, Paul. "Phishing Web Site Methods". FraudWatch International. Archived from the original on January 31, 2011. Retrieved December 14, 2006.
  31. "Phishing con hijacks browser bar". BBC News. April 8, 2004.
  32. Krebs, Brian. "Flaws in Financial Sites Aid Scammers". Security Fix. Archived from the original on January 31, 2011. Retrieved June 28, 2006.
  33. Mutton, Paul. "PayPal Security Flaw allows Identity Theft". Netcraft. Archived from the original on January 31, 2011. Retrieved June 19, 2006.
  34. Miller, Rich. "Phishing Attacks Continue to Grow in Sophistication". Netcraft. Archived from the original on January 31, 2011. Retrieved December 19, 2007.
  35. "Serious security flaw in OAuth, OpenID discovered". CNET. May 2, 2014. Retrieved November 10, 2014.
  36. "Covert Redirect Vulnerability Related to OAuth 2.0 and OpenID". Tetraph. May 1, 2014. Retrieved November 10, 2014.
  37. Varshney, Gaurav; Misra, Manoj; Atrey, Pradeep (Jan 4, 2018). "Browshing a new way of phishing using a malicious browser extension". Browshing a new way to phishing using malicious browser extension. IEEE. pp. 1–5. doi:10.1109/IPACT.2017.8245147. ISBN 978-1-5090-5682-8.
  38. "Facebook, Google Users Threatened by New Security Flaw". Tom's Guid. May 2, 2014. Retrieved November 11, 2014.
  39. "Facebook, Google users threatened by new security flaw". FOX NEWS. May 5, 2014. Retrieved November 10, 2014.
  40. "Nasty Covert Redirect Vulnerability found in OAuth and OpenID". The Hacker News. May 3, 2014. Retrieved November 10, 2014.
  41. "Facebook, Google Users Threatened by New Security Flaw". Yahoo. May 2, 2014. Retrieved November 10, 2014.
  42. "'Covert Redirect' vulnerability impacts OAuth 2.0, OpenID". SC Magazine. May 2, 2014. Retrieved November 10, 2014.
  43. "Covert Redirect Flaw in OAuth is Not the Next Heartbleed". Symantec. May 3, 2014. Retrieved November 10, 2014.
  44. Graham, Meg (19 January 2017). "This Gmail phishing attack is tricking experts. Here's how to avoid it". Retrieved 28 January 2017.
  45. Tomlinson, Kerry (27 January 2017). "Fake news can poison your computer as well as your mind". Retrieved 28 January 2017.
  46. Gonsalves, Antone (April 25, 2006). "Phishers Snare Victims With VoIP". Techweb. Archived from the original on March 28, 2007.
  47. "Identity thieves take advantage of VoIP". March 21, 2005. Archived from the original on March 24, 2005.
  48. "Internet Banking Targeted Phishing Attack" (PDF). Metropolitan Police Service. June 3, 2005. Archived from the original (PDF) on February 18, 2010. Retrieved March 22, 2009.
  49. Felix, Jerry & Hauck, Chris (September 1987). "System Security: A Hacker's Perspective". 1987 Interex Proceedings. 8: 6.
  50. "EarthLink wins $25 million lawsuit against junk e-mailer".
  51. Langberg, Mike (September 8, 1995). "AOL Acts to Thwart Hackers". San Jose Mercury News.
  52. Rekouche, Koceilah (2011). "Early Phishing". arXiv:1106.4692 [cs.CR].
  53. Stutz, Michael (January 29, 1998). "AOL: A Cracker's Momma!". Wired News. Archived from the original on December 14, 2005.
  54. "Phishing | History of Phishing".
  55. "Phishing". Word Spy. Retrieved September 28, 2006.
  56. "History of AOL Warez". Archived from the original on January 31, 2011. Retrieved September 28, 2006.
  57. "GP4.3 – Growth and Fraud — Case #3 – Phishing". Financial Cryptography. December 30, 2005.
  58. Sangani, Kris (September 2003). "The Battle Against Identity Theft". The Banker. 70 (9): 53–54.
  59. Kerstein, Paul (July 19, 2005). "How Can We Stop Phishing and Pharming Scams?". CSO. Archived from the original on March 24, 2008.
  60. "In 2005, Organized Crime Will Back Phishers". IT Management. December 23, 2004. Archived from the original on January 31, 2011.
  61. Abad, Christopher (September 2005). "The economy of phishing: A survey of the operations of the phishing market". First Monday. Archived from the original on 2011-11-21. Retrieved 2010-10-08.
  62. "UK phishing fraud losses double". Finextra. March 7, 2006.
  63. Richardson, Tim (May 3, 2005). "Brits fall prey to phishing". The Register.
  64. Krebs, Brian (October 13, 2007). "Shadowy Russian Firm Seen as Conduit for Cybercrime". Washington Post.
  65. Miller, Rich. "Bank, Customers Spar Over Phishing Losses". Netcraft. Retrieved December 14, 2006.
  66. "Latest News". Archived from the original on October 7, 2008.
  67. "Bank of Ireland agrees to phishing refunds". Archived from the original on October 28, 2008.
  68. "Suspicious e-Mails and Identity Theft". Internal Revenue Service. Archived from the original on January 31, 2011. Retrieved July 5, 2006.
  69. "Phishing for Clues". Indiana University Bloomington. September 15, 2005. Archived from the original on July 31, 2009. Retrieved September 15, 2005.
  70. Kirk, Jeremy (June 2, 2006). "Phishing Scam Takes Aim at". IDG Network. Archived from the original on June 16, 2006.
  71. "Malicious Website / Malicious Code: MySpace XSS QuickTime Worm". Websense Security Labs. Archived from the original on December 5, 2006. Retrieved December 5, 2006.
  72. McCall, Tom (December 17, 2007). "Gartner Survey Shows Phishing Attacks Escalated in 2007; More than $3 Billion Lost to These Attacks". Gartner.
  73. "A Profitless Endeavor: Phishing as Tragedy of the Commons" (PDF). Microsoft. Retrieved November 15, 2008.
  74. "Torrent of spam likely to hit 6.3 million TD Ameritrade hack victims". Archived from the original on May 5, 2009.
  75. "1-Click Hosting at RapidTec — Warning of Phishing!". Archived from the original on April 30, 2008. Retrieved December 21, 2008.
  76. APWG. "Phishing Activity Trends Report" (PDF). Retrieved November 4, 2013.
  77. "APWG Phishing Attack Trends Reports". Retrieved October 20, 2018.
  78. "Anatomy of an RSA attack". RSA FraudAction Research Labs. Retrieved September 15, 2014.
  79. Drew, Christopher; Markoff, John (May 27, 2011). "Data Breach at Security Firm Linked to Attack on Lockheed". The New York Times. Retrieved September 15, 2014.
  80. Keizer, Greg (2011-08-13). "Suspected Chinese spear-phishing attacks continue to hit Gmail users". Computer World. Retrieved December 4, 2011.
  81. Ewing, Philip (2011-08-22). "Report: Chinese TV doc reveals cyber-mischief". Dod Buzz. Retrieved December 4, 2011.
  82. "Syrian hackers Use Outbrain to Target The Washington Post, Time, and CNN", Philip Bump, The Atlantic Wire, 15 August 2013. Retrieved 15 August 2013.
  83. Paul, Andrew. "Phishing Emails: The Unacceptable Failures of American Express". Email Answers. Archived from the original on October 9, 2013. Retrieved October 9, 2013.
  84. O'Connell, Liz. "Report: Email phishing scam led to Target breach". Retrieved September 15, 2014.
  85. Ausick, Paul. "Target CEO Sack". Retrieved September 15, 2014.
  86. Kelion, Leo (December 24, 2013). "Cryptolocker ransomware has 'infected about 250,000 PCs'". BBC. Retrieved December 24, 2013.
  87. "Israeli defence computer hacked via tainted email -cyber firm". Reuters. 2014-01-26.
  88. לוי, רויטרס ואליאור (27 January 2014). "האקרים השתלטו על מחשבים ביטחוניים". Ynet.
  89. "Hackers break into Israeli defence computers, says security company". The Guardian. Archived from the original on 2014-02-09.
  90. "Israel defence computers hit by hack attack". BBC News. 2014-01-27.
  91. "Israeli Defense Computer Hit in Cyber Attack: Data Expert | SecurityWeek.Com".
  92. "Israel to Ease Cyber-Security Export Curbs, Premier Says". Bloomberg.
  93. Halpern, Micah D. "Cyber Break-in @ IDF". Huffington Post.
  94. Prosecutors find that ‘Fappening’ celebrity nudes leak was not Apple’s fault March 15, 2016, Techcrunch
  95. "ICANN Targeted in Spear Phishing Attack | Enhanced Security Measures Implemented". Retrieved December 18, 2014.
  96. "Eccleston Indictment". November 1, 2013.
  97. "Former U.S. Nuclear Regulatory Commission Employee Pleads Guilty to Attempted Spear-Phishing Cyber-Attack on Department of Energy Computers". 2016-02-02.
  98. Nakashima, Ellen (28 September 2016). "Russian hackers harassed journalists who were investigating Malaysia Airlines plane crash". Washington Post. Retrieved 26 October 2016.
  99. ThreatConnect (2016-09-28). "ThreatConnect reviews activity targeting Bellingcat, a key contributor in the MH17 investigation". ThreatConnect. Retrieved 26 October 2016.
  100. Kube, Courtney (7 August 2015). "Russia hacks Pentagon computers: NBC, citing sources". Retrieved 7 August 2015.
  101. Starr, Barbara (7 August 2015). "Official: Russia suspected in Joint Chiefs email server intrusion". Retrieved 7 August 2015.
  102. Doctorow, Cory (August 28, 2015). "Spear phishers with suspected ties to Russian government spoof fake EFF domain, attack White House". Boing Boing.
  103. Quintin, Cooper (August 27, 2015). "New Spear Phishing Campaign Pretends to be EFF". EFF.
  104. "Austria's FACC, hit by cyber fraud, fires CEO". Reuters. 26 May 2016. Retrieved 20 December 2018.
  105. Sanger, David E.; Corasaniti, Nick (14 June 2016). "D.N.C. Says Russian Hackers Penetrated Its Files, Including Dossier on Donald Trump". New York Times. Retrieved 26 October 2016.
  106. Economist, Staff of (24 September 2016). "Bear on bear". Economist. Retrieved 25 October 2016.
  107. "KU employees fall victim to phishing scam, lose paychecks".
  108. "Hackers lurking, parliamentarians told". Deutsche Welle. Retrieved 21 September 2016.
  109. Pinkert, Georg Heil; Berlin, Nicolas Richter (2016-09-20). "Hackerangriff auf deutsche Parteien". Süddeutsche Zeitung. Retrieved 21 September 2016.
  110. Holland, Martin. "Angeblich versuchter Hackerangriff auf Bundestag und Parteien". Heise. Retrieved 21 September 2016.
  111. Hemicker, Lorenz; Alto, Palo. "Wir haben Fingerabdrücke". Frankfurter Allgemeine. Retrieved 21 September 2016.
  112. Hyacinth Mascarenhas (August 23, 2016). "Russian hackers 'Fancy Bear' likely breached Olympic drug-testing agency and DNC, experts say". International Business Times. Retrieved September 13, 2016.
  113. "What we know about Fancy Bears hack team". BBC News. 2016-09-15. Retrieved 17 September 2016.
  114. Gallagher, Sean (6 October 2016). "Researchers find fake data in Olympic anti-doping, Guccifer 2.0 Clinton dumps". Ars Technica. Retrieved 26 October 2016.
  115. "Russian Hackers Launch Targeted Cyberattacks Hours After Trump's Win". 2016-11-10.
  116. European Parliament Committee on Foreign Affairs (23 November 2016), "MEPs sound alarm on anti-EU propaganda from Russia and Islamist terrorist groups" (PDF), European Parliament, retrieved 26 November 2016
  117. Lewis Sanders IV (11 October 2016), "'Divide Europe': European lawmakers warn of Russian propaganda", Deutsche Welle, retrieved 24 November 2016
  118. "Qatar faced 93,570 phishing attacks in first quarter of 2017". Gulf-Times (in Arabic). 2017-05-12. Retrieved 2018-01-28.
  119. "Facebook and Google Were Victims of $100M Payment Scam". Fortune. Retrieved 2018-01-28.
  120. "Amazon Prime Day phishing scam spreading now!". The Kim Komando Show. Retrieved 2018-01-28.
  121. "Cryptocurrency Hackers Are Stealing from EOS's $4 Billion ICO Using This Sneaky Scam". Jen Wieczner. Retrieved 2018-05-31.
  122. "Millersmiles Home Page". Oxford Information Services. Archived from the original on July 21, 2007. Retrieved January 3, 2010.
  123. "FraudWatch International Home Page". FraudWatch International. Retrieved January 3, 2010.
  124. Baker, Emiley; Wade Baker; John Tedesco (2007). "Organizations Respond to Phishing: Exploring the Public Relations Tackle Box". Communication Research Reports. 24 (4): 327. doi:10.1080/08824090701624239.
  125. Arachchilage, Nalin; Love, Steve; Scott, Michael (June 1, 2012). "Designing a Mobile Game to Teach Conceptual Knowledge of Avoiding 'Phishing Attacks'". International Journal for E-Learning Security. 2 (1): 127–132. doi:10.20533/ijels.2046.4568.2012.0016. Retrieved April 1, 2016.
  126. Ponnurangam Kumaraguru; Yong Woo Rhee; Alessandro Acquisti; Lorrie Cranor; Jason Hong; Elizabeth Nunge (November 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. Archived from the original (PDF) on January 30, 2007. Retrieved November 14, 2006.
  127. Perrault, Evan K. (2017-03-23). "Using an Interactive Online Quiz to Recalibrate College Students' Attitudes and Behavioral Intentions About Phishing". Journal of Educational Computing Research. 55 (8): 1154–1167. doi:10.1177/0735633117699232.
  128. Hendric, William. "Steps to avoid phishing". Retrieved March 3, 2015.
  129. "Anti-Phishing Tips You Should Not Follow". HexView. Archived from the original on March 20, 2008. Retrieved June 19, 2006.
  130. "Protect Yourself from Fraudulent Emails". PayPal. Archived from the original on April 6, 2011. Retrieved July 7, 2006.
  131. Zeltser, Lenny (March 17, 2006). "Phishing Messages May Include Highly-Personalized Information". The SANS Institute.
  132. Markus Jakobsson & Jacob Ratkiewicz. "Designing Ethical Phishing Experiments". WWW '06. Archived from the original on January 31, 2011.
  133. Markus Jakobsson; Alex Tsow; Ankur Shah; Eli Blevis; Youn-kyung Lim. "What Instills Trust? A Qualitative Study of Phishing" (PDF). Archived from the original (PDF) on March 6, 2007.
  134. "APWG Phishing Attack Trends Reports". APWG. Retrieved 12 September 2018.
  135. Olivo, Cleber K.; Santin, Altair O.; Oliveira, Luiz S. (July 2011). "Obtaining the Threat Model for E-mail Phishing". Applied Soft Computing. 13 (12): 4841–4848. doi:10.1016/j.asoc.2011.06.016.
  136. Madhusudhanan Chandrasekaran; Krishnan Narayanan; Shambhu Upadhyaya (March 2006). "Phishing E-mail Detection Based on Structural Properties" (PDF). NYS Cyber Security Symposium. Archived from the original (PDF) on February 16, 2008.
  137. Ian Fette; Norman Sadeh; Anthony Tomasic (June 2006). "Learning to Detect Phishing Emails" (PDF). Carnegie Mellon University Technical Report CMU-ISRI-06-112.
  138. "Google Safe Browsing".
  139. Franco, Rob. "Better Website Identification and Extended Validation Certificates in IE7 and Other Browsers". IEBlog. Archived from the original on January 17, 2010. Retrieved May 20, 2006.
  140. "Bon Echo Anti-Phishing". Mozilla. Archived from the original on August 23, 2011. Retrieved June 2, 2006.
  141. "Safari 3.2 finally gains phishing protection". Ars Technica. November 13, 2008. Archived from the original on August 23, 2011. Retrieved November 15, 2008.
  142. "Gone Phishing: Evaluating Anti-Phishing Tools for Windows". 3Sharp. September 27, 2006. Archived from the original on January 14, 2008. Retrieved October 20, 2006.
  143. "Two Things That Bother Me About Google's New Firefox Extension". Nitesh Dhanjani on O'Reilly ONLamp. Retrieved July 1, 2007.
  144. "Firefox 2 Phishing Protection Effectiveness Testing". Archived from the original on January 31, 2011. Retrieved January 23, 2007.
  145. Higgins, Kelly Jackson. "DNS Gets Anti-Phishing Hook". Dark Reading. Archived from the original on August 18, 2011. Retrieved October 8, 2006.
  146. Krebs, Brian (August 31, 2006). "Using Images to Fight Phishing". Security Fix. Archived from the original on November 16, 2006.
  147. Seltzer, Larry (August 2, 2004). "Spotting Phish and Phighting Back". eWeek.
  148. Bank of America. "How Bank of America SiteKey Works For Online Banking Security". Archived from the original on August 23, 2011. Retrieved January 23, 2007.
  149. Brubaker, Bill (July 14, 2005). "Bank of America Personalizes Cyber-Security". Washington Post.
  150. Stone, Brad (February 5, 2007). "Study Finds Web Antifraud Measure Ineffective". New York Times. Retrieved February 5, 2007.
  151. Stuart Schechter; Rachna Dhamija; Andy Ozment; Ian Fischer (May 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. Archived from the original (PDF) on July 20, 2008. Retrieved February 5, 2007.
  152. "Phishers target Nordea's one-time password system". Finextra. October 12, 2005.
  153. Krebs, Brian (July 10, 2006). "Citibank Phish Spoofs 2-Factor Authentication". Security Fix. Archived from the original on November 10, 2006.
  154. Graham Titterington. "More doom on phishing". Ovum Research, April 2006.
  155. Schneier, Bruce. "Security Skins". Schneier on Security. Retrieved December 3, 2006.
  156. Rachna Dhamija; J.D. Tygar (July 2005). "The Battle Against Phishing: Dynamic Security Skins" (PDF). Symposium On Usable Privacy and Security (SOUPS) 2005. Archived from the original (PDF) on June 29, 2007. Retrieved February 5, 2007.
  157. "Dynamic, Mutual Authentication Technology for Anti-Phishing". Retrieved September 9, 2012.
  158. "Anti-Phishing Working Group: Vendor Solutions". Anti-Phishing Working Group. Archived from the original on January 31, 2011. Retrieved July 6, 2006.
  159. McMillan, Robert (March 28, 2006). "New sites let users find and report phishing". LinuxWorld. Archived from the original on January 19, 2009.
  160. Schneier, Bruce (October 5, 2006). "PhishTank". Schneier on Security. Archived from the original on January 31, 2011. Retrieved December 7, 2007.
  161. "Federal Trade Commission". Retrieved March 6, 2009.
  162. "Report a Phishing Page".
  163. How to report phishing scams to Google Archived 2013-04-14 at Consumer
  164. Using the smartphone to verify and sign online banking transactions, SafeSigner.
  165. Kan, Michael (7 March 2019). "Google: Phishing Attacks That Can Beat Two-Factor Are on the Rise". PC Mag. Retrieved 9 September 2019.
  166. Joseph Steinberg (August 25, 2014). "Why You Are at Risk of Phishing Attacks". Forbes. Retrieved November 14, 2014.
  167. Legon, Jeordan (January 26, 2004). "Phishing scams reel in your identity". CNN.
  168. Leyden, John (March 21, 2005). "Brazilian cops net 'phishing kingpin'". The Register.
  169. Roberts, Paul (June 27, 2005). "UK Phishers Caught, Packed Away". eWEEK.
  170. "Nineteen Individuals Indicted in Internet 'Carding' Conspiracy". Retrieved October 13, 2015.
  171. "8 held over suspected phishing fraud". The Daily Yomiuri. May 31, 2006.
  172. "Phishing gang arrested in USA and Eastern Europe after FBI investigation". Archived from the original on January 31, 2011. Retrieved December 14, 2006.
  173. "Phishers Would Face 5 Years Under New Bill". Information Week. March 2, 2005.
  174. "Fraud Act 2006". Archived from the original on August 23, 2011. Retrieved December 14, 2006.
  175. "Prison terms for phishing fraudsters". The Register. November 14, 2006.
  176. "Microsoft Partners with Australian Law Enforcement Agencies to Combat Cyber Crime". Archived from the original on November 3, 2005. Retrieved August 24, 2005.
  177. Espiner, Tom (March 20, 2006). "Microsoft launches legal assault on phishers". ZDNet.
  178. Leyden, John (November 23, 2006). "MS reels in a few stray phish". The Register.
  179. "A History of Leadership – 2006". Archived from the original on May 22, 2007.
  180. "AOL Takes Fight Against Identity Theft To Court, Files Lawsuits Against Three Major Phishing Gangs". Archived from the original on January 31, 2007. Retrieved March 8, 2006.
  181. "HB 2471 Computer Crimes Act; changes in provisions, penalty". Retrieved March 8, 2006.
  182. Brulliard, Karin (April 10, 2005). "Va. Lawmakers Aim to Hook Cyberscammers". Washington Post.
  183. "Earthlink evidence helps slam the door on phisher site spam ring". Archived from the original on July 5, 2007. Retrieved December 14, 2006.
  184. Prince, Brian (January 18, 2007). "Man Found Guilty of Targeting AOL Customers in Phishing Scam".
  185. Leyden, John (January 17, 2007). "AOL phishing fraudster found guilty". The Register.
  186. Leyden, John (June 13, 2007). "AOL phisher nets six years' imprisonment". The Register.
  187. Gaudin, Sharon (June 12, 2007). "California Man Gets 6-Year Sentence For Phishing". InformationWeek.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.