FredZhang7
commited on
Commit
•
93c3909
1
Parent(s):
0337205
Update README.md
Browse files
README.md
CHANGED
@@ -1,12 +1,58 @@
|
|
1 |
---
|
2 |
-
license:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3 |
---
|
4 |
**I have decided to release the auto-moderation models all at once sometime in July, 2023. The curated/original datasets for training these models will be avaliable first.**
|
5 |
|
6 |
-
|
|
|
|
|
7 |
If we could plot the lifespan of URLs, we could see that the oldest website has been online since Nov 7th, 2008, while the most recent phishing websites appeared as late as July 10th, 2023.
|
8 |
|
9 |
-
As we can see, there's no correlation between `is_malicious` and the columns `meta_percentage`, `mouseover_changes`, `not_indexed_by_google`,
|
10 |
The majority of features have very weak correlations with `is_malicious`, while a minority has a weak correlation. Is this problematic for training? Not really.
|
11 |
|
12 |
I split the classification task into two stages in anticipation of the limited availability of online phishing websites due to their short lifespan, as well as the possibility that research done on phishing is not up-to-date:
|
@@ -15,4 +61,4 @@ I split the classification task into two stages in anticipation of the limited a
|
|
15 |
|
16 |
This way, I can make the most out of the limited phishing websites avaliable.
|
17 |
|
18 |
-
![Phish Eater Data Analysis](https://i.imgur.com/
|
|
|
1 |
---
|
2 |
+
license: cc-by-4.0
|
3 |
+
task_categories:
|
4 |
+
- text-classification
|
5 |
+
- feature-extraction
|
6 |
+
- tabular-classification
|
7 |
+
language:
|
8 |
+
- sq
|
9 |
+
- th
|
10 |
+
- it
|
11 |
+
- tl
|
12 |
+
- de
|
13 |
+
- hr
|
14 |
+
- fi
|
15 |
+
- da
|
16 |
+
- lv
|
17 |
+
- pl
|
18 |
+
- ca
|
19 |
+
- ro
|
20 |
+
- ja
|
21 |
+
- lt
|
22 |
+
- af
|
23 |
+
- ru
|
24 |
+
- so
|
25 |
+
- en
|
26 |
+
- id
|
27 |
+
- cs
|
28 |
+
- sw
|
29 |
+
- es
|
30 |
+
- sl
|
31 |
+
- hu
|
32 |
+
- ko
|
33 |
+
- nl
|
34 |
+
- pt
|
35 |
+
- tr
|
36 |
+
- sv
|
37 |
+
- sk
|
38 |
+
- cy
|
39 |
+
- bg
|
40 |
+
- fr
|
41 |
+
- et
|
42 |
+
- no
|
43 |
+
- vi
|
44 |
+
- multilingual
|
45 |
+
size_categories:
|
46 |
+
- 1M<n<10M
|
47 |
---
|
48 |
**I have decided to release the auto-moderation models all at once sometime in July, 2023. The curated/original datasets for training these models will be avaliable first.**
|
49 |
|
50 |
+
This dataset is original, and my feature extraction method is covered in [feature_extraction.py](./feature_extraction.py)
|
51 |
+
|
52 |
+
In the *features* dataset, there're 770,098 websites online at the time of data collection. The plots below show the regression line and correlation coefficients of 20+ features extracted and whether the URL is malicious.
|
53 |
If we could plot the lifespan of URLs, we could see that the oldest website has been online since Nov 7th, 2008, while the most recent phishing websites appeared as late as July 10th, 2023.
|
54 |
|
55 |
+
As we can see, there's no correlation between `is_malicious` and the columns `meta_percentage`, `mouseover_changes`, `not_indexed_by_google`, and `right_click_disabled` as of July, 2023, contrary to some [analyses of researchers in 2013 on phishing detection](./Phishing_Websites_Features.docx).
|
56 |
The majority of features have very weak correlations with `is_malicious`, while a minority has a weak correlation. Is this problematic for training? Not really.
|
57 |
|
58 |
I split the classification task into two stages in anticipation of the limited availability of online phishing websites due to their short lifespan, as well as the possibility that research done on phishing is not up-to-date:
|
|
|
61 |
|
62 |
This way, I can make the most out of the limited phishing websites avaliable.
|
63 |
|
64 |
+
![Phish Eater Data Analysis](https://i.imgur.com/ADh6luR.png)
|