Log in to view charts and search reports for this IP.
Log In
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 140.245.9.4:
This IP address has been reported a total of
13
times from
8 distinct
sources.
140.245.9.4 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Singapore
with 3
reports;
Canada
with 2
reports;
Hong Kong
with 2
reports.
The most common categories in these recent reports were:
Port Scan
9
times;
Brute-Force
5
times;
Open Proxy
3
times;
Hacking
3
times;
SSH
1
time;
Other
2
times.
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.
Unsolicited TCP connection from 140.245.9.4 to port 0 at 2026-09-05T20:40:18Z. Source IP completed t ...
show moreUnsolicited TCP connection from 140.245.9.4 to port 0 at 2026-09-05T20:40:18Z. Source IP completed three-way handshake to non-public service on this host. Detected by automated intrusion monitoring.
show less
[20:32] Attempted to relay through an open SOCKS5 proxy (CONNECT to api.ipify.org:443), authenticati ...
show more[20:32] Attempted to relay through an open SOCKS5 proxy (CONNECT to api.ipify.org:443), authenticating as 111333:1****3
show less
Unsolicited TCP connection from 140.245.9.4 to port 0 at 2026-08-23T13:05:00Z. Source IP completed t ...
show moreUnsolicited TCP connection from 140.245.9.4 to port 0 at 2026-08-23T13:05:00Z. Source IP completed three-way handshake to non-public service on this host. Detected by automated intrusion monitoring.
show less
Port Scan
Hacking
Anonymous
15502/tcp,15490/tcp,15492/tcp,15491/tcp,15493/tcp,15494/tcp,15497/tcp,15498/tcp,15499/tcp,15495/tcp, ...
show more15502/tcp,15490/tcp,15492/tcp,15491/tcp,15493/tcp,15494/tcp,15497/tcp,15498/tcp,15499/tcp,15495/tcp,15496/tcp,15500/tcp,15501/tcp (13 or more attempts)
show less
[10:15] Attempted to relay through an open SOCKS5 proxy (CONNECT to api.ipify.org:443), authenticati ...
show more[10:15] Attempted to relay through an open SOCKS5 proxy (CONNECT to api.ipify.org:443), authenticating as 868:8*8
show less
Open Proxy
Port Scan
Anonymous
9460/tcp,9456/tcp,9443/tcp,9444/tcp,9447/tcp,9448/tcp (6 or more attempts)
[18:27] Attempted to relay through an open SOCKS5 proxy (CONNECT to api.ipify.org:443), authenticati ...
show more[18:27] Attempted to relay through an open SOCKS5 proxy (CONNECT to api.ipify.org:443), authenticating as 5272:5**2
show less
Aug 15 18:03:13 srv-ubuntu-dev3 sshd[2510973]: Failed password for invalid user azureuser from 140.2 ...
show moreAug 15 18:03:13 srv-ubuntu-dev3 sshd[2510973]: Failed password for invalid user azureuser from 140.245.9.4 port 61076 ssh2
Aug 15 18:03:15 srv-ubuntu-dev3 sshd[2510973]: Connection closed by invalid user azureuser 140.245.9.4 port 61076 [preauth]
Aug 15 18:08:35 srv-ubuntu-dev3 sshd[2511788]: Invalid user azureuser from 140.245.9.4 port 51069
Aug 15 18:08:35 srv-ubuntu-dev3 sshd[2511788]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.245.9.4
Aug 15 18:08:37 srv-ubuntu-dev3 sshd[2511788]: Failed password for invalid user azureuser from 140.245.9.4 port 51069 ssh2
...
show less
