168.76.131.178

Attacks by type

Incidents by severity: Medium 1, Low 6

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, 11:37 PM UTC

  Recidivist SSH brute-force from 168.76.131.178 (1 prior ban in the recidive window, consistent with the 2026-10-19 first-time incident) re-matched shieldie-guard's 'sshd' jail and is now under an escalated 7200s firewall ban; likely persistent automated scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 30, 2026, 10:40 AM UTC

  Recidivist opportunistic SSH credential guessing from 168.76.131.178 (5th ban; 4 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and was banned for 57600s; consistent with untargeted scanning noise, no evidence of successful auth.

• sshdServer 2LowAI verdict: malicious1 hitOct 26, 2026, 10:47 PM UTC

  Recidivist opportunistic SSH credential guessing from 168.76.131.178 (4th ban; 3 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; consistent with prior verdicts, no evidence of a successful login or targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 21, 2026, 1:55 AM UTC

  Repeated SSH auth failures from 168.76.131.178 tripped shieldie-guard's sshd jail, which applied a 3600s firewall ban with no prior bans in the recidive window; this is consistent with opportunistic internet-wide brute-force noise, not a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 19, 2026, 7:19 PM UTC

  Persistent repeat offender 168.76.131.178 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (5th ban; 4 prior in recidive window, refused attempts included) and received a 57600s firewall ban; this fits opportunistic automated brute-force, not evidence of a targeted attack or compromise.

• sshdServer 1LowAI verdict: malicious1 hitOct 19, 2026, 5:10 PM UTC

  First-time SSH brute-force burst from 168.76.131.178 (0 prior bans in the recidive window) matched shieldie-guard's 'sshd' jail and was already blocked with a 3600s firewall ban; this looks like opportunistic internet scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 10, 2026, 9:15 PM UTC

  Persistent repeat offender 168.76.131.178 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (4th ban; 3 prior in the recidive window, refused attempts included) and was contained with a 28800s firewall ban; consistent with automated brute-force noise, not a targeted attack.

Timeline

1. Nov 4, 2026, 11:40 PM UTCLast reported
2. Nov 4, 2026, 11:37 PM UTCsshd Medium
3. Oct 30, 2026, 10:40 AM UTCsshd Low
4. Oct 26, 2026, 10:47 PM UTCsshd Low
5. Oct 21, 2026, 1:55 AM UTCsshd Low
6. Oct 19, 2026, 7:19 PM UTCsshd Low
7. Oct 19, 2026, 5:10 PM UTCsshd Low
8. Oct 10, 2026, 9:15 PM UTCsshd Low
9. Sep 23, 2026, 4:47 AM UTCFirst reported