115.160.76.23

Attacks by type

Incidents by severity: Critical 2, Low 18

Incidents

These incidents come from 2 different servers. Each describes only its own history with this address, so a first ban on one can be a repeat ban on another.

• sshdServer 1CriticalAI verdict: malicious1 hitNov 11, 2026, 5:38 PM UTC
• sshdServer 2CriticalAI verdict: malicious5 hitsNov 11, 2026, 11:49 AM UTC
• sshdServer 1LowAI verdict: malicious1 hitOct 31, 2026, 5:16 PM UTC

  Persistent repeat offender 115.160.76.23 tripped shieldie-guard's sshd jail again (8 prior bans in recidive window, refused attempts included) and received an escalated 921600s firewall ban; consistent with automated SSH brute-force noise rather than a targeted attack, already contained.

• sshdServer 2LowAI verdict: malicious5 hitsOct 31, 2026, 11:24 AM UTC

  Recidivist opportunistic SSH credential guessing from 115.160.76.23 (9th ban, 8 earlier in recidive window) re-tripped shieldie-guard's sshd jail, which applied a 921600s firewall ban; persistent but untargeted noise consistent with prior verdicts.

• sshdServer 1LowAI verdict: malicious1 hitOct 25, 2026, 7:15 PM UTC

  Persistent repeat offender 115.160.76.23 tripped shieldie-guard's sshd jail again (7 prior bans in recidive window, refused attempts included) and received an escalated 460800s firewall ban; pattern is consistent with automated brute-force noise rather than a targeted attack, and no evidence of successful authentication.

• sshdServer 2LowAI verdict: malicious1 hitOct 25, 2026, 1:25 PM UTC

  Recidivist opportunistic SSH credential guessing from 115.160.76.23 (8th ban, 7 earlier in recidive window) re-tripped shieldie-guard's sshd jail, which applied a 460800s firewall ban; persistent but consistent with automated noise, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 22, 2026, 9:46 AM UTC

  Persistent repeat offender 115.160.76.23 tripped shieldie-guard's sshd jail again (6 prior bans in recidive window, refused attempts included) and received an escalated 230400s firewall ban; pattern is consistent with automated brute-force noise rather than a targeted attack, with no evidence of successful authentication.

• sshdServer 2LowAI verdict: malicious1 hitOct 22, 2026, 4:00 AM UTC

  Persistent opportunistic SSH credential guessing from recidivist 115.160.76.23 (7th ban, 6 earlier in recidive window) re-tripped shieldie-guard's sshd jail, which applied a 230400s firewall ban; consistent with prior noise-level verdicts, no sign of successful auth or targeting.

• sshdServer 1LowAI verdict: malicious1 hitOct 20, 2026, 5:32 PM UTC

  Persistent repeat offender 115.160.76.23 tripped shieldie-guard's sshd jail again (5 prior bans in recidive window, refused attempts included) and received an escalated 115200s firewall ban; the pattern looks like persistent automated SSH brute-force rather than a targeted attack, and the evidence shows no successful logins.

• sshdServer 2LowAI verdict: malicious1 hitOct 20, 2026, 11:47 AM UTC

  Recidivist opportunistic SSH credential guessing from 115.160.76.23 (6th ban, 5 earlier in recidive window) re-tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban; the pattern is persistent but consistent with automated noise rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 19, 2026, 9:28 PM UTC

  Persistent repeat offender 115.160.76.23 tripped shieldie-guard's sshd jail again (4 prior bans in recidive window, refused attempts included) and received an escalated 57600s ban. This pattern looks like persistent automated SSH brute-force noise, not a targeted compromise.

• sshdServer 2LowAI verdict: malicious1 hitOct 19, 2026, 3:43 PM UTC

  Recidivist opportunistic SSH credential guessing from 115.160.76.23 (5th ban, 4 earlier in recidive window) re-tripped shieldie-guard's sshd jail, which applied an escalated 57600s firewall ban; persistent but untargeted noise consistent with prior verdicts.

• sshdServer 1LowAI verdict: malicious1 hitOct 19, 2026, 1:23 AM UTC

  Fourth consecutive daily sshd jail hit from persistent repeat offender 115.160.76.23 (3 prior bans in recidive window, refused attempts included); shieldie-guard escalated to a 28800s ban — persistent automated brute-force consistent with prior verdicts, no evidence of successful auth or targeting.

• sshdServer 2LowAI verdict: malicious1 hitOct 18, 2026, 7:38 PM UTC

  Recidivist opportunistic SSH credential guessing from 115.160.76.23 (4th ban, 3 earlier in recidive window) re-tripped shieldie-guard's sshd jail, which applied an escalated 28800s firewall ban; the pattern matches untargeted scanning, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 18, 2026, 5:17 AM UTC

  Third-time repeat offender 115.160.76.23 again tripped shieldie-guard's sshd jail (2 prior bans in recidive window) and received an escalated 14400s ban; persistent automated SSH brute-force consistent with prior low-severity verdicts, no evidence of successful auth or targeting.

• sshdServer 2LowAI verdict: malicious1 hitOct 17, 2026, 11:32 PM UTC

  Recidivist opportunistic SSH credential guessing from 115.160.76.23 (3rd ban: 2 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied an escalated 14400s firewall ban; the pattern fits persistent automated scanning, with no evidence of a targeted attack or successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 17, 2026, 9:11 AM UTC

  Repeat offender 115.160.76.23 (banned 3600s on 2026-10-16) again tripped shieldie-guard's sshd jail and received an escalated 7200s ban; persistent but consistent with automated SSH brute-force noise rather than a targeted attack, with no evidence of successful auth.

• sshdServer 2LowAI verdict: malicious1 hitOct 17, 2026, 3:25 AM UTC

  Repeat offender 115.160.76.23 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (2nd ban, 1 prior in recidive window incl. refused attempts), and shieldie-guard applied an escalated 7200s firewall ban; the pattern fits opportunistic automated brute-force noise rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 16, 2026, 12:54 PM UTC

  Repeated SSH auth failures from 115.160.76.23 tripped shieldie-guard's sshd jail, which applied a 3600s firewall ban with no prior bans in the recidive window; consistent with opportunistic internet-wide brute-force noise rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 16, 2026, 6:56 AM UTC

  Repeated SSH auth failures from 115.160.76.23 tripped shieldie-guard's sshd jail, which applied a deterministic 3600s firewall ban; this is the address's first ban (recidive 0), consistent with untargeted internet-wide brute-force noise.

Timeline

1. Nov 11, 2026, 5:42 PM UTCLast reported
2. Nov 11, 2026, 5:38 PM UTCsshd Critical
3. Nov 11, 2026, 11:49 AM UTCsshd Critical
4. Oct 31, 2026, 5:16 PM UTCsshd Low
5. Oct 31, 2026, 11:24 AM UTCsshd Low
6. Oct 25, 2026, 7:15 PM UTCsshd Low
7. Oct 25, 2026, 1:25 PM UTCsshd Low
8. Oct 22, 2026, 9:46 AM UTCsshd Low
9. Oct 22, 2026, 4:00 AM UTCsshd Low
10. Oct 20, 2026, 5:32 PM UTCsshd Low
11. Oct 20, 2026, 11:47 AM UTCsshd Low
12. Oct 19, 2026, 9:28 PM UTCsshd Low
13. Oct 19, 2026, 3:43 PM UTCsshd Low
14. Oct 19, 2026, 1:23 AM UTCsshd Low
15. Oct 18, 2026, 7:38 PM UTCsshd Low
16. Oct 18, 2026, 5:17 AM UTCsshd Low
17. Oct 17, 2026, 11:32 PM UTCsshd Low
18. Oct 17, 2026, 9:11 AM UTCsshd Low
19. Oct 17, 2026, 3:25 AM UTCsshd Low
20. Oct 16, 2026, 12:54 PM UTCsshd Low
21. Oct 16, 2026, 7:01 AM UTCFirst reported
22. Oct 16, 2026, 6:56 AM UTCsshd Low