195.178.110.30

Attacks by type

Incidents by severity: Medium 4, Low 10

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

  Recidivist SSH brute-force from 195.178.110.30 (2 prior bans in the recidive window) again tripped shieldie-guard's 'sshd' jail and drew a 14400s firewall ban; it belongs to the same [addr]/24 range seen in multiple past incidents, which points to a persistent automated campaign from that network and not a single-host targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitNov 5, 2026, 3:00 AM UTC

  Recidivist SSH brute-force from 195.178.110.30 (1 prior ban in the recidive window) again tripped shieldie-guard's 'sshd' jail and drew a 7200s firewall ban; it is part of the same [addr]/24 range seen in prior incidents, which points to persistent automated scanning from one network rather than a narrowly targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitNov 5, 2026, 2:58 AM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (8th ban, 7 earlier in recidive window, from the repeatedly seen [addr]/24 range); shieldie-guard applied a 460800s firewall ban — persistent automated noise, not targeted, consistent with prior verdicts.

• sshdServer 2LowAI verdict: malicious1 hitNov 1, 2026, 3:49 AM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (7th ban, 6 earlier in recidive window, from the repeatedly seen [addr]/24 range); shieldie-guard's sshd jail applied a 230400s firewall ban. This looks like persistent automated scanning, not a targeted attack.

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

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (6th ban, 5 earlier in recidive window, from the repeatedly seen [addr]/24 range); shieldie-guard applied a 115200s firewall ban, and nothing in the evidence suggests a successful login or a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 29, 2026, 6:03 PM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (5th ban, 4 earlier in recidive window, from the repeatedly seen [addr]/24 range); shieldie-guard's sshd jail applied a 57600s firewall ban, and it is consistent with prior noise-level verdicts rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 29, 2026, 6:26 AM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (4th ban, 3 earlier in recidive window), part of the [addr]/24 range repeatedly seen; already contained by shieldie-guard's 28800s firewall ban, no sign of successful auth.

• sshdServer 2LowAI verdict: malicious1 hitOct 29, 2026, 12:47 AM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (3rd ban, 2 earlier in recidive window) from the same [addr]/24 range seen in prior [path] incidents; contained by shieldie-guard's sshd jail with a 14400s firewall ban, no sign of targeting or successful auth.

• sshdServer 2LowAI verdict: malicious1 hitOct 28, 2026, 10:44 PM UTC

  Recidivist opportunistic SSH brute-force from 195.178.110.30 (2nd ban, 1 earlier in recidive window; same [addr]/24 range seen in prior [path] incidents) contained by shieldie-guard's sshd jail with a 7200s nftables ban; no evidence of successful auth.

• sshdServer 3LowAI verdict: malicious1 hitOct 15, 2026, 4:12 AM UTC

  Persistent, recurring SSH brute-force from 195.178.110.30 (10th ban in the recidive window, same /24 seen in prior incidents) was contained by shieldie-guard's sshd jail with an escalated 1843200s (~21-day) firewall ban; pattern indicates automated scanning noise rather than a targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitOct 13, 2026, 8:28 PM UTC

  Persistent recidivist SSH brute-force from 195.178.110.30 (9 prior bans in the recidive window, up from 6 previously; neighbor [addr] also seen) triggered shieldie-guard's 'sshd' jail, which applied a 1843200s (~21-day) firewall ban; this looks like a persistent automated scanner rather than a targeted attack, with no evidence of successful login.

• sshdServer 2LowAI verdict: malicious1 hitOct 7, 2026, 10:45 AM UTC

  Recurring opportunistic SSH brute-force from 195.178.110.30 (9 prior bans in the recidive window; same [addr]/24 range as several recent incidents) tripped shieldie-guard's sshd jail, which applied a 1843200s firewall ban; the pattern is persistent scanning noise, not a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 4, 2026, 11:57 AM UTC

  Persistent SSH brute-force from 195.178.110.30 (8 earlier bans in the recidive window) was contained by shieldie-guard's sshd jail with a 921600s firewall ban; the source shares the [addr]/24 range with prior low-severity incidents, which points to a recurring automated campaign from that range rather than a targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitOct 2, 2026, 11:36 PM UTC

  Persistent recidivist SSH brute-force from 195.178.110.30 (8 prior bans in the recidive window, up from 6 on 2026-09-23) re-triggered shieldie-guard's 'sshd' jail, which applied a 921600s (~10.7-day) nftables ban; this looks like automated scanning, not a targeted compromise, and the evidence shows no successful auth.

Timeline

1. Nov 5, 2026, 5:07 AM UTCLast reported
2. Nov 5, 2026, 5:06 AM UTCsshd Medium
3. Nov 5, 2026, 3:00 AM UTCsshd Medium
4. Nov 5, 2026, 2:58 AM UTCsshd Low
5. Nov 1, 2026, 3:49 AM UTCsshd Low
6. Oct 30, 2026, 1:20 PM UTCsshd Low
7. Oct 29, 2026, 6:03 PM UTCsshd Low
8. Oct 29, 2026, 6:26 AM UTCsshd Low
9. Oct 29, 2026, 12:47 AM UTCsshd Low
10. Oct 28, 2026, 10:44 PM UTCsshd Low
11. Oct 15, 2026, 4:12 AM UTCsshd Low
12. Oct 13, 2026, 8:28 PM UTCsshd Medium
13. Oct 7, 2026, 10:45 AM UTCsshd Low
14. Oct 4, 2026, 11:57 AM UTCsshd Low
15. Oct 2, 2026, 11:36 PM UTCsshd Medium
16. Sep 20, 2026, 9:10 AM UTCFirst reported