109.160.32.35

Attacks by type

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

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 1CriticalAI verdict: malicious5 hitsNov 11, 2026, 11:07 PM UTC
• sshdServer 2HighAI verdict: malicious1 hitNov 9, 2026, 3:17 PM UTC
• sshdServer 3MediumAI verdict: malicious1 hitNov 7, 2026, 1:53 PM UTC

  Recidivist SSH brute-force from 109.160.32.35 (2 prior bans in the recidive window; also seen in earlier incidents along with neighbor [addr]) was banned for 14400s by shieldie-guard's 'sshd' jail. This looks like persistent automated scanning from one /24, not a host-specific targeted attack.

• sshdServer 3MediumAI verdict: malicious1 hitOct 27, 2026, 6:07 PM UTC

  Recidivist SSH brute-force from 109.160.32.35 (3 prior bans in the recidive window, escalating from earlier incidents) banned for 28800s by shieldie-guard's 'sshd' jail; part of a recurring pattern from the [addr]/24 range. This looks like persistent automated targeting of this host, not random noise.

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

  109.160.32.35 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (3 earlier bans in the recidive window) and received a 28800s firewall ban; the persistent recidivist pattern, consistent with related 109.160.32.x sources, indicates automated brute-force noise rather than a targeted attack.

• sshdServer 3MediumAI verdict: malicious1 hitOct 19, 2026, 2:50 PM UTC

  Recidivist SSH brute-force source 109.160.32.35 (2 prior bans in the recidive window) was banned for 14400s by shieldie-guard's 'sshd' jail; it is the fourth address from [addr]/24 in recent incidents, which points to persistent scanning from one range rather than a single random scanner.

• sshdServer 1LowAI verdict: malicious1 hitOct 17, 2026, 10:02 AM UTC

  109.160.32.35 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (2 earlier bans in the recidive window, refused attempts included) and received a 14400s firewall ban; it is consistent with persistent automated brute-force from the [addr]/24 range seen in prior incidents rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 15, 2026, 12:54 PM UTC

  Repeated SSH auth failures from 109.160.32.35 tripped shieldie-guard's sshd jail (7200s firewall ban, 1 prior ban in the recidive window); it matches recent low-severity incidents from other hosts in the same [addr]/24, which points to persistent automated scanning from one network rather than a targeted attack.

Timeline

1. Nov 11, 2026, 11:09 PM UTCLast reported
2. Nov 11, 2026, 11:07 PM UTCsshd Critical
3. Nov 9, 2026, 3:17 PM UTCsshd High
4. Nov 7, 2026, 1:53 PM UTCsshd Medium
5. Oct 27, 2026, 6:07 PM UTCsshd Medium
6. Oct 20, 2026, 5:26 PM UTCsshd Low
7. Oct 19, 2026, 2:50 PM UTCsshd Medium
8. Oct 17, 2026, 10:02 AM UTCsshd Low
9. Oct 15, 2026, 12:54 PM UTCsshd Low
10. Oct 1, 2026, 12:58 AM UTCFirst reported