20.12.41.6

Attacks by type

Incidents by severity: Critical 1, Medium 2, 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 1MediumAI verdict: malicious1 hitNov 12, 2026, 5:31 AM UTC
• sshdServer 2CriticalAI verdict: malicious5 hitsNov 11, 2026, 10:17 PM UTC
• sshdServer 2LowAI verdict: malicious1 hitNov 4, 2026, 11:23 AM UTC

  Recidivist opportunistic SSH brute-force from 20.12.41.6 (4th ban: 3 earlier bans in the recidive window, refused attempts included); shieldie-guard's sshd jail applied an escalated 28800s firewall ban; no evidence of targeting or successful auth.

• sshdServer 2MediumAI verdict: malicious1 hitOct 22, 2026, 5:57 AM UTC

  Persistent recidivist SSH brute-force from 20.12.41.6 (4th ban, 3 earlier bans in the recidive window, including refused attempts) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; the pattern looks like persistent automated scanning rather than a confirmed targeted attack, and there is no evidence of a successful login.

• sshdServer 2LowAI verdict: malicious1 hitOct 12, 2026, 3:39 PM UTC

  20.12.41.6 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (3rd ban; 2 prior in the recidive window, refused attempts included), and shieldie-guard applied a 14400s firewall ban; this persistent recidivist behavior fits opportunistic automated brute-forcing, and the evidence shows no sign of a targeted attack or a successful login.

• sshdServer 2LowAI verdict: malicious1 hitOct 12, 2026, 2:49 AM UTC

  20.12.41.6 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (2nd ban; 1 prior in the recidive window, refused attempts included), and shieldie-guard applied a 7200s firewall ban; this is consistent with persistent opportunistic brute-force noise, and the evidence does not indicate a targeted attack.

Timeline

1. Nov 12, 2026, 5:32 AM UTCLast reported
2. Nov 12, 2026, 5:31 AM UTCsshd Medium
3. Nov 11, 2026, 10:17 PM UTCsshd Critical
4. Nov 4, 2026, 11:23 AM UTCsshd Low
5. Oct 22, 2026, 5:57 AM UTCsshd Medium
6. Oct 12, 2026, 3:39 PM UTCsshd Low
7. Oct 12, 2026, 2:49 AM UTCsshd Low
8. Sep 24, 2026, 10:28 AM UTCFirst reported