85.185.201.10

Attacks by type

Incidents by severity: High 1, Low 4

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 1HighAI verdict: malicious1 hitNov 11, 2026, 9:07 PM UTC
• sshdServer 2LowAI verdict: malicious1 hitOct 23, 2026, 1:49 AM UTC

  Repeat offender 85.185.201.10 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (4th ban; 3 prior in recidive window), consistent with persistent automated brute-force noise rather than a targeted attack; shieldie-guard applied a 28800s firewall ban.

• sshdServer 2LowAI verdict: malicious1 hitOct 21, 2026, 9:41 PM UTC

  Repeat offender 85.185.201.10 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (3rd ban; 2 prior in the recidive window), consistent with opportunistic automated brute-force noise rather than a targeted attack; no evidence of successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 17, 2026, 5:53 AM UTC

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

• sshdServer 3LowAI verdict: malicious1 hitOct 17, 2026, 5:53 AM UTC

  Repeated SSH auth failures from first-time source 85.185.201.10 (0 prior bans in recidive window) matched shieldie-guard's 'sshd' jail and were blocked with a 3600s ban; consistent with opportunistic internet-wide brute-force noise rather than a targeted attack.

Timeline

1. Nov 11, 2026, 9:11 PM UTCLast reported
2. Nov 11, 2026, 9:07 PM UTCsshd High
3. Oct 23, 2026, 1:49 AM UTCsshd Low
4. Oct 21, 2026, 9:41 PM UTCsshd Low
5. Oct 17, 2026, 5:53 AM UTCsshd Low
6. Oct 17, 2026, 5:53 AM UTCsshd Low
7. Oct 3, 2026, 12:16 PM UTCFirst reported