123.7.194.205 // failure audit: an account failed to log on
186.170.16.222 // failure audit: an account failed to log on
124.158.122.140 // failure audit: an account failed to log on
162.247.74.7 // Scanning IP
204.8.96.155 // Scanning IP
204.8.96.105 // Scanning IP
182.182.71.235 // failure audit: an account failed to log on
45.227.254.153 // failure audit: an account failed to log on
152.32.156.158 // network connection detected
42.117.154.84 // failure audit: an account failed to log on
103.1.92.68 // network connection detected
45.134.225.15 // failure audit: an account failed to log on
185.147.124.245 // failure audit: an account failed to log on
213.154.14.68 // failure audit: an account failed to log on
185.246.209.152 // failure audit: an account failed to log on
149.202.130.57 // failure audit: an account failed to log on
78.142.18.92 // failure audit: an account failed to log on
223.100.22.69 // failure audit: an account failed to log on
45.227.254.120 // failure audit: an account failed to log on
190.186.3.2 // failure audit: an account failed to log on
2.179.76.229 // network connection detected
43.134.187.116 // failure audit: an account failed to log on
128.185.235.26 // failure audit: an account failed to log on
88.214.48.35 // failure audit: an account failed to log on
183.82.144.84 // network connection detected, failure audit: an account failed to log on
159.65.133.5 // Credential Stuffing
152.42.212.110 // Credential Stuffing
167.71.207.7 // Credential Stuffing
139.59.115.129 // Credential Stuffing
152.42.203.135 // Credential Stuffing
88.214.50.50 // failure audit: an account failed to log on
193.29.13.50 // failure audit: an account failed to log on
111.68.102.195 // failure audit: an account failed to log on
118.182.101.109 // failure audit: an account failed to log on
65.109.80.122 // failure audit: an account failed to log on
88.214.25.73 // failure audit: an account failed to log on
196.188.63.229 // failure audit: an account failed to log on
45.227.254.41 // failure audit: an account failed to log on
106.37.75.191 // failure audit: an account failed to log on
3.148.219.146 // failure audit: an account failed to log on
88.214.25.74 // failure audit: an account failed to log on
203.160.72.147 // failure audit: an account failed to log on
34.68.34.64 // attempt log4j exploits
154.192.32.24 // failure audit: an account failed to log on
182.182.49.114 // failure audit: an account failed to log on
104.247.220.146 // failure audit: an account failed to log on
198.244.177.154 // failure audit: an account failed to log on
83.21.1.30 // network connection detected
194.180.49.39 // network connection detected
177.159.119.54 // failure audit: an account failed to log on
113.163.17.112 // failure audit: an account failed to log on
139.135.63.252 // failure audit: an account failed to log on
182.182.85.170 // failure audit: an account failed to log on
113.160.207.151 // failure audit: an account failed to log on
152.32.146.202 // network connection detected
190.94.251.11 // network connection detected
176.29.176.111 // network connection detected
93.87.25.89 // network connection detected
192.190.43.57 // network connection detected
179.43.141.234 // network connection detected
115.244.249.74 // network connection detected
189.206.33.2 // network connection detected
170.231.81.131 // network connection detected
59.145.183.86 // network connection detected
37.232.88.238 // network connection detected
177.39.84.90 // network connection detected
85.104.3.188 // network connection detected
185.246.209.153 // failure audit: an account failed to log on
104.247.193.82 // failure audit: an account failed to log on
193.163.125.161 // Scanning IP
195.82.147.174 // failure audit: an account failed to log on
60.247.92.186 // Scanning IP
103.203.59.0 // Scanning IP
99.88.80.211 // failure audit: an account failed to log on
8.34.210.53 // attempt log4j
5.178.87.180 // failure audit: an account failed to log on
182.182.91.212 // failure audit: an account failed to log on
203.115.110.205 // network connection detected
113.160.98.131 // failure audit: an account failed to log on
65.108.144.82 // network connection detected
79.127.132.8 // network connection detected, failure audit: an account failed to log on
217.64.22.6 // network connection detected
157.254.164.14 // failure audit: an account failed to log on
194.180.48.149 // failure audit: an account failed to log on
182.182.21.92 // failure audit: an account failed to log on
187.190.73.49 // failure audit: an account failed to log on
44.212.182.171 // Incident 11042025
44.218.96.168 // Incident 11042025
3.216.138.97 // Incident 11042025
3.238.166.239 // Incident 11042025
3.238.214.71 // Incident 11042025
3.238.215.209 // Incident 11042025
44.212.182.5 // Incident 11042025
3.238.166.204 // Incident 11042025
3.238.214.246 // Incident 11042025
3.216.140.82 // Incident 11042025
3.216.144.213 // Incident 11042025
3.216.143.179 // Incident 11042025
44.210.64.198 // Incident 11042025
44.220.31.21 // Incident 11042025
44.220.29.198 // Incident 11042025
3.238.212.240 // Incident 11042025
44.212.176.163 // Incident 11042025
44.212.182.186 // Incident 11042025
3.238.215.231 // Incident 11042025
44.212.182.71 // Incident 11042025
3.216.144.42 // Incident 11042025
3.216.145.208 // Incident 11042025
44.212.177.55 // Incident 11042025
3.216.138.114 // Incident 11042025
44.212.178.12 // Incident 11042025
3.216.136.231 // Incident 11042025
3.238.214.160 // Incident 11042025
44.212.178.71 // Incident 11042025
3.216.141.177 // Incident 11042025
44.210.64.158 // Incident 11042025
44.212.177.255 // Incident 11042025
44.220.29.125 // Incident 11042025
44.220.28.190 // Incident 11042025
3.216.145.155 // Incident 11042025
44.206.7.75 // Incident 11042025
44.220.28.12 // Incident 11042025
44.210.65.190 // Incident 11042025
44.212.180.88 // Incident 11042025
44.210.65.12 // Incident 11042025
44.218.96.242 // Incident 11042025
3.216.144.96 // Incident 11042025
3.216.138.61 // Incident 11042025
3.216.144.167 // Incident 11042025
31.171.154.59 // Incident 11042025
185.7.214.13 // failure audit: an account failed to log on
185.42.12.205 // failure audit: an account failed to log on
45.88.186.251 // network connection detected
46.209.206.178 // network connection detected
161.97.182.239 // failure audit: an account failed to log on
77.73.236.86 // failure audit: an account failed to log on
81.21.81.129 // network connection detected
36.108.170.27 // network connection detected
88.214.25.115 // failure audit: an account failed to log on
45.135.232.66 // failure audit: an account failed to log on
94.20.81.6 // network connection detected
203.115.110.73 // network connection detected
34.135.174.224 // failure audit: an account failed to log on
185.190.24.101 // Credential Stuffing
58.27.195.243 // failure audit: an account failed to log on
182.182.50.166 // failure audit: an account failed to log on
58.181.99.75 // failure audit: an account failed to log on
58.181.99.73 // failure audit: an account failed to log on
185.152.66.226 // network connection detected, failure audit: an account failed to log on
92.42.15.193 // failure audit: an account failed to log on
5.182.4.154 // failure audit: an account failed to log on
95.143.191.159 // failure audit: an account failed to log on
92.53.90.104 // failure audit: an account failed to log on
77.223.118.28 // failure audit: an account failed to log on
188.246.224.72 // failure audit: an account failed to log on
185.137.233.87 // failure audit: an account failed to log on
188.124.37.22 // failure audit: an account failed to log on
188.124.36.148 // failure audit: an account failed to log on
45.248.64.165 // Brute
79.127.132.50 // network connection detected, failure audit: an account failed to log on
210.19.252.30 // network connection detected
194.180.48.85 // failure audit: an account failed to log on
80.66.88.30 // failure audit: an account failed to log on
103.168.204.62 // network connection detected
165.227.156.225 // Port Scanning
170.64.229.42 // Port Scanning
103.35.188.74 // SSL Fails
167.88.160.70 // SSL Fails
5.180.24.93 // SSL Fails
103.35.189.241 // SSL Fails
1.228.113.10 // failure audit: an account failed to log on
5.182.5.119 // failure audit: an account failed to log on
95.143.190.228 // failure audit: an account failed to log on
45.92.177.109 // failure audit: an account failed to log on
198.12.89.161 // failure audit: an account failed to log on
34.173.30.211 // failure audit: an account failed to log on
182.182.28.185 // failure audit: an account failed to log on
111.7.96.156 // Scanning IP
8.152.208.190 // Web Exploits
45.90.162.234 // Web Exploits
34.19.127.189 // JNDI Attempts
103.244.90.115 // network connection detected
45.227.254.154 // failure audit: an account failed to log on
45.227.254.155 // failure audit: an account failed to log on
45.227.254.151 // failure audit: an account failed to log on
45.227.254.156 // failure audit: an account failed to log on
66.96.194.170 // Credential Stuffing
87.120.127.0/27 // Credential Stuffing
92.119.196.0/27 // Credential Stuffing
92.119.197.0/27 // Credential Stuffing
195.178.110.164 // Web Exploits
45.227.254.152 // failure audit: an account failed to log on
35.188.74.106 // Web Exploits
80.94.95.114 // failure audit: an account failed to log on
43.230.203.254 // network connection detected
118.71.169.95 // failure audit: an account failed to log on
141.98.11.61 // failure audit: an account failed to log on
185.147.124.165 // failure audit: an account failed to log on
43.156.134.57 // network connection detected
186.121.214.108 // failure audit: an account failed to log on
194.26.192.94 // network connection detected
45.86.203.241 // failure audit: an account failed to log on
34.171.115.142 // Web Exploits
34.135.113.150 // failure audit: an account failed to log on
194.180.49.244 // failure audit: an account failed to log on
103.219.60.153 // failure audit: an account failed to log on
34.72.196.98 // failure audit: an account failed to log on
222.124.139.164 // failure audit: an account failed to log on
162.254.24.185 // network connection detected
213.21.228.3 // network connection detected, failure audit: an account failed to log on
185.192.70.214 // failure audit: an account failed to log on
147.45.45.220 // failure audit: an account failed to log on
206.238.178.107 // failure audit: an account failed to log on
80.94.95.90 // failure audit: an account failed to log on
193.29.13.6 // failure audit: an account failed to log on
179.60.146.60 // failure audit: an account failed to log on
141.98.11.27 // Web Exploits
141.98.11.210 // Web Exploits
91.199.163.13 // failure audit: an account failed to log on
50.170.225.123 // failure audit: an account failed to log on
194.180.48.42 // failure audit: an account failed to log on
111.93.74.158 // network connection detected
91.199.163.12 // failure audit: an account failed to log on
179.60.146.61 // failure audit: an account failed to log on
45.87.43.37 // Web Exploits
103.78.165.76 // network connection detected
185.191.127.222 // Malicious Scanning
45.86.203.25 // network connection detected, failure audit: an account failed to log on
185.192.69.215 // network connection detected, failure audit: an account failed to log on
194.32.120.20 // network connection detected, failure audit: an account failed to log on
165.227.188.42 // Malicious Scanning
35.226.222.151 // Web Exploits
34.57.187.192 // Web Exploits
168.119.5.223 // network connection detected, failure audit: an account failed to log on
194.180.49.228 // failure audit: an account failed to log on
182.176.84.7 // failure audit: an account failed to log on
194.5.53.18 // network connection detected, failure audit: an account failed to log on
45.154.138.22 // network connection detected, failure audit: an account failed to log on
185.194.178.38 // failure audit: an account failed to log on
194.180.48.142 // network connection detected, failure audit: an account failed to log on
218.250.231.191 // Web Exploits
161.97.87.220 // failure audit: an account failed to log on
35.239.83.250 // Web Exploits
181.115.171.157 // Scanning IP
195.178.110.163 // Secret Digging
185.7.214.16 // failure audit: an account failed to log on
34.45.57.231 // failure audit: an account failed to log on
34.28.58.52 // Web Exploits
31.170.22.205 // Web Exploits
34.132.135.234 // attempt exploits
218.255.4.253 // failure audit: an account failed to log on
206.1.52.119 // failure audit: an account failed to log on
34.19.116.62 // attempt exploits
35.192.153.30 // attempt exploits
196.191.212.238 // Brute Force
89.179.78.247 // Brute Force
196.28.226.125 // Brute Force
5.180.234.228 // Brute Force
2.55.125.200 // Brute Force
77.83.255.10 // Brute Force
72.5.43.31 // Cyberpunks[.] chat IR
34.30.4.191 // Web Exploits
34.135.157.139 // Web Exploits
34.70.230.87 // Web Exploits
61.53.144.224 // Web Exploits
185.42.12.5 // failure audit: an account failed to log on
45.164.177.118 // Web Exploits
130.61.60.124 // Web Exploits
194.156.99.80 // Web Exploits
34.71.205.208 // Web Exploits
185.40.4.51 // Web Exploits
45.148.10.35 // Web Exploits
62.60.191.64 // Scanning IP
139.59.125.28 // Web Exploits
167.172.224.131 // Web Exploits
111.7.106.107 // Scanning IP
34.121.46.155 // Web Exploits
185.156.73.169 // failure audit: an account failed to log on
185.156.73.167 // failure audit: an account failed to log on
124.135.44.252 // Web Exploits
185.243.96.135 // failure audit: an account failed to log on
92.63.197.9 // failure audit: an account failed to log on
94.102.52.73 // failure audit: an account failed to log on
185.243.96.107 // failure audit: an account failed to log on
45.148.10.81 // Hostile Scanning
34.69.3.247 // Web Exploits
34.44.147.20 // Web Exploits
34.134.31.77 // Web Exploits
158.58.190.46 // Web Exploits
34.19.116.58 // attempt exploits
35.202.89.174 // Web Exploits
194.0.234.34 // failure audit: an account failed to log on
80.64.30.62 // failure audit: an account failed to log on
34.30.210.247 // Web Exploits
34.28.114.111 // Web Exploits
196.251.83.180 // Web Exploits
118.193.56.246 // Scanning IP
5.143.245.194 // Web Exploits
185.42.12.66 // SSL Fails
194.165.16.18 // failure audit: an account failed to log on
91.238.181.8 // failure audit: an account failed to log on
91.238.181.10 // failure audit: an account failed to log on
91.238.181.7 // failure audit: an account failed to log on
91.238.181.6 // network connection detected, failure audit: an account failed to log on
185.213.173.51 // Web Exploits
45.164.177.161 // Log4j Attempts
185.91.127.9 // Log4j Attempts
203.113.4.231 // failure audit: an account failed to log on
8.34.210.49 // attempt exploits
113.105.164.28 // failure audit: an account failed to log on
185.243.96.116 // failure audit: an account failed to log on
177.92.240.168 // attempt exploits
50.3.137.177 // Brute Force
5.157.5.100 // Brute Force
107.173.112.245 // Brute Force
185.122.170.10 // Brute Force
23.81.230.134 // Brute Force
138.94.218.193 // Brute Force
104.160.17.116 // Brute Force
107.150.71.30 // Brute Force
34.68.34.81 // attempt exploits
45.178.251.94 // Web Exploits
185.42.12.65 // SSL Fails
119.185.243.223 // Web Exploits
35.224.204.209 // Web Exploits
34.44.34.37 // Web Exploits
103.146.158.143 // Web Exploits
35.195.46.0 // Web Exploits
143.110.208.18 // Web Exploits
95.214.53.198 // Web Exploits
34.67.56.248 // Web Exploits
117.186.191.142 // Web Exploits
213.230.92.40 // Scanning
209.38.144.40 // Scanning
92.255.57.86 // failure audit: an account failed to log on
24.199.112.66 // Port scanning
194.165.16.163 // failure audit: an account failed to log on
194.165.16.164 // failure audit: an account failed to log on
194.165.16.162 // failure audit: an account failed to log on
194.165.16.167 // failure audit: an account failed to log on
194.165.16.161 // failure audit: an account failed to log on
194.165.16.166 // failure audit: an account failed to log on
194.165.16.165 // failure audit: an account failed to log on
91.238.181.94 // failure audit: an account failed to log on
91.238.181.92 // failure audit: an account failed to log on
91.238.181.95 // failure audit: an account failed to log on
91.238.181.96 // failure audit: an account failed to log on
91.238.181.93 // failure audit: an account failed to log on
91.238.181.91 // failure audit: an account failed to log on
88.214.25.123 // failure audit: an account failed to log on
88.214.25.125 // failure audit: an account failed to log on
88.214.25.121 // failure audit: an account failed to log on
88.214.25.124 // failure audit: an account failed to log on
88.214.25.122 // failure audit: an account failed to log on
46.73.96.182 // Password Spray
80.64.30.118 // failure audit: an account failed to log on
194.85.251.34 // Web Exploits
37.221.66.57 // DDOS
34.19.116.54 // Web Exploits
197.205.59.231 // Brute Force
103.247.7.66 // attempt exploits
128.199.215.40 // Scanning IP
77.51.214.170 // Brute Force
111.48.208.197 // Brute Force
46.72.252.233 // Brute Force
112.168.71.109 // Brute Force
188.227.66.92 // Brute Force
110.35.63.30 // Brute Force
111.70.19.149 // Brute Force
61.146.121.14 // Brute Force
218.23.95.14 // Brute Force
221.149.233.245 // Brute Force
220.120.224.227 // Brute Force
27.223.100.90 // Brute Force
117.70.94.155 // Port scanning
45.125.66.114 // Web Exploits
124.228.83.189 // Password Spray
165.154.226.146 // Web Exploits
122.225.203.106 // Brute Force
124.114.180.50 // Brute force
37.26.136.250 // Aikapool Crypto mining pool IP
91.224.92.10 // Web Exploits
69.50.94.110 // BruteForce
88.214.25.111 // failure audit: an account failed to log on
88.214.25.116 // failure audit: an account failed to log on
223.118.50.87 // appserve request
34.19.116.48 // attempt exploits
134.122.106.248 // Scanning IP
38.54.101.65 // Palo Alto PAN-OS CVE-2025-0108 Auth Bypass Attempt - GreyNoise
1.55.112.205 // Palo Alto PAN-OS CVE-2025-0108 Auth Bypass Attempt - GreyNoise
123.116.247.134 // Palo Alto PAN-OS CVE-2025-0108 Auth Bypass Attempt - GreyNoise
198.12.122.248 // Palo Alto PAN-OS CVE-2025-0108 Auth Bypass Attempt - GreyNoise
47.190.9.241 // Palo Alto PAN-OS CVE-2025-0108 Auth Bypass Attempt - greynoise
38.54.50.252 // Palo Alto PAN-OS CVE-2025-0108 Auth Bypass Attempt - greynoise
121.202.153.100 // Brute Force
61.153.208.38 // Brute Force
185.42.12.96 // Fortigate Brute
141.98.11.205 // Web Exploits
34.68.34.92 // attempt exploits
221.224.2.202 // Brute Force
182.76.87.90 // Brute Force
91.134.185.87 // Scanning IP
185.156.73.166 // failure audit: an account failed to log on
36.139.105.112 // Scanning
222.216.206.99 // Web Exploits
47.100.201.178 // Web Exploits
190.212.140.11 // Web Exploits
202.0.92.253 // Web Exploits
8.218.73.108 // Web Exploits
81.181.248.148 // Web Exploits
221.122.67.75 // Web Exploits
124.236.100.56 // Web bot: DDoS
154.212.141.161 // Scanning IP
130.61.229.116 // Web Exploits
179.60.146.32 // failure audit: an account failed to log on
179.60.146.37 // failure audit: an account failed to log on
179.60.146.35 // failure audit: an account failed to log on
141.98.83.10 // failure audit: an account failed to log on
141.98.83.70 // failure audit: an account failed to log on
179.60.146.31 // failure audit: an account failed to log on
179.60.146.36 // failure audit: an account failed to log on
64.62.156.41 // Scanning IP
149.137.142.15 // BackBlaze IP Address
202.22.140.219 // Malicious Login
36.189.253.253 // Web Exploits
146.19.24.76 // Scanning IP
8.34.210.35 // attempt exploits
85.206.91.51 // Brute Force
135.125.204.13 // Brute Force
185.42.12.124 // Credential Stuffing
185.93.89.118 // Web Exploits
185.156.73.74 // failure audit: an account failed to log on
92.63.197.22 // failure audit: an account failed to log on
49.236.203.211 // Scanning
75.119.138.110 // Web Exploits
178.216.220.91 // Brute Force
110.175.220.250 // Brute Force
34.68.34.85 // attempt exploits
141.98.10.33 // Network connection detected
154.212.141.147 // Scanning IP
113.140.95.250 // Brute Force
8.211.44.115 // TCP Scans
192.42.116.212 // Scanning IP
84.239.45.17 // Scanning IP
34.68.34.87 // attempt exploits
102.53.15.54 // Brute Force
34.68.34.89 // Malicious Scanning
13.64.108.189 // SSL Fail
65.49.1.41 // SSL Fail
65.49.1.43 // SSL fail
36.224.97.59 // Web Exploits
60.13.146.4 // Web Exploits
5.189.153.135 // Web Exploits
45.61.157.172 // SSL Fail
144.172.96.123 // SSL Fail
144.172.97.104 // SSL Fail
172.86.111.64 // SSL Fail
45.150.65.66 // SSL Fail
103.113.70.129 // SSL Fail
45.61.135.124 // SSL Fail
103.35.190.61 // SSL Fail
50.114.94.170 // SSL Fail
193.56.116.207 // SSL Fail
193.37.33.223 // SSL Fail
157.97.121.119 // SSL Fail
193.37.33.246 // SSL Fail
136.144.42.214 // SSL Fail
45.132.115.6 // SSL Fail
104.234.32.168 // SSL Fail
45.146.55.36 // SSL Fail
35.89.137.11 // Web Exploits
192.42.116.201 // TOR
185.220.101.54 // TOR
87.121.84.7 // Web Exploits
91.134.185.88 // Scanning IP
207.90.244.2 // Scanning IP
8.34.210.50 // attempt exploits
174.138.84.177 // Scanning IP
185.42.12.86 // failure audit: an account failed to log on
167.114.209.103 // Scanning IP
34.68.34.66 // attempt exploits
34.68.34.91 // attempt exploits
146.185.239.70 // Brute Force
45.135.232.124 // failure audit: an account failed to log on
111.23.122.227 // Web Exploits
185.42.12.42 // failure audit: an account failed to log on
95.164.35.50 // SSL Fail
94.131.97.81 // SSL Fail
95.164.69.68 // SSL Fail
94.131.120.228 // SSL Fail
45.83.131.89 // SSL Fail
45.83.20.253 // SSL Fail
176.120.75.183 // SSL Fail
185.73.125.74 // SSL Fail
176.120.75.184 // SSL Fail
176.120.75.209 // SSL Fail
176.120.75.145 // SSL Fail
176.120.75.142 // SSL Fail
147.135.23.100 // Scanning
185.42.12.58 // failure audit: an account failed to log on
185.42.12.59 // failure audit: an account failed to log on
34.19.127.183 // attempt exploits
154.84.61.148 // Web Exploits
146.190.145.108 // Web Exploits
123.160.129.212 // Brute Force
108.165.153.95 // Brute Force
211.196.31.2 // Brute Force
34.68.34.75 // attempt exploits
34.68.34.77 // attempt exploits
8.34.210.51 // attempt exploits
197.55.224.113 // spray
38.180.6.79 // Brute Force
172.86.109.95 // Brute Force
172.86.106.65 // Brute Force
172.86.104.221 // Brute Force
172.86.111.210 // Brute Force
195.149.87.72 // Brute Force
38.180.6.75 // Scanning IP
109.248.160.118 // SSL Fails
198.54.131.124 // SSL Fails
172.86.105.244 // SSL Fails
38.180.135.173 // SSL Fails
38.180.61.208 // SSL Fails
38.180.91.185 // SSL Fails
37.1.209.202 // SSL Fails
172.86.106.231 // SSL Fails
38.180.25.215 // SSL Fails
185.196.10.129 // Web Exploits
65.49.1.84 // Scanning IP
45.159.231.124 // Web Exploits
38.180.91.21 // SSL Fails
38.180.61.52 // SSL Fails
4.156.21.82 // Scanning IP
103.153.77.181 // Web Exploits
34.19.127.201 // Web Exploits
34.19.127.215 // attempt exploits
34.19.127.181 // attempt exploits
93.91.119.151 // VPN Attempts
154.213.184.16 // Malicious Scanning
98.175.31.195 // Malicious IP
196.250.178.160 // Brute Force
222.161.242.146 // SSL Fails
121.202.204.100 // SSL Fails
183.249.1.72 // SSL Fails
34.68.34.71 // attempt exploits
165.154.172.88 // Scanning IP
104.18.9.38 // This is a local news website in Denmark http://thelocal.dk used so customers can check that they are consuming the Blacklist correctly.
103.226.248.206 // Web Exploits
149.22.94.37 // Fortigate Vuln CVE-2024-55591
37.19.196.65 // Fortigate Vuln CVE-2024-55591
155.133.4.175 // Fortigate Vuln CVE-2024-55591
87.249.138.47 // Fortigate Vuln CVE-2024-55591
45.55.158.47 // Fortigate Vuln CVE-2024-55591
82.147.88.107 // SSL Fails
31.58.141.189 // SSL Fails
45.89.244.133 // SSL Fails
95.215.204.146 // SSL Fails
185.92.182.99 // SSL Fails
82.147.88.133 // SSL Fails
195.211.124.207 // SSL Fails
82.147.88.90 // SSL Fails
104.254.90.243 // SSL Fails
82.147.88.89 // SSL Fails
82.147.88.87 // SSL Fails
193.46.255.0/24 // SSL Fails
147.45.47.0/24 // SSL Fails
185.92.183.92 // SSL Fails
46.8.225.109 // SSL Fails
217.138.195.27 // SSL Fails
208.77.22.212 // SSL Fails
64.42.179.51 // SSL Fails
193.176.158.83 // SSL Fails
185.92.182.143 // SSL Fails
185.92.180.167 // SSL Fails
198.54.130.28 // SSL Fails
173.249.217.38 // SSL Fails
192.145.126.115 // SSL Fails
46.8.78.12 // SSL Fails
45.159.208.151 // SSL Fails
46.8.226.109 // SSL Fails
45.156.25.248 // Brute Force
82.147.88.23 // SSL Fails
46.8.64.173 // SSL Fails
194.113.37.190 // SSL Fails
193.43.72.212 // SSL Fails
193.107.93.5 // SSL Fails
193.107.93.135 // SSL Fails
193.107.92.207 // SSL Fails
193.107.92.205 // SSL Fails
185.159.128.71 // SSL Fails
109.248.160.181 // SSL Fails
193.107.92.203 // SSL Fails
2.58.47.203 // SSL Fails
184.75.221.59 // SSL Fails
184.75.221.43 // SSL Fails
184.75.221.180 // SSL Fails
64.42.179.35 // SSL Fails
184.75.223.227 // SSL Fails
45.152.114.22 // SSL Fails
184.75.223.195 // SSL Fails
217.151.98.168 // SSL Fails
193.107.93.129 // SSL Fails
89.238.150.43 // SSL Fails
194.116.215.247 // SSL Fails
204.8.98.65 // SSL Fails
104.193.135.243 // SSL Fails
184.75.221.211 // SSL Fails
184.75.221.171 // SSL Fails
184.75.221.195 // SSL Fails
104.254.90.203 // SSL Fails
184.75.221.163 // SSL Fails
193.107.93.152 // SSL Fails
146.70.61.139 // SSL Fails
84.39.116.180 // SSL Fails
146.70.61.147 // SSL Fails
89.249.74.213 // SSL Fails
84.39.117.57 // SSL Fails
89.249.74.218 // SSL Fails
146.70.61.131 // SSL Fails
82.147.84.0/23 // SSL Fails
193.107.93.0/24 // SSL Fails
193.107.92.0/24 // SSL Fails
92.255.57.73 // SSL Fails
141.98.101.133 // SSL Fails
217.151.98.163 // SSL Fails
217.138.195.19 // SSL Fails
184.75.223.235 // SSL Fails
64.42.179.43 // SSL Fails
109.206.236.7 // SSL Fails
193.107.93.234 // SSL Fails
109.206.236.14 // SSL Fails
146.185.239.72 // Russian IP - login failed
147.45.47.204 // Russian IP - login failed
147.45.47.218 // Russian IP - ssl failed
87.121.86.36 // Credential Stuffing
8.34.210.52 // Web Exploits
8.34.210.54 // Web Exploits
83.222.191.146 // Web Exploits
80.64.30.169 // Brute Force
185.147.124.171 // failure audit: an account failed to log on
34.19.127.197 // Web Exploits
199.195.248.205 // Web Exploits
92.114.59.139 // Web Exploits
66.240.236.109 // Scanning IP
34.19.116.52 // attempt exploits
189.44.61.166 // network connection detected
218.207.25.249 // Web Exploits
92.63.197.55 // failure audit: an account failed to log on
185.156.73.24 // failure audit: an account failed to log on
185.156.73.69 // failure audit: an account failed to log on
139.5.1.255 // Web Exploits
92.63.197.69 // failure audit: an account failed to log on
91.224.92.18 // Web Exploits
34.68.34.80 // attempt exploits
45.190.253.64 // TCP Flooding
85.237.57.200 // Brute Force
31.13.224.63 // SSL Fails
95.153.241.43 // Brute Force
5.32.177.24 // Brute Force
147.235.97.158 // Brute Force
95.79.108.51 // Brute Force
187.237.47.214 // Brute Force
200.35.54.73 // Brute Force
216.194.174.27 // Brute Force
50.74.136.134 // Brute Force
213.136.80.106 // web Exploits
170.84.185.228 // web Exploits
216.10.250.218 // web Exploits
38.222.120.173 // web Exploits
190.104.199.167 // web Exploits
104.207.45.180 // web Exploits
128.14.216.246 // web Exploits
212.96.69.182 // web Exploits
94.21.161.91 // web Exploits
84.54.71.165 // web Exploits
156.228.97.76 // web Exploits
186.90.88.115 // web Exploits
156.228.171.211 // web Exploits
45.160.89.118 // web Exploits
154.213.203.5 // web Exploits
185.147.124.177 // failure audit: an account failed to log on
85.159.208.197 // Prob Port 179
156.228.80.218 // Brute Force
156.228.91.9 // Brute Force
156.228.84.22 // Brute Force
104.207.48.8 // SSL Fails
104.207.59.195 // SSL Fails
112.98.179.132 // Brute Force
64.52.80.94 // Hosting Meduza Stealer Panel
194.59.30.192 // Hosting Meduza Stealer Panel
147.45.44.216 // Hosting Meduza Stealer Panel
31.192.232.119 // Hosting Fake Agreement
172.86.109.138 // SSL Fails
172.86.110.3 // SSL Fails
50.114.94.51 // SSL Fails
193.56.116.57 // SSL Fails
64.64.116.8 // SSL Fails
91.193.232.79 // SSL Fails
185.238.231.163 // SSL Fails
104.234.225.5 // SSL Fails
216.73.160.119 // SSL Fails
199.101.192.82 // SSL Fails
167.88.169.34 // SSL Fails
172.86.109.203 // SSL Fails
172.86.109.194 // SSL Fails
216.21.13.15 // DGA - lyoztkhgdpwycx[.]com
216.21.13.14 // DGA - lyoztkhgdpwycx[.]com
156.233.72.26 // network connection detected
45.169.173.81 // network connection detected
151.217.62.23 // Web Exploits
34.19.116.56 // Web Exploits
34.19.127.178 // Web Exploits
142.44.160.96 // Web Exploits
172.86.106.90 // Brute Force
38.180.60.188 // Brute Force
172.86.106.175 // Brute Force
172.86.110.109 // Brute Force
38.180.6.254 // Brute Force
38.180.138.179 // Brute Force
172.86.108.71 // Brute Force
172.86.111.178 // Brute Force
172.86.111.136 // Brute Force
132.226.229.76 // Credential Stuffing
34.19.127.209 // attempt exploits
8.34.210.33 // Attempting log4j - dropped
8.34.210.37 // Web Exploits
210.12.68.242 // Scanning IP
47.251.74.11 // Web Exploits
34.68.34.70 // attempt exploits
34.68.34.93 // attempting Nmap scan - dropped
8.34.210.40 // attempting nmap scan - dropped
193.107.92.22 // Brute Force
34.19.116.50 // Web Exploits
34.19.127.187 // Web Exploits
45.227.254.94 // SSL Brute Force
193.41.206.24 // Scanning
172.86.115.74 // SSL Brute Force
172.86.113.173 // SSL Brute Force
207.244.225.208 // Web Exploits
23.188.88.0/27 // SSL Brute Force
192.147.125.0/25 // SSL Brute Force
104.254.90.251 // Brute Force
162.219.176.3 // Brute Force
87.101.92.171 // Brute Force
185.147.124.0/24 // SSL Brute Force
45.141.87.175 // SSL Brute Force
141.98.102.235 // Brute Force
141.98.102.243 // Brute Force
68.235.52.68 // Brute Force
184.75.221.3 // Brute Force
68.235.35.124 // Brute Force
195.54.170.249 // Brute Force
188.116.20.238 // Brute Force
45.141.87.137 // Brute Force
178.162.204.214 // Brute Force
46.8.238.44 // Brute Force
217.144.191.85 // Brute Force
109.206.236.38 // Brute Force
184.75.223.211 // Brute Force
194.116.215.249 // Brute Force
23.188.88.26 // Brute Force
31.59.185.247 // Brute Force
34.68.34.67 // Scanning IP
171.244.40.20 // Web Exploits
5.181.86.212 // Credential Stuffing
193.3.19.202 // Brute Force
185.147.124.107 // Brute Force
62.102.148.185 // SSL Fails
82.147.85.44 // SSL Fails
45.130.86.11 // SSL Fails
104.254.90.187 // SSL Fails
79.142.76.244 // SSL Fails
184.75.223.219 // SSL Fails
188.116.40.24 // SSL Fails
178.255.222.194 // VPN Attempts
46.8.230.4 // SSL Fails
31.15.16.152 // SSL Fails
184.75.221.107 // SSL Fails
205.204.87.47 // SSL Fails
176.97.74.27 // SSL Fails
193.187.173.130 // SSL Fails
185.170.104.53 // SSL Fails
82.147.84.220 // SSL Fails
109.206.236.47 // SSL Fails
31.15.16.244 // VPN Attempts
46.8.64.65 // VPN Attempts
31.15.16.95 // VPN Attempts
82.147.84.140 // SSL Fails
139.28.218.235 // SSL Fails
184.75.221.203 // SSL Fails
213.152.161.149 // SSL Fails
37.1.192.67 // SSL Fails
217.212.240.66 // SSL Fails
38.180.23.121 // SSL Fails
213.152.162.154 // VPN Attempts
213.152.162.104 // SSL Fails
178.238.229.54 // SSL Fails
130.0.232.141 // SSL Fails
176.97.72.120 // SSL Fails
80.209.239.42 // VPN Attempts
45.141.87.169 // SSL Fails
176.97.77.167 // SSL Fails
82.102.27.171 // SSL Fails
134.19.179.163 // SSL Fails
199.189.27.123 // SSL Fails
31.58.141.84 // SSL Fails
204.8.98.95 // VPN Attempts
176.97.65.13 // VPN Attempts
103.108.95.138 // VPN Attempts
38.180.21.20 // VPN Attempts
147.135.112.230 // VPN Attempts
146.70.76.35 // VPN Attempts
204.8.98.45 // VPN Attempts
193.37.252.67 // VPN Attempts
173.249.217.7 // VPN Attempts
204.8.98.25 // VPN Attempts
103.231.88.202 // SSL Fails
103.231.89.218 // VPN Attempts
204.8.98.105 // VPN Attempts
193.37.252.51 // VPN Attempts
204.8.98.15 // VPN Attempts
64.42.179.59 // VPN Attempts
194.132.123.4 // VPN Attempts
204.8.98.35 // VPN Attempts
37.1.208.113 // VPN Attempts
198.54.129.44 // VPN Attempts
198.44.134.4 // VPN Attempts
217.138.222.66 // SSL Fails
23.248.169.6 // SSL Fails
198.44.133.117 // SSL Fails
45.141.87.143 // SSL Fails
193.37.252.163 // SSL Fails
204.8.98.85 // SSL Fails
198.44.133.101 // SSL Fails
204.8.98.55 // SSL Fails
68.235.52.36 // SSL Fails
198.54.128.124 // SSL Fails
143.244.63.95 // SSL Fails
143.110.177.84 // SSL Fails
173.249.217.23 // SSL Fails
198.44.136.252 // SSL Fails
198.54.129.52 // SSL Fails
178.162.194.17 // SSL Fails
185.156.175.171 // SSL Fails
193.187.91.18 // SSL Fails
193.37.252.115 // SSL Fails
198.44.133.133 // SSL Fails
68.235.48.108 // SSL Fails
198.54.129.60 // SSL Fails
109.248.148.246 // SSL Fails
23.130.104.130 // SSL Fails
31.57.243.7 // Web Exploits
101.66.172.251 // Web Exploits
85.10.56.126 // SSL VPN Attempts
176.97.68.79 // SSL VPN Attempts
194.99.104.35 // SSL Fails
77.221.134.5 // SSL Fails
46.183.218.150 // SSL Fails
45.141.87.134 // SSL Fails
46.8.227.55 // SSL Fails
45.141.87.218 // VPN Attempts
109.206.236.56 // SSL Fails
217.145.79.251 // SSL Fails
37.77.56.246 // SSL Fails
185.255.47.190 // Brute Force
195.222.57.190 // Brute Force
2.57.219.2 // Brute Force
95.174.99.133 // Brute Force
167.99.43.24 // Web Exploits
170.130.55.170 // Credential Stuffing
172.86.109.169 // Credential Stuffing
208.115.218.90 // Credential Stuffing
103.35.191.8 // Credential Stuffing
185.7.214.89 // failure audit: an account failed to log on
94.103.125.203 // Brute Force
185.7.214.87 // failure audit: an account failed to log on
93.123.109.182 // Brute Force
31.13.224.207 // Brute Force
31.13.224.42 // Brute Force
45.149.241.109 // Brute Force
31.13.224.202 // Brute Force
31.13.224.210 // Brute Force
31.13.224.169 // Brute Force
31.13.224.205 // Brute Force
31.13.224.232 // VPN attempts
185.7.214.81 // failure audit: an account failed to log on
91.238.181.40 // failure audit: an account failed to log on
65.49.1.67 // Scanning IP
154.212.141.195 // network connection detected
178.72.71.140 // Web Exploits
202.95.12.147 // Web Exploits
34.68.34.90 // attempt log4j
8.34.210.38 // attempt Log4j
202.112.237.201 // Malicious Scanning
34.68.34.73 // Web Exploits
34.68.34.83 // Web Exploits
34.68.34.76 // Web Exploits
61.3.108.0 // attempting RCE
31.173.66.222 // Brute Force
92.127.176.103 // Brute Force
186.239.134.158 // Scanning IP
92.255.85.253 // Scanning IP
203.55.131.3 // Scanning IP
65.49.1.78 // scanning IP
142.251.2.27 // Testing the Blacklist
173.194.202.27 // Testing the Blacklist
142.251.10.27 // Testing the Blacklist
185.156.73.62 // failure audit: an account failed to log on
185.156.73.59 // failure audit: an account failed to log on
92.63.197.62 // failure audit: an account failed to log on
92.63.197.59 // failure audit: an account failed to log on
157.20.228.4 // Web Exploits
8.222.140.84 // Web Exploits
47.237.94.12 // Web Exploits
8.222.226.153 // Web Exploits
8.222.128.126 // Web Exploits
38.46.220.87 // Scanning
8.34.210.47 // Scanning IP
34.68.34.74 // Scanning IP
68.183.15.116 // Scanning
78.128.112.218 // Magecart Hosting
139.45.197.253 // Newly Parked Domains - Activity
139.45.197.228 // Newly Parked Domains - Activity
92.249.48.201 // Scanning
141.98.11.35 // Scanning
223.71.167.171 // Scanning IP
34.68.34.84 // JNDI
37.156.216.153 // Brute Force
92.119.178.3 // Brute Force
198.54.134.252 // Brute Force
156.96.151.132 // Brute Force
193.37.252.99 // Brute Force
34.68.34.78 // Scanning IP
60.166.61.48 // Web Exploits
156.238.100.131 // Web Exploits
130.61.224.147 // Web Exploits
185.190.24.53 // Brute Force
93.190.141.252 // Scanning
154.213.184.23 // Malicious Scanning
223.149.50.239 // Web Exploits
34.68.34.94 // Web Exploits
197.255.204.218 // Brute Force
93.182.161.113 // Brute Force
93.182.161.125 // Brute Force
93.182.161.109 // Brute Force
50.208.119.170 // Brute Force
62.76.95.152 // Brute Force
187.93.153.166 // Brute Force
202.99.233.151 // Brute Force
60.12.48.38 // Brute Force
60.31.181.52 // Brute Force
34.68.34.72 // Scanning IP
8.34.210.48 // Scanning IP
45.149.241.68 // Brute Force
178.215.224.18 // Brute Force
85.31.47.193 // Brute Force
94.156.166.66 // Brute Force
45.149.241.65 // Brute Force
64.62.156.92 // Scanning IP
45.148.10.206 // Scanning
93.123.109.13 // Credential Stuffing
93.123.109.9 // Credential Stuffing
93.123.109.8 // Credential Stuffing
64.226.86.7 // Scanning IP
204.188.228.142 // Scanning
146.190.80.45 // Scanning
94.232.47.183 // Brute force
94.103.125.200 // Brute force
94.103.125.198 // Brute force
94.103.125.201 // Brute force
94.103.125.202 // Brute force
94.103.125.199 // Brute force
135.181.63.70 // malware
185.7.214.126 // Credential Stuffing
185.7.214.124 // Credential Stuffing
128.1.57.69 // Scanning IP
88.214.25.117 // failure audit: an account failed to log on
47.236.200.126 // Scanning
204.188.228.55 // Scanning
178.128.108.136 // Scanning
201.131.126.16 // Scanning
143.198.215.140 // Scanning
161.35.223.243 // Scanning
103.122.163.182 // Credential Stuffing
165.232.54.174 // Scanning
78.153.140.177 // Scanning
45.43.33.218 // Scanning
77.221.146.0/24 // Credential Stuffing
88.214.25.248 // Credential Stuffing
154.205.159.178 // Web Exploits
64.227.171.183 // Scanning
157.230.111.75 // Scanning
199.127.60.228 // Scanning
72.46.130.218 // Scanning IP
165.227.207.54 // Scanning
159.65.144.118 // Web Exploits
44.220.185.47 // Web Exploits
147.45.112.107 // failure audit: an account failed to log on
147.45.112.108 // failure audit: an account failed to log on
147.45.112.103 // failure audit: an account failed to log on
147.45.112.104 // failure audit: an account failed to log on
147.45.112.105 // failure audit: an account failed to log on
185.234.216.0/24 // Credential Stuffing
92.255.85.49 // Credential Stuffing
45.128.52.61 // Credential Stuffing
186.250.29.18 // Credential Stuffing
92.255.85.48 // Credential Stuffing
147.45.112.106 // failure audit: an account failed to log on
106.51.226.240 // Credential Stuffing
45.130.145.0/24 // Credential Stuffing
185.122.204.186 // Credential Stuffing
80.64.30.87 // Credential Stuffing
200.61.208.226 // Credential Stuffing
147.45.112.110 // failure audit: an account failed to log on
23.26.218.6 // Credential Stuffing
185.238.231.217 // Credential Stuffing
136.144.19.197 // Credential Stuffing
92.255.57.58 // Web Exploits
42.236.85.79 // Scanning
31.220.1.88 // Scanning
78.46.194.43 // Hosting Hellcat Ransomware
65.49.1.33 // Scanning IP
94.103.125.194 // Hacking attempts into Global Protect
92.255.85.41 // VPN Attempts
94.103.125.192 // brute force attempts
94.103.125.191 // brute force attempts
94.103.125.195 // brute force attempts
64.62.156.15 // Scanning IP
115.231.78.11 // Attempts Port 4567
35.216.148.67 // Scanning
103.197.112.186 // Web Exploits
159.89.160.70 // Scanning
88.214.25.114 // failure audit: an account failed to log on
88.214.25.113 // failure audit: an account failed to log on
146.70.165.46 // Credential Stuffing
79.127.217.58 // Credential Stuffing
159.203.13.59 // Scanning
178.128.32.203 // Scanning
85.203.15.104 // Scanning
68.183.202.121 // Scanning
194.165.16.27 // failure audit: an account failed to log on
147.45.112.100 // failure audit: an account failed to log on
88.214.25.112 // failure audit: an account failed to log on
91.238.181.39 // failure audit: an account failed to log on
108.165.243.61 // Credential Stuffing
161.35.149.81 // Scanning
212.47.70.69 // Scanning
70.39.75.166 // Scanning
147.45.112.102 // failure audit: an account failed to log on
162.243.201.34 // Scanning
91.193.232.62 // Credential Stuffing
141.98.11.79 // Malicious Scanning
144.126.223.51 // Scanning
93.123.109.11 // Credential Stuffing
196.190.118.132 // Scanning IP
93.123.109.10 // Credential Stuffing
181.237.30.168 // Brute Force
45.145.116.201 // Brute Force
196.64.16.138 // Scanning
45.83.130.82 // VPN Attempts
45.83.21.37 // VPN Attempts
185.153.181.230 // VPN Attempts
64.227.186.248 // Web Exploits
142.93.1.91 // Web Exploits
103.125.189.18 // Web Exploits
134.209.25.199 // Web Exploits
103.147.184.29 // Web Exploits
195.26.253.72 // Web Exploits
95.164.62.127 // Vidar C2 Panel
5.10.250.35 // Brute Force
91.241.150.246 // Scanning IP
45.145.119.225 // Credential Stuffing
165.227.30.202 // Scanning
128.14.129.10 // Scanning
157.230.150.172 // Scanning
188.166.186.224 // Scanning
117.186.238.82 // Web Exploits
185.147.124.105 // failure audit: an account failed to log on
45.205.147.60 // malicious scanning
80.242.208.68 // Scanning
91.194.11.115 // Scanning
196.64.2.238 // Scanning
138.197.157.93 // Scanning
103.134.152.2 // Credential Stuffing
80.94.93.246 // Web Exploits
159.203.87.13 // Web Exploits
117.209.90.217 // Web Exploits
39.108.101.130 // Malicious Scanning
87.120.113.3 // Scanning IP
185.82.219.179 // ENV File Scanning Attempt
194.165.16.26 // failure audit: an account failed to log on
222.189.163.82 // Exchange probing
62.173.140.238 // network connection detected
45.137.22.45 // network connection detected
157.230.245.252 // Secrets Digging (.env)
18.236.71.93 // Suspicious EC2 Traffic