OWASP Phishycat Project
OWASP Phishycat Project
OWASP Phishycat is a phishing detection framework. It detects a phishing page and show alert to the user. Currently, it only supports chrome browser. This project also includes a plugin called "Phishblocker" to communicate with browser and back-end server. It can be extended in other platforms as well.
Original domains should be registered in project database before it goes for testing. Once it guess the domain name then it compares the real time images of both web pages (phishing site and original website) . Attacker will try to make the web page design look similar to original website as much as possible. If both images are similar to each other, then next step is to compare DOM of both web pages. If it does not match then there is a high chance that it is a phishing site. Because, we can say two web pages are similar only when every elements of the pages are identical. In this case, we have similar looking two websites but their DOM is different.
We take the phishing domain and try to match it with all the registered domain names. If similar looking domain name exist in project database then we do the real time image compare of both web pages. If image compare is true, we proceed with real time DOM analysis of both web pages.
Here we are assuming that phishing domain name is similar to original domain, which may not be the case always. In future, We can implement services like text analysis in a webpage and find the focused keywords, it will help us to get the idea of original domain.
In our MVP, we are not considering threshold for image comparing and DOM analysis. A little change in image and DOM can give us wrong result. There might be elements in web page which are designed to load dynamically every time we refresh the page. To avoid this problem, threshold values will be added in next release of OWASP Phishycat.
OWASP Phishycat is free to use. It is licensed under the Apache License 2.0 https://apache.org/licenses/LICENSE-2.0.html
Current github: https://github.com/abhijitio/
News and Events
How can I participate in your project?
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.
If I am not a programmer can I participate in your project?
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.
As of June 2017, the highest priorities for the next 3 months are:
- Complete the text analysis to find the focused keyword and less dependency on domain name analysis.
- Database integration to properly maintain the registered domains.
- Get other people to review the Code Project Template and provide feedback.
- Develop plugin for Firefox.
- Mobile Application support.
Subsequent Releases will add
- Threshold value for image checking to avoid false positives.
- Threshold value for DOM analysis to avoid false positives.
Involvement in the development and promotion of Code Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
Please use the Code Project Template project mailing list for feedback about:
- What do like?
- What don't you like?
- What features would you like to see prioritized on the roadmap?