This IP address has been reported a total of
13
times from
13 distinct
sources.
80.5.5.130 was first reported on
, and the most recent report was
.
Recent Reports:
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
[Press84-BanHammer] bad username — Sourced from: www.langsvlaamsewegen.be — Request: POST /wp-login. ...
show more[Press84-BanHammer] bad username — Sourced from: www.langsvlaamsewegen.be — Request: POST /wp-login.php
show less
Asking over plain http and never following the redirect served — a crawler that reads nothing it ask ...
show moreAsking over plain http and never following the redirect served — a crawler that reads nothing it asks for | method: GET | path: /wp-login.php | 2026-09-16 17:14 UTC
show less
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Sa ...
show moreMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0
show less
Botnet UDP flood (DDoS) against a hosted game server at 185.143.177.x:6666/udp in AS203136 (LLC Ordu ...
show moreBotnet UDP flood (DDoS) against a hosted game server at 185.143.177.x:6666/udp in AS203136 (LLC Ordunet), Georgia, on 2026-09-11 between 01:00 and 02:30 local time (+04:00). This source sustained more than 800 packets/sec toward a single UDP port, against about 200 packets/sec for a legitimate player of that server. It was one of 1958 sources in 956 networks and 110 countries in the same wave, 500 of which flooded udp/47472 where no service listens at all. Detected on a MikroTik RouterOS router in the raw/prerouting chain (dst-limit 800,200,src-address/10s); the timestamp is when this source crossed the threshold. Not a scan and not brute force - a packet flood, so the host is most likely compromised. Evidence: [email protected].
show less
Client failed challenge verification, marked as suspicious. HTTP request received over TCP on applic ...
show moreClient failed challenge verification, marked as suspicious. HTTP request received over TCP on application ports 80/443. Observed 2026-09-09T07:17:15Z.
show less
UDP flood (DDoS) vs AS215599: 272 pkts / 0.39 MB to UDP 8443 across 151 dst IP(s), 2026-08-19 21:46 ...
show moreUDP flood (DDoS) vs AS215599: 272 pkts / 0.39 MB to UDP 8443 across 151 dst IP(s), 2026-08-19 21:46 to 2026-08-20 00:36 CEST. No legitimate service on these UDP ports (7-day baseline 0 GB/day). Carpet-bombing of a /24, likely botnet-compromised host. Evidence: sFlow + hardware ACL counters.
show less
UDP flood (DDoS) vs AS215599: 272 pkts / 0.39 MB to UDP 8443 across 151 dst IP(s), 2026-08-19 21:46 ...
show moreUDP flood (DDoS) vs AS215599: 272 pkts / 0.39 MB to UDP 8443 across 151 dst IP(s), 2026-08-19 21:46 to 2026-08-20 00:36 CEST. No legitimate service on these UDP ports (7-day baseline 0 GB/day). Carpet-bombing of a /24, likely botnet-compromised host. Evidence: sFlow + hardware ACL counters.
show less