43.134.71.187

Attacks by type

Incidents by severity: Critical 1, Low 3

Incidents

These incidents come from 2 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: malicious18 hitsNov 11, 2026, 11:24 AM UTC
• sshdServer 1LowAI verdict: malicious5 hitsNov 7, 2026, 5:15 PM UTC

  Untargeted SSH brute-force noise from repeat offender 43.134.71.187 (1 prior ban in the recidive window, same [addr]/16 range as recent incidents) tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban.

• sshdServer 2LowAI verdict: malicious1 hitOct 23, 2026, 3:30 PM UTC

  Repeated SSH auth failures from 43.134.71.187 tripped shieldie-guard's sshd jail (3600s firewall ban, no prior bans in recidive window, attempts refused), consistent with opportunistic internet-wide brute-force noise rather than a targeted attack, matching prior similar incidents.

• sshdServer 1LowAI verdict: malicious1 hitOct 17, 2026, 10:04 PM UTC

  Repeated SSH auth failures from 43.134.71.187 tripped shieldie-guard's sshd jail, which applied a deterministic 3600s firewall ban; this is the address's first ban (recidive 0), consistent with opportunistic internet-wide SSH scanning rather than a targeted attack.

Timeline

1. Nov 11, 2026, 11:25 AM UTCLast reported
2. Nov 11, 2026, 11:24 AM UTCsshd Critical
3. Nov 7, 2026, 5:15 PM UTCsshd Low
4. Oct 23, 2026, 3:30 PM UTCsshd Low
5. Oct 17, 2026, 10:07 PM UTCFirst reported
6. Oct 17, 2026, 10:04 PM UTCsshd Low