109.160.32.179

Attacks by type

Incidents by severity: Medium 2, Low 5

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 1LowAI verdict: malicious1 hitNov 5, 2026, 1:56 AM UTC

  109.160.32.179 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (4 earlier bans in the recidive window), part of a recurring pattern from the [addr]/24 range consistent with persistent automated brute-force noise rather than a targeted attack; shieldie-guard applied a 57600s ban.

• sshdServer 1LowAI verdict: malicious1 hitNov 4, 2026, 11:45 AM UTC

  same as 16e587c9: [addr] re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (3 earlier bans in recidive window) and received a 28800s ban; it matches the ongoing pattern from the same [addr]/24 range seen 2026-11-01 and 2026-11-03, which points to persistent automated brute-force rather than a targeted attack.

• sshdServer 2MediumAI verdict: malicious1 hitNov 3, 2026, 3:45 AM UTC

  Recidivist SSH brute-force from 109.160.32.179 (1 prior ban in the recidive window) matched shieldie-guard's 'sshd' jail, which applied a 7200s firewall ban; same [addr]/24 range as recent incidents (.114, .145) suggests a coordinated campaign from one netblock rather than random noise.

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

  109.160.32.179 re-tripped shieldie-guard's sshd jail for the 4th time in the recidive window and received an escalated 28800s ban; this matches persistent automated brute-force from the [addr]/24 range (also seen from .32 and .141) rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 16, 2026, 9:41 AM UTC

  109.160.32.179 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (2 earlier bans in the recidive window) and received a 14400s ban; it matches recurring opportunistic brute-force from the same [addr]/24 range seen in prior incidents, not evidence of a targeted attack.

• sshdServer 2MediumAI verdict: malicious1 hitOct 16, 2026, 12:29 AM UTC

  Recidivist SSH brute-force from 109.160.32.179 (2 prior bans in the recidive window) is now held by shieldie-guard's 14400s 'sshd' jail ban. Earlier incidents show other hosts in the same [addr]/24 doing the same thing, which points to coordinated persistent scanning rather than random noise, but there is no evidence of a successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 13, 2026, 4:00 AM UTC

  109.160.32.179 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (1 earlier ban in the recidive window) and received a 7200s ban; it fits a recurring pattern from the same [addr]/24 range (.166, .128, .152), indicating persistent automated brute-force rather than a targeted attack.

Timeline

1. Nov 5, 2026, 2:01 AM UTCLast reported
2. Nov 5, 2026, 1:56 AM UTCsshd Low
3. Nov 4, 2026, 11:45 AM UTCsshd Low
4. Nov 3, 2026, 3:45 AM UTCsshd Medium
5. Oct 18, 2026, 2:35 PM UTCsshd Low
6. Oct 16, 2026, 9:41 AM UTCsshd Low
7. Oct 16, 2026, 12:29 AM UTCsshd Medium
8. Oct 13, 2026, 4:00 AM UTCsshd Low
9. Sep 27, 2026, 10:01 PM UTCFirst reported