This IP address has been reported a total of
36
times from
9 distinct
sources.
161.132.168.114 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.
Real-time Intercept: SQL attack. Reference: 2026-06-27 08:24:06.03 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-27 08:24:06.03 Logon Login failed for user 'sa'. [161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-27 06:43:33.58 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-27 06:43:33.58 Logon Login failed for user 'sa'. [161.132.168.114]
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: 161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-26 01:29:59.76 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-26 01:29:59.76 Logon Login failed for user 'sa'. [161.132.168.114]
show less
Rule : MSSQLSERVER
Rule: MSSQLSERVER
Event: MSSQLSERVER
sa Reason: Password did not match that fo ...
show moreRule : MSSQLSERVER
Rule: MSSQLSERVER
Event: MSSQLSERVER
sa Reason: Password did not match that for the login provided. [CLIENT: 161.132.168.114]
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: 161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-24 08:16:21.79 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-24 08:16:21.79 Logon Login failed for user 'sa'. [161.132.168.114]
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: 161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-23 12:03:41.17 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-23 12:03:41.17 Logon Login failed for user 'sa'. [161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-23 03:00:54.12 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-23 03:00:54.12 Logon Login failed for user 'sa'. [161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-22 13:01:45.88 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-22 13:01:45.88 Logon Login failed for user 'sa'. [161.132.168.114]
show less
Real-time Intercept: SQL attack. Reference: 2026-06-22 12:13:12.26 Logon Login failed for user 's ...
show moreReal-time Intercept: SQL attack. Reference: 2026-06-22 12:13:12.26 Logon Login failed for user 'sa'. [161.132.168.114]
show less
Brute-Force
Showing 1 to
15
of 36 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩