-
Notifications
You must be signed in to change notification settings - Fork 3
/
Incidents_Description.txt
executable file
·2885 lines (2881 loc) · 131 KB
/
Incidents_Description.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
#### Data in this file are collected by: Ahmed A. Alghamdi
#### This file explains the incidents exist in the SoM34 dataset
#### Details of some ICMP scans in the dataset are not included in this file
#### More details can found on the GitHub repository: https://github.com/aag1990/UAHL
List of suspected incidents as stated in the technical reports:
A1: AWstats incident:
@ Associated IP addresses: (213.135.2.227)
@ Number of logged events: (http_access: 2) (http_error: 16) (SnortSysLog: 9)
@ Notes: - The events in http_access include encoded commands which download a malicious file from a
website(http://www.shady.go.ro/aw.tgz).
- The related messages in http_error show that the attack was successful, also the response state is 200 (successful)
@ HTTP status codes: [200]
-------------------------------------
A2: AWstats incident:
@ Associated IP addresses: (82.55.78.243)
@ Number of logged events: (http_access: 1) (http_error: 16) (SnortSysLog: 6)
@ Notes: - The event in http_access includes an encoded command which downloads a malicious file from a
website(http://www.shady.go.ro/aw.tgz).
- The related messages in http_error show that the attack was successful, also the response state is 200 (successful)
- The request and results in A2 are the same as A1, also those two attacks were performed in
short time. (Thus, A1 and A2 might be the same attack but from different IP addresses)
@ HTTP status codes: [200]
-------------------------------------
A3: AWstats incident:
@ Associated IP addresses: (212.203.66.69)
@ Number of logged events: (http_access: 13) (http_error: 135) (SnortSysLog: 29)
@ Notes: - The events in http_access include encoded commands which perform different commands and
queries such as checking for files (by using the commands "uname -a" and "cat /etc/issue"),
also download malicious files from different websites (www.adjud.go.ro/t.tgz, www.maveric.com/t.tgz)
by using the commands "Lynx" and "wget".
- The events response in http_access state the code 200 (successful)
- There is a time difference between events in http_access and the related events in http_error, that might
be because the files took some time to download on the victim device, or because the connection fails or timeout.
- The lynx command did not work on the victim device, error messages show that in http_error.
- The connection via "wget" to the website "www.adjud.go.ro" timed out, thus the malicious file was not
downloaded on the victim device. Report 1, states that for this reason, the attack was not successful.
@ HTTP status codes: [200]
-------------------------------------
A4: AWstats incident:
@ Associated IP addresses: (82.49.16.150)
@ Number of logged events: (http_access: 2) (http_error: 14)
@ Notes: - The events in http_access include encoded commands which perform two different commands such as shutting-down
the "netd" service by using the command "Killall -9 inetd", also download malicious files from different,
also downloading a malicious file from a website(www.shady.go.ro/a.tgz) by using the command "wget".
- The events response in http_access state the code 200 (successful)
- There is a strong similarity between this attack and the A1 attack. The attacker started the "inetd" service in
the A1 attack, while he shut it sown in this attack. Also, the same website (www.shady.go.ro) was used to download
the file on the victim device, which indicates the same attacker might be responsible for both attacks.
- The http_error file shows that the file was downloaded on the victim device, although there was a problem
binding a program to a port. Report1 states that this indicates that the desired port was used by other
application or that the command "killall" did not work on the victim device.
@ HTTP status codes: [200]
-------------------------------------
A5: AWstats scans:
@ Associated IP addresses: (210.51.12.238)
@ Number of logged events: (http_access: 92) (http_error: 98)
@ Notes: - The related events in http_access are "| id |" commands that performs scans on the AWstats script.
- The events response states in http_access are 404(Not Found), 403(Forbidden), 200(successful).
- Report1 states that no intrusion of the system took place by those commands (scanning commands only).
- The entry involves access attempt to "/var/www/html" which is forbidden by the server.
@ HTTP status codes: [404, 403, 200]
-------------------------------------
A6: AWstats scans:
@ Associated IP addresses: (64.62.145.98)
@ Number of logged events: (http_access: 414) (http_error: 382)
@ Notes: - The related events in http_access are "| id |" commands that performs scans on the AWstats script.
- The events response states in http_access are 404(Not Found), 403(Forbidden), 200(successful), 500(Internal Server Error)
- Report1 states that no intrusion of the system took place by those commands (scanning commands only).
- The entry involves access attempt to "/var/www/html" which is forbidden by the server.
@ HTTP status codes: [404, 403, 200, 500]
-------------------------------------
THIS INCIDENT IS COMBINED WITH A51
-------------------------------------
A8: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (211.233.14.63)
@ Number of logged events: (syslog_secure: 33)
-------------------------------------
A9: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (210.99.250.240)
@ Number of logged events: (syslog_secure: 30)
-------------------------------------
A10: SSH brute force scan:
@ Associated IP addresses: (70.84.72.68)
@ Number of logged events: (syslog_secure: 10) (syslog_messages: 10)
-------------------------------------
A11: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (211.141.89.73)
@ Number of logged events: (syslog_secure: 140) (syslog_messages: 2)
-------------------------------------
A12: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (208.29.180.3)
@ Number of logged events: (syslog_secure: 33) (syslog_messages: 10)
-------------------------------------
A13: SSH brute force scan:
@ Associated IP addresses: (222.237.79.237)
@ Number of logged events: (syslog_secure: 80) (syslog_messages: 80)
-------------------------------------
A14: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (66.154.114.114)
@ Number of logged events: (syslog_secure: 44) (syslog_messages: 23)
-------------------------------------
A15: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (67.28.17.226)
@ Number of logged events: (syslog_secure: 29)
-------------------------------------
A16: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (210.3.2.8)
@ Number of logged events: (syslog_secure: 33) (syslog_messages: 23)
-------------------------------------
A17: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (148.228.20.76)
@ Number of logged events: (syslog_secure: 54) (syslog_messages: 1)
-------------------------------------
A18: Scanning for the existence of a sshd runnin:
@ Associated IP addresses: (200.120.71.160)
@ Number of logged events: (syslog_secure: 19)
-------------------------------------
A19: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (220.130.226.25)
@ Number of logged events: (syslog_secure: 33)
-------------------------------------
A20: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (83.246.112.22)
@ Number of logged events: (syslog_secure: 40) (syslog_messages: 19)
-------------------------------------
A21: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (62.193.229.186)
@ Number of logged events: (syslog_secure: 80) (syslog_messages: 80)
-------------------------------------
A22: SSH brute force scan:
@ Associated IP addresses: (69.44.156.105)
@ Number of logged events: (syslog_secure: 16) (syslog_messages: 16)
-------------------------------------
A23: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (81.56.82.49)
@ Number of logged events: (syslog_secure: 32) (syslog_messages: 32)
-------------------------------------
A24: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (210.70.129.207)
@ Number of logged events: (syslog_secure: 33) (syslog_messages: 10)
-------------------------------------
A25: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (202.110.184.100)
@ Number of logged events: (syslog_secure: 102) (syslog_messages: 93) (SnortSysLog: 258)
-------------------------------------
A26: SSH brute force scan:
@ Associated IP addresses: (211.147.240.247)
@ Number of logged events: (syslog_secure: 9) (syslog_messages: 9)
-------------------------------------
A27: SSH brute force scan:
@ Associated IP addresses: (202.69.66.162)
@ Number of logged events: (syslog_secure: 2) (syslog_messages: 2)
-------------------------------------
A28: SSH brute force scan:
@ Associated IP addresses: (61.120.122.98)
@ Number of logged events: (syslog_secure: 6) (syslog_messages: 6)
-------------------------------------
A29: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (200.27.232.100)
@ Number of logged events: (syslog_secure: 8) (syslog_messages: 4) (SnortSysLog: 9)
-------------------------------------
A30: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (217.74.112.2)
@ Number of logged events: (syslog_secure: 28) (SnortSysLog: 15)
-------------------------------------
A31: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (219.159.82.198)
@ Number of logged events: (syslog_secure: 36) (SnortSysLog: 36)
-------------------------------------
A32: SSH brute force scan:
@ Associated IP addresses: (62.193.226.4)
@ Number of logged events: (syslog_secure: 80) (syslog_messages: 80) (SnortSysLog: 45)
-------------------------------------
A33: SSH brute force scan:
@ Associated IP addresses: (211.158.7.250)
@ Number of logged events: (syslog_secure: 16) (syslog_messages: 16)
-------------------------------------
A34: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (212.174.124.64)
@ Number of logged events: (syslog_secure: 78)
-------------------------------------
A35: SSH brute force scan:
@ Associated IP addresses: (198.107.38.61)
@ Number of logged events: (syslog_secure: 8) (syslog_messages: 8)
-------------------------------------
A36: SSH brute force scan:
@ Associated IP addresses: (210.125.27.175)
@ Number of logged events: (syslog_secure: 17) (syslog_messages: 17)
-------------------------------------
A37: Scanning for the existence of a running sshd & then multiple accepted password messages:
@ Associated IP addresses: (83.103.78.202)
@ Number of logged events: (syslog_secure: 29)
-------------------------------------
A38: SSH brute force scan:
@ Associated IP addresses: (80.86.103.61)
@ Number of logged events: (syslog_secure: 16) (syslog_messages: 16)
-------------------------------------
A39: SSH brute force scan:
@ Associated IP addresses: (66.79.166.130)
@ Number of logged events: (syslog_secure: 80) (syslog_messages: 80)
-------------------------------------
A40: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (69.13.1.1)
@ Number of logged events: (syslog_secure: 39) (SnortSysLog: 35)
-------------------------------------
A41: Scanning for the existence of a running sshd:
@ Associated IP addresses: (83.17.162.86)
@ Number of logged events: (syslog_secure: 23) (SnortSysLog: 5)
-------------------------------------
A42: SSH brute force scan:
@ Associated IP addresses: (67.103.15.70)
@ Number of logged events: (syslog_secure: 18) (syslog_messages: 10) (SnortSysLog: 19)
-------------------------------------
A43: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (128.59.112.2)
@ Number of logged events: (syslog_secure: 39) (syslog_messages: 23) (SnortSysLog: 91)
-------------------------------------
A44: SSH brute force scan:
@ Associated IP addresses: (207.188.80.171)
@ Number of logged events: (syslog_secure: 10) (syslog_messages: 10) (SnortSysLog: 51)
-------------------------------------
A45: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (82.76.137.124)
@ Number of logged events: (syslog_secure: 2) (syslog_messages: 1) (SnortSysLog: 2)
-------------------------------------
A46: SSH brute force scan:
@ Associated IP addresses: (61.222.170.236)
@ Number of logged events: (syslog_secure: 16) (syslog_messages: 16) (SnortSysLog: 5)
-------------------------------------
A47: SSH brute force scan:
@ Associated IP addresses: (202.68.93.5)
@ Number of logged events: (syslog_secure: 5) (syslog_messages: 5) (SnortSysLog: 10)
-------------------------------------
A48: Scanning for the existence of a running sshd & SSH brute force scan:
@ Associated IP addresses: (202.105.113.167)
@ Number of logged events: (syslog_secure: 11) (SnortSysLog: 26)
-------------------------------------
A49: Scanning for the existence of a running sshd:
@ Associated IP addresses: (219.234.219.7)
@ Number of logged events: (syslog_secure: 22) (SnortSysLog: 44)
-------------------------------------
A50: RPC attack:
@ Number of logged events: (syslog_messages: 12)
@ Notes: - (Two events related to activating the service by the kernal were not considered)).
- There were a couple of attacks directed a gainst a glibc bug in the rpc XDR decoder library.
-------------------------------------
A51: System restart (including SSH Server Restart):
@ Number of logged events: (syslog_secure: 1) (syslog_messages: 4)
@ Notes: Some lines show that the system has been rebooted (might be by a malicious command, or might be a benign one!),
however, 23 IP adresses (11.11.79.*) were configured on the server after the reboot.
-------------------------------------
A52: Crashes of xinetd:
@ Number of logged events: (syslog_messages: 14)
@ Notes: The log shows that xinetd is going up and down for no apparent reason (this can be an indication of an attack)
-------------------------------------
A53: System Load:
@ Number of logged events: (syslog_maillog: 137)
@ Notes: There are many records of "did not issue MAIL/EXPN/VRFY/ETRN" connections to MTA.
Usually, those entries are from address verification programs, but they can also be a sign of a virus activity.
-------------------------------------
A54: Relay attempts:
@ Number of logged events: (syslog_maillog: 14)
@ Notes: Several relay attempts found in the log file. None of them were successful (Based on report1)
-------------------------------------
A55: Rebuilding aliases:
@ Number of logged events: (syslog_maillog: 5)
@ Notes: Aliases were rebuilt and the Sendmail daemon restarted,
this correlates with the reboot. (No indicator to malicious activity)
-------------------------------------
A56: pop3 service init:
@ Number of logged events: (syslog_maillog: 4)
@ Notes: pop3 service initiated from different IP addresses (146.83.8.224 & 151.25.187.213)
-------------------------------------
A57: Multiple scans ("Double decoding scan (nimda type)" & "/NULL.printer scan" & "/scripts/nsiislog.dll scan"):
@ Associated IP addresses: (81.6.250.202)
@ Number of logged events: (http_access: 8) (http_error: 8) (SnortSysLog: 3)
@ HTTP status codes: [404]
@ Notes: the entries are recorded on different timestamps: (1107265953, 1107419135, 1107530763, 1108640676, 1109157759, 1109299584, 1109390774, 1110257843)
-------------------------------------
A58: Multiple scans ("Double decoding scan (nimda type)" & "/NULL.printer scan" & "/scripts/nsiislog.dll scan"):
@ Associated IP addresses: (65.96.54.37)
@ Number of logged events: (http_access: 8) (http_error: 8) (SnortSysLog: 13)
@ HTTP status codes: [404]
@ Notes: the entries are recorded on different timestamps (1107585887, 1107672403, 1107780484, 1108045632, 1109281729, 1109694260, 1110228878, 1110930333)
-------------------------------------
A59: Multiple scans ("Double decoding scan (nimda type)" & "/scripts/nsiislog.dll scan"):
@ Associated IP addresses: (80.100.183.164)
@ Number of logged events: (http_access: 2) (http_error: 2)
@ HTTP status codes: [404]
@ Notes: the entries are recorded on different timestamps (1110146692, 1110160683)
-------------------------------------
A60: Multiple scans ("Double decoding scan (nimda type)" & "/scripts/nsiislog.dll scan", "Web application attack"):
@ Associated IP addresses: (68.209.255.26)
@ Number of logged events: (http_access: 2) (http_error: 2) (SnortSysLog: 6)
@ HTTP status codes: [404]
@ Notes: the entries are recorded on different timestamps (1109356384, 1110640736)
-------------------------------------
A61: Multiple scans ("/NULL.printer scan" & "/scripts/nsiislog.dll scan"):
@ Associated IP addresses: (67.104.84.66)
@ Number of logged events: (http_access: 2) (http_error: 2) (SnortSysLog: 2)
@ HTTP status codes: [404]
@ Notes: the entries are recorded on different timestamps (1108493680, 1109341113)
-------------------------------------
A62: Multiple scans ("/NULL.printer scan" & "/scripts/nsiislog.dll scan"):
@ Associated IP addresses: (66.30.71.74)
@ Number of logged events: (http_access: 4) (http_error: 4) (SnortSysLog: 16)
@ HTTP status codes: [404]
@ Notes: the entries are recorded on different timestamps (1109488020, 1109939784, 1110718227, 1110998036)
-------------------------------------
A63: ("CONNECT Scan" & "Proxy request"):
@ Associated IP addresses: (211.144.162.173)
@ Number of logged events: (http_access: 5) (http_error: 3)
@ HTTP status codes: [405, 501, 404]
@ Notes: the entries are recorded on different timestamps (1107601106, 1107601711, 1107608639, 1107616179, 1107621865)
-------------------------------------
A64: ("CONNECT Scan" & "Proxy request"):
@ Associated IP addresses: (219.153.10.142)
@ Number of logged events: (http_access: 4) (http_error: 1)
@ HTTP status codes: [405, 404]
@ Notes: the entries are recorded on different timestamps (1107601978, 1107602441, 1107606782, 1107619306)
-------------------------------------
A65: ("CONNECT Scan" & "Proxy request"):
@ Associated IP addresses: (61.178.79.227)
@ Number of logged events: (http_access: 34) (http_error: 17)
@ HTTP status codes: [405, 403]
-------------------------------------
A66: Multiple malicious behaviour ("AWStats scan" & "access attempt to /var/www/html"):
@ Associated IP addresses: (66.99.250.98)
@ Number of logged events: (http_access: 42) (http_error: 42)
@ HTTP status codes: [404, 403]
-------------------------------------
A67: Multiple malicious behaviour ("AWStats scan" & "Access attempt to /var/www/html"):
@ Associated IP addresses: (81.181.146.13)
@ Number of logged events: (http_access: 55) (http_error: 66) (SnortSysLog: 64)
@ HTTP status codes: [404, 500, 403]
-------------------------------------
A68: Double decoding scan (nimda type):
@ Associated IP addresses: (211.59.0.204)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A69: Double decoding scan (nimda type):
@ Associated IP addresses: (69.233.130.234)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A70: Double decoding scan (nimda type):
@ Associated IP addresses: (67.181.19.171)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A71: Double decoding scan (nimda type):
@ Associated IP addresses: (218.28.40.100)
@ Number of logged events: (http_access: 8) (http_error: 8)
@ HTTP status codes: [404]
-------------------------------------
A72: Double decoding scan (nimda type):
@ Associated IP addresses: (221.184.100.13)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A73: Double decoding scan (nimda type):
@ Associated IP addresses: (69.86.164.233)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A74: Double decoding scan (nimda type):
@ Associated IP addresses: (60.248.26.50)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A75: Double decoding scan (nimda type):
@ Associated IP addresses: (67.176.32.32)
@ Number of logged events: (http_access: 2) (http_error: 2) (SnortSysLog: 3)
@ HTTP status codes: [404]
-------------------------------------
A76: Double decoding scan (nimda type):
@ Associated IP addresses: (220.28.212.176)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A77: Double decoding scan (nimda type):
@ Associated IP addresses: (172.169.6.104)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A78: Double decoding scan (nimda type):
@ Associated IP addresses: (24.18.186.248)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A79: Double decoding scan (nimda type):
@ Associated IP addresses: (69.158.2.56)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A80: Double decoding scan (nimda type):
@ Associated IP addresses: (62.251.110.161)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A81: Double decoding scan (nimda type):
@ Associated IP addresses: (24.19.201.156)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A82: Double decoding scan (nimda type):
@ Associated IP addresses: (61.235.189.106)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A83: Double decoding scan (nimda type):
@ Associated IP addresses: (63.202.179.73)
@ Number of logged events: (http_access: 32) (http_error: 26)
@ HTTP status codes: [404, 400]
-------------------------------------
A84: Double decoding scan (nimda type):
@ Associated IP addresses: (81.193.64.246)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A85: Double decoding scan (nimda type):
@ Associated IP addresses: (211.211.4.51)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A86: Double decoding scan (nimda type):
@ Associated IP addresses: (67.162.217.35)
@ Number of logged events: (http_access: 32) (http_error: 26)
@ HTTP status codes: [404, 400]
-------------------------------------
A87: Double decoding scan (nimda type):
@ Associated IP addresses: (68.255.20.187)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A88: Double decoding scan (nimda type):
@ Associated IP addresses: (69.210.209.141)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A89: Double decoding scan (nimda type):
@ Associated IP addresses: (24.5.169.95)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A90: Double decoding scan (nimda type):
@ Associated IP addresses: (172.155.203.99)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A91: Double decoding scan (nimda type):
@ Associated IP addresses: (201.129.65.141)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A92: Double decoding scan (nimda type):
@ Associated IP addresses: (69.153.13.148)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A93: Double decoding scan (nimda type):
@ Associated IP addresses: (206.49.194.36)
@ Number of logged events: (http_access: 6) (http_error: 6)
@ HTTP status codes: [404]
-------------------------------------
A94: Double decoding scan (nimda type):
@ Associated IP addresses: (211.59.0.40)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A95: Double decoding scan (nimda type):
@ Associated IP addresses: (69.229.28.252)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A96: Double decoding scan (nimda type):
@ Associated IP addresses: (24.99.140.64)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A97: Double decoding scan (nimda type):
@ Associated IP addresses: (221.234.48.249)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 57)
@ HTTP status codes: [404, 400]
-------------------------------------
A98: Double decoding scan (nimda type):
@ Associated IP addresses: (24.107.54.128)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 67)
@ HTTP status codes: [404, 400]
-------------------------------------
A99: Double decoding scan (nimda type):
@ Associated IP addresses: (61.157.206.11)
@ Number of logged events: (http_access: 5) (http_error: 5) (SnortSysLog: 12)
@ HTTP status codes: [404]
-------------------------------------
A100: Double decoding scan (nimda type):
@ Associated IP addresses: (68.55.90.67)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 54)
@ HTTP status codes: [404, 400]
-------------------------------------
A101: Double decoding scan (nimda type):
@ Associated IP addresses: (202.155.10.139)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 2)
@ HTTP status codes: [404]
-------------------------------------
A102: Double decoding scan (nimda type):
@ Associated IP addresses: (80.161.21.71)
@ Number of logged events: (http_access: 11) (http_error: 10) (SnortSysLog: 34)
@ HTTP status codes: [404]
-------------------------------------
A103: Double decoding scan (nimda type):
@ Associated IP addresses: (209.201.25.170)
@ Number of logged events: (http_access: 23) (http_error: 23) (SnortSysLog: 73)
@ HTTP status codes: [404]
-------------------------------------
A104: Double decoding scan (nimda type):
@ Associated IP addresses: (24.60.73.107)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 65)
@ HTTP status codes: [404, 400]
-------------------------------------
A105: Double decoding scan (nimda type):
@ Associated IP addresses: (211.200.172.163)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 58)
@ HTTP status codes: [404, 400]
-------------------------------------
A106: Double decoding scan (nimda type):
@ Associated IP addresses: (221.210.34.10)
@ Number of logged events: (http_access: 3) (http_error: 3) (SnortSysLog: 5)
@ HTTP status codes: [404]
-------------------------------------
A107: Double decoding scan (nimda type):
@ Associated IP addresses: (60.210.131.23)
@ Number of logged events: (http_access: 4) (http_error: 4) (SnortSysLog: 9)
@ HTTP status codes: [404]
-------------------------------------
A108: Double decoding scan (nimda type):
@ Associated IP addresses: (221.189.148.73)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 54)
@ HTTP status codes: [404, 400]
-------------------------------------
A109: Double decoding scan (nimda type):
@ Associated IP addresses: (63.84.238.40)
@ Number of logged events: (http_access: 21) (http_error: 21) (SnortSysLog: 88)
@ HTTP status codes: [404]
-------------------------------------
A110: Double decoding scan (nimda type):
@ Associated IP addresses: (66.249.194.119)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 4)
@ HTTP status codes: [404]
-------------------------------------
A111: Double decoding scan (nimda type):
@ Associated IP addresses: (61.219.99.89)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A112: Double decoding scan (nimda type):
@ Associated IP addresses: (203.112.195.156)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A113: Double decoding scan (nimda type):
@ Associated IP addresses: (216.84.100.130)
@ Number of logged events: (http_access: 23) (http_error: 23)
@ HTTP status codes: [404]
-------------------------------------
A114: Double decoding scan (nimda type):
@ Associated IP addresses: (67.162.253.25)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A115: Double decoding scan (nimda type):
@ Associated IP addresses: (68.233.81.168)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A116: Double decoding scan (nimda type):
@ Associated IP addresses: (67.162.65.157)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A117: Double decoding scan (nimda type):
@ Associated IP addresses: (82.154.66.15)
@ Number of logged events: (http_access: 16) (http_error: 13)
@ HTTP status codes: [404, 400]
-------------------------------------
A118: Double decoding scan (nimda type):
@ Associated IP addresses: (24.23.244.160)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 56)
@ HTTP status codes: [404, 400]
-------------------------------------
A119: Double decoding scan (nimda type):
@ Associated IP addresses: (69.246.7.31)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 58)
@ HTTP status codes: [404, 400]
-------------------------------------
A120: Double decoding scan (nimda type):
@ Associated IP addresses: (67.170.0.153)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 54)
@ HTTP status codes: [404, 400]
-------------------------------------
A121: Double decoding scan (nimda type):
@ Associated IP addresses: (218.11.95.43)
@ Number of logged events: (http_access: 8) (http_error: 8) (SnortSysLog: 21)
@ HTTP status codes: [404]
-------------------------------------
A122: Double decoding scan (nimda type):
@ Associated IP addresses: (71.16.50.10)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 66)
@ HTTP status codes: [404, 400]
-------------------------------------
A123: Double decoding scan (nimda type):
@ Associated IP addresses: (209.120.201.177)
@ Number of logged events: (http_access: 16) (http_error: 13) (SnortSysLog: 64)
@ HTTP status codes: [404, 400]
-------------------------------------
A124: Code Red Scan:
@ Associated IP addresses: (65.202.15.194)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A125: Code Red Scan:
@ Associated IP addresses: (63.245.85.123)
@ Number of logged events: (http_access: 3) (http_error: 3)
@ HTTP status codes: [404]
-------------------------------------
A126: Code Red Scan:
@ Associated IP addresses: (66.117.40.185)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A127: Code Red Scan:
@ Associated IP addresses: (172.168.100.47)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A128: Code Red Scan:
@ Associated IP addresses: (195.12.85.67)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A129: Code Red Scan:
@ Associated IP addresses: (172.140.206.239)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A130: Code Red Scan:
@ Associated IP addresses: (221.2.159.157)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A131: Code Red Scan:
@ Associated IP addresses: (80.63.173.34)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A132: Code Red Scan:
@ Associated IP addresses: (202.75.41.30)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A133: Code Red Scan:
@ Associated IP addresses: (202.66.47.23)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A134: Code Red Scan:
@ Associated IP addresses: (63.226.106.228)
@ Number of logged events: (http_access: 5) (http_error: 5)
@ HTTP status codes: [404]
-------------------------------------
A135: Code Red Scan:
@ Associated IP addresses: (61.53.32.222)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A136: Code Red Scan:
@ Associated IP addresses: (172.134.23.11)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A137: Code Red Scan:
@ Associated IP addresses: (172.166.225.172)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A138: Code Red Scan & ICMP pings:
@ Associated IP addresses: (218.13.32.15)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 8)
@ HTTP status codes: [404]
-------------------------------------
A139: Code Red Scan:
@ Associated IP addresses: (172.131.91.78)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 5)
@ HTTP status codes: [404]
-------------------------------------
A140: Code Red Scan:
@ Associated IP addresses: (221.15.136.90)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 7)
@ HTTP status codes: [404]
-------------------------------------
A141: Code Red Scan:
@ Associated IP addresses: (172.155.134.244)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A142: Code Red Scan:
@ Associated IP addresses: (172.141.217.125)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A143: Code Red Scan:
@ Associated IP addresses: (81.241.4.157)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A144: Code Red Scan:
@ Associated IP addresses: (218.62.41.222)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A145: Code Red Scan:
@ Associated IP addresses: (60.208.186.49)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A146: Code Red Scan:
@ Associated IP addresses: (61.54.219.221)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A147: Code Red Scan:
@ Associated IP addresses: (221.136.82.153)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A148: Code Red Scan:
@ Associated IP addresses: (66.133.205.244)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A149: Code Red Scan:
@ Associated IP addresses: (63.102.226.241)
@ Number of logged events: (http_access: 4) (http_error: 4)
@ HTTP status codes: [404]
-------------------------------------
A150: Code Red Scan:
@ Associated IP addresses: (82.251.81.153)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A151: Code Red Scan:
@ Associated IP addresses: (82.75.223.39)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A152: Code Red Scan:
@ Associated IP addresses: (172.146.155.53)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A153: Code Red Scan & ICMP ping:
@ Associated IP addresses: (201.9.48.227)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 5)
@ HTTP status codes: [404]
-------------------------------------
A154: Code Red Scan:
@ Associated IP addresses: (201.9.104.83)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 4)
@ HTTP status codes: [404]
-------------------------------------
A155: /NULL.printer scan:
@ Associated IP addresses: (61.88.122.10)
@ Number of logged events: (http_access: 2) (http_error: 2) (SnortSysLog: 4)
@ HTTP status codes: [404]
-------------------------------------
A156: /NULL.printer scan:
@ Associated IP addresses: (216.184.121.184)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A157: /NULL.printer scan:
@ Associated IP addresses: (68.146.167.38)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A158: /NULL.printer scan:
@ Associated IP addresses: (69.234.56.155)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A159: /NULL.printer scan:
@ Associated IP addresses: (70.147.9.192)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A160: /NULL.printer scan:
@ Associated IP addresses: (66.112.85.249)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 4)
@ HTTP status codes: [404]
-------------------------------------
A161: /NULL.printer scan:
@ Associated IP addresses: (66.64.221.234)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A162: /NULL.printer scan:
@ Associated IP addresses: (68.73.139.166)
@ Number of logged events: (http_access: 1) (http_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A163: /NULL.printer scan:
@ Associated IP addresses: (66.18.136.228)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 5)
@ HTTP status codes: [404]
-------------------------------------
A164: /NULL.printer scan:
@ Associated IP addresses: (64.237.165.66)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 3)
@ HTTP status codes: [404]
-------------------------------------
A165: /NULL.printer scan:
@ Associated IP addresses: (195.70.152.248)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 2)
@ HTTP status codes: [404]
-------------------------------------
A166: /sumthin scan:
@ Associated IP addresses: (211.22.73.68)
@ Number of logged events: (http_access: 6) (http_error: 6) (http_ssl_error: 6)
@ HTTP status codes: [404]
-------------------------------------
A167: /sumthin scan:
@ Associated IP addresses: (210.127.248.52)
@ Number of logged events: (http_access: 46) (http_error: 46) (http_ssl_error: 46) (SnortSysLog: 24)
@ HTTP status codes: [404]
-------------------------------------
A168: /sumthin scan:
@ Associated IP addresses: (61.30.127.4)
@ Number of logged events: (http_access: 3) (http_error: 3) (http_ssl_error: 3)
@ HTTP status codes: [404]
-------------------------------------
A169: /sumthin scan:
@ Associated IP addresses: (220.95.232.60)
@ Number of logged events: (http_access: 23) (http_error: 23) (http_ssl_error: 23)
@ HTTP status codes: [404]
-------------------------------------
A170: /sumthin scan:
@ Associated IP addresses: (220.95.231.3)
@ Number of logged events: (http_access: 23) (http_error: 23) (http_ssl_error: 23)
@ HTTP status codes: [404]
-------------------------------------
A171: /sumthin scan:
@ Associated IP addresses: (194.225.176.4)
@ Number of logged events: (http_access: 12) (http_error: 12) (http_ssl_error: 12)
@ HTTP status codes: [404]
-------------------------------------
A172: /sumthin scan:
@ Associated IP addresses: (212.59.13.202)
@ Number of logged events: (http_access: 1) (http_error: 1) (http_ssl_error: 1)
@ HTTP status codes: [404]
-------------------------------------
A173: /sumthin scan:
@ Associated IP addresses: (60.248.32.153)
@ Number of logged events: (http_access: 16) (http_error: 16) (http_ssl_error: 16) (SnortSysLog: 23)
@ HTTP status codes: [404]
-------------------------------------
A174: /sumthin scan:
@ Associated IP addresses: (61.81.96.175)
@ Number of logged events: (http_access: 23) (http_error: 23) (http_ssl_error: 23) (SnortSysLog: 26)
@ HTTP status codes: [404]
-------------------------------------
A175: /sumthin scan:
@ Associated IP addresses: (200.87.201.251)
@ Number of logged events: (http_access: 4) (http_error: 4) (http_ssl_error: 4) (SnortSysLog: 4)
@ HTTP status codes: [404]
-------------------------------------
A176: /sumthin scan:
@ Associated IP addresses: (207.228.251.216)
@ Number of logged events: (http_access: 23) (http_error: 23) (http_ssl_error: 23) (SnortSysLog: 29)
@ HTTP status codes: [404]
-------------------------------------
A177: /_vti_bin/_vti_aut/fp30reg.dll scan:
@ Associated IP addresses: (65.117.45.251)
@ Number of logged events: (http_access: 23) (http_error: 23)
@ HTTP status codes: [404]
-------------------------------------
A178: /_vti_bin/_vti_aut/fp30reg.dll scan:
@ Associated IP addresses: (148.245.28.39)
@ Number of logged events: (http_access: 22) (http_error: 22)
@ HTTP status codes: [404]
-------------------------------------
A179: /_vti_bin/_vti_aut/fp30reg.dll scan & ICMP pings:
@ Associated IP addresses: (201.130.217.132)
@ Number of logged events: (http_access: 11) (http_error: 11) (SnortSysLog: 143)
@ HTTP status codes: [404]
-------------------------------------
A180: /_vti_bin/_vti_aut/fp30reg.dll scan & ICMP pings:
@ Associated IP addresses: (4.152.207.126)
@ Number of logged events: (http_access: 46) (http_error: 46) (SnortSysLog: 615)
@ HTTP status codes: [404]
-------------------------------------
A181: /_vti_bin/_vti_aut/fp30reg.dll scan & ICMP pings:
@ Associated IP addresses: (4.152.207.238)
@ Number of logged events: (http_access: 94) (http_error: 94) (SnortSysLog: 1330)
@ HTTP status codes: [404]
-------------------------------------
A182: /_vti_bin/_vti_aut/fp30reg.dll scan:
@ Associated IP addresses: (216.105.210.91)
@ Number of logged events: (http_access: 45) (http_error: 45)
@ HTTP status codes: [404]
-------------------------------------
A183: /_vti_bin/_vti_aut/fp30reg.dll scan:
@ Associated IP addresses: (64.122.238.114)
@ Number of logged events: (http_access: 91) (http_error: 91)
@ HTTP status codes: [404]
-------------------------------------
A184: /_vti_bin/_vti_aut/fp30reg.dll scan:
@ Associated IP addresses: (216.171.174.124)
@ Number of logged events: (http_access: 28) (http_error: 28)
@ HTTP status codes: [404]
-------------------------------------
A185: /_vti_bin/_vti_aut/fp30reg.dll scan:
@ Associated IP addresses: (66.173.230.27)
@ Number of logged events: (http_access: 40) (http_error: 40)
@ HTTP status codes: [404]
-------------------------------------
A186: /_vti_bin/_vti_aut/fp30reg.dll scan & ICMP pings:
@ Associated IP addresses: (210.116.59.164)
@ Number of logged events: (http_access: 184) (http_error: 184) (SnortSysLog: 2238)
@ HTTP status codes: [404]
-------------------------------------
A187: /_vti_bin/_vti_aut/fp30reg.dll scan & ICMP pings:
@ Associated IP addresses: (65.16.76.54)
@ Number of logged events: (http_access: 2) (http_error: 2) (SnortSysLog: 45)
@ HTTP status codes: [404]
-------------------------------------
A188: /_vti_bin/_vti_aut/fp30reg.dll scan & ICMP ping:
@ Associated IP addresses: (202.122.16.7)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 13)
@ HTTP status codes: [404]
-------------------------------------
A189: /scripts/nsiislog.dll scan:
@ Associated IP addresses: (69.67.42.139)
@ Number of logged events: (http_access: 1) (http_error: 1) (SnortSysLog: 1)
@ HTTP status codes: [404]
-------------------------------------
A190: CONNECT Scan:
@ Associated IP addresses: (82.229.169.73)
@ Number of logged events: (http_access: 23)
@ HTTP status codes: [405]
-------------------------------------
A191: CONNECT Scan:
@ Associated IP addresses: (218.78.209.75)
@ Number of logged events: (http_access: 2)
@ HTTP status codes: [405]
-------------------------------------
A192: CONNECT Scan:
@ Associated IP addresses: (218.78.209.79)
@ Number of logged events: (http_access: 1)
@ HTTP status codes: [405]
-------------------------------------
A193: CONNECT Scan:
@ Associated IP addresses: (219.153.10.141)
@ Number of logged events: (http_access: 1)
@ HTTP status codes: [405]
-------------------------------------
A194: CONNECT Scan:
@ Associated IP addresses: (219.153.10.140)
@ Number of logged events: (http_access: 2)
@ HTTP status codes: [405]
-------------------------------------
A195: CONNECT Scan:
@ Associated IP addresses: (218.78.209.77)
@ Number of logged events: (http_access: 2)
@ HTTP status codes: [405]
-------------------------------------
A196: CONNECT Scan:
@ Associated IP addresses: (218.78.209.67)
@ Number of logged events: (http_access: 1)
@ HTTP status codes: [405]
-------------------------------------
A197: CONNECT Scan:
@ Associated IP addresses: (193.109.122.45)
@ Number of logged events: (http_access: 1) (SnortSysLog: 1)
@ HTTP status codes: [405]
-------------------------------------
A198: CONNECT Scan:
@ Associated IP addresses: (193.109.122.47)
@ Number of logged events: (http_access: 1) (SnortSysLog: 1)
@ HTTP status codes: [405]
-------------------------------------
A199: CONNECT Scan:
@ Associated IP addresses: (193.109.122.23)
@ Number of logged events: (http_access: 1) (SnortSysLog: 3)
@ HTTP status codes: [405]
-------------------------------------
A200: CONNECT Scan: