36.64.131.68

Attacks by type

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

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: malicious15 hitsNov 12, 2026, 12:53 AM UTC
• sshdServer 1LowAI verdict: malicious5 hitsNov 5, 2026, 3:11 PM UTC

  Persistent recidivist 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (6 prior bans in the recidive window), consistent with untargeted automated brute-force noise; shieldie-guard has already applied a 230400s firewall ban.

• sshdServer 1LowAI verdict: malicious1 hitOct 29, 2026, 4:25 PM UTC

  Persistent repeat offender 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (7th ban, 6 prior in recidive window), now under a 230400s firewall ban; consistent with automated brute-force noise, not a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 27, 2026, 5:44 PM UTC

  Repeat SSH brute-force from 36.64.131.68 (2nd ban; 1 prior ban in recidive window, refused attempts included) tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; persistent but consistent with opportunistic automated scanning rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 26, 2026, 1:35 AM UTC

  Persistent repeat offender 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (6th ban, 5 prior in recidive window), now under a 115200s firewall ban; consistent with automated brute-force noise, not evidence of a targeted attack or successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 18, 2026, 5:24 AM UTC

  Persistent repeat offender 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (5th ban, 4 prior in recidive window); consistent with automated brute-force noise rather than a targeted attack, already contained by a 57600s firewall ban.

• sshdServer 1LowAI verdict: malicious1 hitOct 15, 2026, 7:23 AM UTC

  Persistent repeat offender 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (6th ban; 5 prior in the recidive window). This looks like automated brute-force noise, not a targeted attack, and shieldie-guard already applied a 115200s firewall ban.

• sshdServer 2LowAI verdict: malicious1 hitOct 13, 2026, 4:51 PM UTC

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

• sshdServer 3MediumAI verdict: malicious1 hitOct 13, 2026, 4:49 PM UTC

  Recidivist source 36.64.131.68 (1 prior ban in the recidive window, incl. the 2026-10-08 incident; refused attempts included) resumed repeated SSH auth failures and shieldie-guard's 'sshd' jail applied an escalated 7200s nftables ban — persistent automated brute-force, no evidence of targeting or successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 12, 2026, 5:06 PM UTC

  Persistent repeat offender 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (5th ban; 4 prior in the recidive window, refused attempts included); this is consistent with automated brute-force noise rather than a targeted attack, and shieldie-guard has already applied a 57600s ban.

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

  Persistent repeat offender 36.64.131.68 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures (4th ban; 3 prior in the recidive window, refused attempts included). This looks like opportunistic brute-force noise, not a targeted attack, and shieldie-guard applied a 28800s firewall ban.

Timeline

1. Nov 12, 2026, 12:57 AM UTCLast reported
2. Nov 12, 2026, 12:53 AM UTCsshd Critical
3. Nov 5, 2026, 3:11 PM UTCsshd Low
4. Oct 29, 2026, 4:25 PM UTCsshd Low
5. Oct 27, 2026, 5:44 PM UTCsshd Low
6. Oct 26, 2026, 1:35 AM UTCsshd Low
7. Oct 18, 2026, 5:24 AM UTCsshd Low
8. Oct 15, 2026, 7:23 AM UTCsshd Low
9. Oct 13, 2026, 4:51 PM UTCsshd Low
10. Oct 13, 2026, 4:49 PM UTCsshd Medium
11. Oct 12, 2026, 5:06 PM UTCsshd Low
12. Oct 12, 2026, 5:53 AM UTCsshd Low
13. Oct 6, 2026, 10:28 AM UTCFirst reported