59.98.148.5

Attacks by type

Incidents by severity: Medium 2, 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 1MediumAI verdict: malicious1 hitNov 12, 2026, 12:50 AM UTC
• sshdServer 2LowAI verdict: malicious1 hitNov 8, 2026, 11:08 AM UTC

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

• sshdServer 3LowAI verdict: malicious5 hitsNov 7, 2026, 4:33 PM UTC

  Persistent but likely untargeted SSH brute-force from 59.98.148.5: repeated auth failures tripped shieldie-guard's sshd jail, which applied a 14400s escalated ban; this is the 3rd ban of this address in the recidive window (refused attempts included), so it is repeat noise, not a targeted attack.

• sshdServer 3MediumAI verdict: malicious1 hitOct 30, 2026, 7:13 PM UTC

  Repeat-offender SSH brute-force: 59.98.148.5 tripped shieldie-guard's sshd jail for a third time in the recidive window (2 prior bans), earning an escalated 14400s ban — persistent but likely [path], no evidence of successful auth.

• sshdServer 3LowAI verdict: malicious1 hitOct 21, 2026, 5:33 PM UTC

  Recidivist opportunistic SSH credential scanning from 59.98.148.5 (2nd ban; 1 earlier ban in the recidive window) tripped shieldie-guard's sshd jail, which applied a deterministic 7200s firewall ban; no indication of a targeted attack or successful login.

Timeline

1. Nov 12, 2026, 12:52 AM UTCLast reported
2. Nov 12, 2026, 12:50 AM UTCsshd Medium
3. Nov 8, 2026, 11:08 AM UTCsshd Low
4. Nov 7, 2026, 4:33 PM UTCsshd Low
5. Oct 30, 2026, 7:13 PM UTCsshd Medium
6. Oct 21, 2026, 5:33 PM UTCsshd Low
7. Sep 26, 2026, 4:16 PM UTCFirst reported