195.178.110.227

Attacks by type

Incidents by severity: Medium 2, Low 7

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 1LowAI verdict: malicious1 hitNov 4, 2026, 11:33 PM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.227 (5th ban, 4 earlier in recidive window, from the repeatedly seen [addr]/24 range), contained by shieldie-guard's sshd jail with a 57600s firewall ban; pattern consistent with noise, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 29, 2026, 3:40 PM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.227 (5th ban, 4 earlier in recidive window) from the repeatedly seen [addr]/24 range, contained by shieldie-guard's sshd jail with a 57600s firewall ban; consistent with prior noise-level verdicts, not targeted.

• sshdServer 2LowAI verdict: malicious1 hitOct 28, 2026, 9:31 PM UTC

  Recidivist automated SSH brute-force from 195.178.110.227 (3rd ban, 2 prior in recidive window; same [addr]/24 range as earlier incidents) contained by shieldie-guard's sshd jail with a 14400s firewall ban; no evidence of successful auth, consistent with untargeted noise.

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

  Recidivist opportunistic SSH brute-force from 195.178.110.227 (4th ban, 3 earlier in the recidive window) that shieldie-guard's sshd jail contained with a deterministic 28800s firewall ban; it shows no sign of a targeted attack or a successful login.

• sshdServer 3MediumAI verdict: malicious1 hitOct 28, 2026, 9:31 PM UTC

  Recidivist SSH brute-force from 195.178.110.227 (2 prior bans in the recidive window) again matched shieldie-guard's 'sshd' jail and received a 14400s firewall ban, consistent with the recurring [addr]/24 automated pattern rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 21, 2026, 4:08 AM UTC

  Recidivist SSH brute-force from 195.178.110.227 (third ban in recidive window, same [addr]/24 range as prior incidents) was blocked by shieldie-guard's sshd jail with a 14400s firewall ban; consistent with persistent automated scanning rather than a targeted attack.

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

  Recurring opportunistic SSH brute-force from 195.178.110.227 (8 prior bans in the recidive window, same [addr]/24 range as multiple recent incidents) tripped shieldie-guard's sshd jail, which applied a 921600s firewall ban; this is persistent noise, not a targeted compromise.

• sshdServer 3MediumAI verdict: malicious1 hitOct 11, 2026, 9:12 AM UTC

  Recidivist SSH brute-force from 195.178.110.227 (2 prior bans in the recidive window) matched shieldie-guard's 'sshd' jail and received a 14400s firewall ban; it fits the recurring [addr]/24 pattern seen in past incidents, which looks like persistent automated scanning rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 6, 2026, 4:08 AM UTC

  same as 73d7d63e: Recurring opportunistic SSH brute-force from [addr] (5 prior bans in the recidive window; same [addr]/24 range seen in multiple recent incidents) tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban. This looks like persistent noise, not a targeted attack.

Timeline

1. Nov 4, 2026, 11:35 PM UTCLast reported
2. Nov 4, 2026, 11:33 PM UTCsshd Low
3. Oct 29, 2026, 3:40 PM UTCsshd Low
4. Oct 28, 2026, 9:31 PM UTCsshd Low
5. Oct 28, 2026, 9:31 PM UTCsshd Low
6. Oct 28, 2026, 9:31 PM UTCsshd Medium
7. Oct 21, 2026, 4:08 AM UTCsshd Low
8. Oct 11, 2026, 2:32 PM UTCsshd Low
9. Oct 11, 2026, 9:12 AM UTCsshd Medium
10. Oct 6, 2026, 4:08 AM UTCsshd Low
11. Sep 20, 2026, 9:10 AM UTCFirst reported