User SKunz-Sec joined AbuseIPDB in October 2023 and has reported 460 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 69.4.234.116 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.118 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.119 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.120 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.121 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.122 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.124 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 69.4.234.125 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 87.249.134.2 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 87.249.134.15 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 87.249.134.28 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 96.44.189.99 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 96.44.191.131 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 104.129.24.99 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 104.129.24.115 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 104.129.41.195 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 104.223.118.35 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 107.150.22.3 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 142.147.89.211 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 142.147.89.226 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 143.244.47.66 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 146.70.172.3 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 146.70.173.3 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 146.70.173.67 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force | |
| 🇺🇸 146.70.173.131 |
IP attempting Brute-Force the following critical firewall event was detected: SSL VPN login fail
|
Brute-Force |