This IP address has been reported a total of
29
times from
11 distinct
sources.
59.92.234.13 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.
Rule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. ...
show moreRule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. [CLIENT: 59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-28 07:01:47.73 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-28 07:01:47.73 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Rule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. ...
show moreRule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. [CLIENT: 59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-27 07:35:10.34 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-27 07:35:10.34 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-26 16:58:44.99 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-26 16:58:44.99 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-26 04:42:57.35 Logon Login failed for user 'a ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-26 04:42:57.35 Logon Login failed for user 'administrator'. Reason: Could not find a login matching the name provided. [59.92.234.13]
show less
Rule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. ...
show moreRule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. [CLIENT: 59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-25 08:19:49.14 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-25 08:19:49.14 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-23 21:44:01.48 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-23 21:44:01.48 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-23 07:52:38.29 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-23 07:52:38.29 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-22 18:03:41.53 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-22 18:03:41.53 Logon Login failed for user 'sa'. [59.92.234.13]
show less
Rule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. ...
show moreRule : MSSQLSERVER
UserAccount : sa
sa Reason: Password did not match that for the login provided. [CLIENT: 59.92.234.13]
show less
Rule : MSSQLSERVER
Rule: MSSQLSERVER
Event: MSSQLSERVER
UserAccount: sa
sa Reason: Password did ...
show moreRule : MSSQLSERVER
Rule: MSSQLSERVER
Event: MSSQLSERVER
UserAccount: sa
sa Reason: Password did not match that for the login provided. [CLIENT: 59.92.234.13]
show less
Port Scan
Brute-Force
Showing 1 to
15
of 29 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩