201.17.133.138

Attacks by type

Incidents by severity: Medium 2, 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 1LowAI verdict: malicious1 hitNov 5, 2026, 12:26 AM UTC

  Recidivist opportunistic SSH brute-force from 201.17.133.138 (4th ban; 3 earlier in recidive window) re-tripped shieldie-guard's sshd jail and was blocked with a 28800s firewall ban; it matches prior untargeted scanning with no sign of successful auth.

• sshdServer 2MediumAI verdict: malicious1 hitOct 31, 2026, 4:12 AM UTC

  Persistent recidivist SSH brute-force from 201.17.133.138 (third ban, 2 prior in recidive window, consistent with 2026-10-12 and 2026-10-26 incidents) matched shieldie-guard's 'sshd' jail, which applied a 14400s firewall ban; the pattern suggests persistent automated targeting of this host rather than one-off noise, but there is no evidence of a successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 28, 2026, 8:48 PM UTC

  Repeat offender 201.17.133.138 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (3rd ban, 2 earlier in recidive window, refused attempts included); consistent with untargeted brute-force noise, already mitigated by a 14400s firewall ban.

• sshdServer 2MediumAI verdict: malicious1 hitOct 26, 2026, 9:37 PM UTC

  Recidivist SSH brute-force from 201.17.133.138 (1 prior ban in recidive window, consistent with the 2026-10-12 first-time incident) matched shieldie-guard's 'sshd' jail, which applied an escalated 7200s firewall ban; pattern indicates persistent automated scanning rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 18, 2026, 4:37 AM UTC

  Repeat offender 201.17.133.138 (previously banned 2026-10-13) re-tripped shieldie-guard's sshd jail with repeated SSH auth failures and received an escalated 7200s firewall ban; the pattern is consistent with untargeted brute-force noise.

• sshdServer 1LowAI verdict: malicious1 hitOct 13, 2026, 3:57 AM UTC

  Untargeted SSH brute-force noise: 201.17.133.138 tripped shieldie-guard's sshd jail with repeated auth failures and received a deterministic 3600s firewall ban; first ban for this address (0 prior in recidive window), consistent with prior similar incidents.

• sshdServer 2LowAI verdict: malicious1 hitOct 12, 2026, 5:26 PM UTC

  Repeated SSH auth failures from first-time source 201.17.133.138 (0 prior bans in recidive window) matched shieldie-guard's 'sshd' jail, which applied a 3600s firewall ban; the pattern fits untargeted internet brute-force noise and is already mitigated.

• sshdServer 3LowAI verdict: malicious1 hitOct 12, 2026, 5:26 PM UTC

  Repeated SSH auth failures from 201.17.133.138 tripped shieldie-guard's sshd jail, which applied a 3600s firewall ban; with no prior bans in the recidive window, this looks like opportunistic internet-wide brute-force noise rather than a targeted attack, consistent with similar past incidents.

Timeline

1. Nov 5, 2026, 12:26 AM UTCLast reported
2. Nov 5, 2026, 12:26 AM UTCsshd Low
3. Oct 31, 2026, 4:12 AM UTCsshd Medium
4. Oct 28, 2026, 8:48 PM UTCsshd Low
5. Oct 26, 2026, 9:37 PM UTCsshd Medium
6. Oct 18, 2026, 4:37 AM UTCsshd Low
7. Oct 13, 2026, 3:57 AM UTCsshd Low
8. Oct 12, 2026, 5:27 PM UTCFirst reported
9. Oct 12, 2026, 5:26 PM UTCsshd Low
10. Oct 12, 2026, 5:26 PM UTCsshd Low