I wrote some Perl years back to take the fight to phishers. You would provide my script with the field names and POST URL of the HTML form within the phishing email, along with some generic types for each form field. There were types for firstnames, lastnames, email, addresses, usernames, passwords, social security numbers, and credit card numbers. The script would generate fake but real-looking values for each of these things--the credit card numbers would even pass a checksum test--and then post to the URL. It would do this as fast as the remote end would accept them with the aim of filling out their database (typically a text file on some compromised server) with bullshit data, making it hard to pick out the legit data from victims.<p>It worked wonderfully. I used it through proxies when I could and watched the phishers try to block me or even attack me back.
I work in security at a large Fortune 500 company. I know at first it sounds like phishing your employees will give you good insight, but you realize quickly that the data you get is not very useful. Here are the roadblocks I've hit with these kinds of simulation phishing services:<p>1. They rely on e-mail while phishing attacks come from multiple sources like Facebook and LinkedIn. Sadly, using those services to simulate phishing attacks violates their ToS.<p>2. Simulation phishing only provides pass or fail data meaning you cannot determine your weakest links in the organization. At best you get an "average" snapshot.<p>3. The data isn't very accurate or precise because there are too many confounding variables involved. Time of day, subject matter, type of phishing (attachment, social engineering, etc). Normally we ran our campaigns once a month but this wasn't enough to produce stable results.<p>4. Clicking doesn't mean they fell victim to the attack -- lot's of people click to investigate then report the links. Ideally, I'd like to specifically know WHY the employee clicked the link and HOW MUCH was actually at stake.<p>4. It pisses people off. There is enough animosity against us security folks that tricking your employees really hurts that relationship. People feel taken advantage of.<p>5. It doesn't actually improve security in any meaningful way. I found that it didn't actually improve people's ability to spot and report phishing attempts. They either became paranoid to the point where they were no longer productive in legitimate emails, or they had no improvements over time.<p>6. There's a growing body of knowledge that dismisses the effectiveness of this kind of phishing training (<a href="http://www.govinfosecurity.com/interviews/training-doesnt-mitigate-phishing-i-2148?" rel="nofollow">http://www.govinfosecurity.com/interviews/training-doesnt-mi...</a>) .<p>With that being said, our company has tried about a dozen of these kinds of services and the best one so far has been one called Apozy that is rather new. It's a different approach but the data and insight you get back is actually very useful.
There are many sites like this and I love what they are doing for raising awareness. As one of the first people to ever fight phishing (I worked at eBay and PayPal fighting phishing before there was a word for it), I'm keenly aware that awareness is the only way to really stop it.<p>That being said, I don't like these reports, because any time I get a phishing email I immediately load it up in a protected VM to see what it does, so it would count me as a victim. Since the page you go to isn't a real looking login page, you can't differentiate between those who fall for it and those who just clicked to see what it was.<p>You need to actually set up the fake page and see who puts in valid credentials to get a true report.
Love it! My recommendation would be to offer an option for allowing the target to be tricked through the whole process. (Even if credentials are discarded completely.) The idea here is nothing is left to the imagination. What you have is great, but it requires them to read and be observant, which is not the type of person who falls for phishing emails. Clicking the link is "No-No" #1, don't exclude "No-No" #2 from your process.
Neat, but doesn't seem very IT/corporate, which would surely be the intended audience.<p>My company uses these guys: <a href="http://www.knowbe4.com/" rel="nofollow">http://www.knowbe4.com/</a>
I often intentionally click links to phishing sites, and sometimes enter in fake usernames and passwords. (I even wrote several bots to auto enter thousands of random usernames and passwords.)<p>I don't like the click link = you lose idea.
Neat! I really like the easy pricing model.<p>Quick question - are you concerned about trademarks (Amazon and such) being included as the phishing templates? Reason I ask is that I'm working on a hosted project [1] similar to this and have considered including default templates. I've held off for this exact reason.<p>Edit - another question, your screenshot in the intro page shows an email (in the Gmail client) coming from "support@github.com". Github has spf records setup so I would be interested to know how you manage to spoof the actual email address itself without getting flagged as spam.<p>[1] <a href="http://github.com/jordan-wright/gophish" rel="nofollow">http://github.com/jordan-wright/gophish</a>
Consider changing pricing to $/click (pay per victim), so that companies are paying for the value you provide (detection security holes), and the CTO can "bet" the CEO that employees need better training/protection.<p>Much more upside for you.
What if this site occasionally sends out real phishing mails? If a lot of sites are using it, they would have interesting stats one could use to target the right audience.<p>Not saying they would, but they could get hacked of course...
Another service which does a similar thing that's been around some time, I used them but the spam filter ate all my fake mail, as it should :-) <a href="https://phish5.com/" rel="nofollow">https://phish5.com/</a>
How do you send your emails ?<p>If your customer is using google domains, microsoft 365 or what else, and the employees do not fall in your phishing attempt and report your mail as spam, you may be heading for some trouble with delivery afterward.
In case anyone one was curious, the "phishing" urls in the phishing emails lead to this page:<p><a href="https://cuttlephish.com/cuttlephished" rel="nofollow">https://cuttlephish.com/cuttlephished</a>
I was doing exactly the same project probably 8 years ago when I was still a high school student. I used to have a lot of websites, too but I never launched as I thought phishing is probably illegal and unethical.
This is a useful service. But I imagine there will be some nontrivial issues regarding spam filtering, server reputation, legal, etc.<p>How do you do email authentication? What are the headers that you put on your email?
Love the brand and name (reminds me of <a href="https://www.youtube.com/watch?v=GDwOi7HpHtQ" rel="nofollow">https://www.youtube.com/watch?v=GDwOi7HpHtQ</a>).