122.15.129.26

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 1LowAI verdict: malicious1 hitNov 4, 2026, 10:39 PM UTC

  Recidivist opportunistic SSH credential scanning from 122.15.129.26 (4th ban; 3 earlier bans in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; consistent with prior untargeted noise, no evidence of successful auth.

• sshdServer 1LowAI verdict: malicious1 hitOct 30, 2026, 9:13 PM UTC

  Recidivist opportunistic SSH credential scanning from 122.15.129.26 (3rd ban; 2 earlier bans in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 14400s firewall ban; no evidence of successful auth or targeting.

• sshdServer 1LowAI verdict: malicious1 hitOct 28, 2026, 8:09 PM UTC

  Recidivist opportunistic SSH credential scanning from 122.15.129.26 (1 earlier ban in recidive window) re-tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; no evidence of successful auth or targeting.

• sshdServer 2LowAI verdict: malicious1 hitOct 10, 2026, 11:57 PM UTC

  Repeated SSH auth failures from 122.15.129.26 (no prior bans in the recidive window) matched shieldie-guard's 'sshd' jail and were contained by a 3600s firewall ban; this is consistent with opportunistic internet-wide brute-force noise, not a targeted attack.

• sshdServer 3HighAI verdict: malicious1 hitOct 10, 2026, 11:56 PM UTC

Timeline

1. Nov 4, 2026, 10:44 PM UTCLast reported
2. Nov 4, 2026, 10:39 PM UTCsshd Low
3. Oct 30, 2026, 9:13 PM UTCsshd Low
4. Oct 28, 2026, 8:09 PM UTCsshd Low
5. Oct 10, 2026, 11:57 PM UTCsshd Low
6. Oct 10, 2026, 11:56 PM UTCsshd High
7. Sep 22, 2026, 8:19 AM UTCFirst reported