96.78.175.36

Attacks by type

Incidents by severity: Medium 4, Low 5

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 4, 2026, 10:56 PM UTC

  Persistent recidivist SSH brute-force from 96.78.175.36 (4 prior bans in recidive window, related /24 activity from .45) again matched shieldie-guard's 'sshd' jail and was contained by a 57600s firewall ban; consistent with a persistent automated campaign, not a targeted compromise.

• sshdServer 1MediumAI verdict: malicious1 hitNov 4, 2026, 2:42 PM UTC

  Persistent recidivist SSH brute-force from 96.78.175.36 (3 prior bans in recidive window, seen repeatedly since 2026-09 alongside a /24 neighbor) again matched shieldie-guard's 'sshd' jail and was contained by a 28800s firewall ban; persistent automated targeting of this host, no evidence of successful auth.

• sshdServer 1MediumAI verdict: malicious1 hitNov 3, 2026, 9:16 PM UTC

  Recidivist SSH brute-force from 96.78.175.36 (2 prior bans in recidive window, refused attempts included; previously flagged as persistent) again matched shieldie-guard's 'sshd' jail and was contained by a 14400s firewall ban; it is persistent, opportunistic scanning from a /24 seen before ([addr]), not evidence of a targeted compromise.

• sshdServer 2LowAI verdict: malicious1 hitOct 31, 2026, 12:10 AM UTC

  Recidivist opportunistic SSH credential guessing from 96.78.175.36 (7th ban: 6 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 230400s firewall ban; the pattern matches prior verdicts of persistent noise, not a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 28, 2026, 8:13 AM UTC

  Recidivist opportunistic SSH credential guessing from 96.78.175.36 (6th ban: 5 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban; consistent with prior untargeted brute-force verdict for this address.

• sshdServer 2LowAI verdict: malicious1 hitOct 27, 2026, 6:12 AM UTC

  Recidivist opportunistic SSH credential guessing from 96.78.175.36 (5th ban: 4 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 57600s firewall ban; consistent with untargeted scanning noise, no sign of a successful login.

• sshdServer 1MediumAI verdict: malicious1 hitOct 20, 2026, 10:46 PM UTC

  Persistent recidivist 96.78.175.36 (3 prior bans in the recidive window, refused attempts included, seen since 2026-09-21) again triggered shieldie-guard's 'sshd' jail and was banned for 28800s; the pattern looks like a persistent automated SSH brute-force campaign against this host rather than one-off noise, with no evidence of a successful login.

• sshdServer 3LowAI verdict: malicious1 hitOct 18, 2026, 6:02 AM UTC

  Repeat SSH brute-force from 96.78.175.36 (2nd ban; 1 prior ban in recidive window, refused attempts included) tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; it looks like opportunistic internet scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 12, 2026, 3:34 AM UTC

  Persistent SSH brute-force from 96.78.175.36 re-tripped shieldie-guard's sshd jail (7th ban; 6 prior in recidive window, refused attempts included) and received a 230400s firewall ban; it looks like a persistent automated scanner rather than a targeted attack, and the neighboring [addr] was also seen earlier.

Timeline

1. Nov 4, 2026, 10:59 PM UTCLast reported
2. Nov 4, 2026, 10:56 PM UTCsshd Medium
3. Nov 4, 2026, 2:42 PM UTCsshd Medium
4. Nov 3, 2026, 9:16 PM UTCsshd Medium
5. Oct 31, 2026, 12:10 AM UTCsshd Low
6. Oct 28, 2026, 8:13 AM UTCsshd Low
7. Oct 27, 2026, 6:12 AM UTCsshd Low
8. Oct 20, 2026, 10:46 PM UTCsshd Medium
9. Oct 18, 2026, 6:02 AM UTCsshd Low
10. Oct 12, 2026, 3:34 AM UTCsshd Low
11. Sep 21, 2026, 4:07 AM UTCFirst reported