109.160.32.151

Attacks by type

Incidents by severity: High 1, Medium 3, Low 1

Incidents

These incidents come from 3 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 1HighAI verdict: malicious1 hitNov 11, 2026, 10:56 PM UTC
• sshdServer 1MediumAI verdict: malicious1 hitNov 11, 2026, 9:56 PM UTC
• sshdServer 2MediumAI verdict: malicious1 hitOct 31, 2026, 4:14 AM UTC

  Recidivist SSH brute-force from 109.160.32.151 (2 prior bans in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail and drew a 14400s ban; the repeat offender and related [addr]/24 sources in past incidents suggest persistent, likely automated attacks targeting this host rather than one-off noise.

• sshdServer 3LowAI verdict: malicious1 hitOct 15, 2026, 2:06 PM UTC

  109.160.32.151 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (3 earlier bans in the recidive window) and was banned for 28800s; it matches recent incidents from other [addr]/24 hosts, which points to persistent automated brute-force from one subnet, not a targeted compromise.

• sshdServer 2MediumAI verdict: malicious1 hitOct 13, 2026, 4:39 AM UTC

  Recidivist SSH brute-force from 109.160.32.151 (1 prior ban in the recidive window) matched shieldie-guard's 'sshd' jail and drew a 7200s ban. Prior incidents from [path] suggest a persistent campaign from the [addr]/24 range rather than random noise.

Timeline

1. Nov 11, 2026, 10:58 PM UTCLast reported
2. Nov 11, 2026, 10:56 PM UTCsshd High
3. Nov 11, 2026, 9:56 PM UTCsshd Medium
4. Oct 31, 2026, 4:14 AM UTCsshd Medium
5. Oct 15, 2026, 2:06 PM UTCsshd Low
6. Oct 13, 2026, 4:39 AM UTCsshd Medium
7. Oct 3, 2026, 1:14 AM UTCFirst reported