182.93.7.194

Attacks by type

Incidents by severity: Critical 1, Medium 1, Low 3

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 1CriticalAI verdict: malicious1 hitNov 11, 2026, 3:17 PM UTC
• sshdServer 2LowAI verdict: malicious1 hitNov 8, 2026, 3:28 AM UTC

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

• sshdServer 3LowAI verdict: malicious1 hitOct 29, 2026, 9:49 PM UTC

  Untargeted SSH brute-force noise: repeated auth failures from 182.93.7.194 (first offense, no recidive) tripped shieldie-guard's sshd jail, which applied a deterministic 3600s firewall ban.

• sshdServer 1MediumAI verdict: malicious1 hitOct 25, 2026, 1:24 PM UTC

  Recidivist SSH brute-force from 182.93.7.194 (1 prior ban in the recidive window, previously banned 2026-10-24 for 3600s) re-matched shieldie-guard's 'sshd' jail, which applied an escalated 7200s firewall ban; the /16 neighbor [addr] showed the same recidivist pattern in [path], suggesting persistent opportunistic scanning from this range rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 24, 2026, 7:18 PM UTC

  Repeated SSH auth failures from 182.93.7.194 (0 prior bans in the recidive window) matched shieldie-guard's 'sshd' jail, which applied a deterministic 3600s firewall ban; the pattern is consistent with opportunistic internet-wide brute-force noise rather than a targeted attack.

Timeline

1. Nov 11, 2026, 3:21 PM UTCLast reported
2. Nov 11, 2026, 3:17 PM UTCsshd Critical
3. Nov 8, 2026, 3:28 AM UTCsshd Low
4. Oct 29, 2026, 9:49 PM UTCsshd Low
5. Oct 25, 2026, 1:24 PM UTCsshd Medium
6. Oct 24, 2026, 7:18 PM UTCsshd Low
7. Sep 23, 2026, 10:26 AM UTCFirst reported