129.121.96.133

Attacks by type

Incidents by severity: Medium 1, Low 12

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 5, 2026, 4:17 AM UTC

  Recidivist SSH brute-force from 129.121.96.133 (3 prior bans in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail and was contained with a 28800s firewall ban; persistent automated attacker from a recurring [addr]/16 range rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitNov 1, 2026, 1:42 AM UTC

  Recidivist opportunistic SSH brute-force from 129.121.96.133 (7th ban; 6 earlier bans in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and received a 230400s firewall ban; part of a recurring pattern from the [addr]/16 range consistent with automated scanning, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 28, 2026, 6:17 PM UTC

  Recidivist SSH brute-force from 129.121.96.133 (3rd ban in recidive window, same /16 as other recent offenders) tripped shieldie-guard's 'sshd' jail and drew a 14400s ban; persistent opportunistic scanning, not evidence of a targeted attack or compromise.

• sshdServer 2LowAI verdict: malicious1 hitOct 26, 2026, 11:41 PM UTC

  Recidivist opportunistic SSH brute-force from 129.121.96.133 (6th ban; 5 earlier bans in the recidive window) re-tripped shieldie-guard's sshd jail and received an escalated 115200s firewall ban; consistent with prior noise-level scanning from the [addr]/16 range, not a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 24, 2026, 2:29 AM UTC

  Persistent automated SSH brute-force from 129.121.96.133 (4th ban, 3 prior in recidive window) was contained by shieldie-guard's sshd jail with an escalated 28800s firewall ban; it is a repeat offender but there is no evidence of a successful login or targeting beyond generic scanning.

• sshdServer 2LowAI verdict: malicious1 hitOct 22, 2026, 5:32 AM UTC

  Persistent SSH brute-force from 129.121.96.133 (5th ban in recidive window) tripped shieldie-guard's sshd jail and received a 57600s firewall ban; it fits the recurring pattern from the [addr]/16 range and looks like automated scanning rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 18, 2026, 4:45 PM UTC

  Repeat offender 129.121.96.133 (previously banned 2026-10-13) tripped shieldie-guard's 'sshd' jail again and received an escalated 7200s ban; together with prior hits from the same 129.121.x.x range, this looks like persistent opportunistic scanning, not a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 17, 2026, 10:45 AM UTC

  Persistent automated SSH brute-force from 129.121.96.133 (third ban in the recidive window, escalating 7200s to 14400s) was contained by shieldie-guard's sshd jail; the pattern is opportunistic scanning rather than a targeted attack, with no evidence of a successful login.

• sshdServer 1LowAI verdict: malicious1 hitOct 13, 2026, 4:46 AM UTC

  Repeated SSH auth failures from 129.121.96.133 tripped shieldie-guard's 'sshd' jail (3600s ban, no prior bans); consistent with recurring opportunistic scanning from the [addr]/16 range seen in past incidents rather than a targeted attack.

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

  Persistent repeat offender 129.121.96.133 (4th ban, 3 prior in recidive window including refused attempts) again tripped shieldie-guard's sshd jail and received an escalated 28800s firewall ban; persistent automated SSH brute-force, no evidence of successful auth or targeting beyond opportunistic scanning.

• sshdServer 3LowAI verdict: malicious1 hitOct 11, 2026, 8:34 PM UTC

  Repeat SSH brute-force from 129.121.96.133 (1 prior ban in the recidive window) tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; the pattern matches recurring opportunistic scanning from the [addr]/16 range rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 11, 2026, 5:02 AM UTC

  Repeat offender 129.121.96.133 (3rd ban, after 3600s and escalated bans on [path]) again tripped shieldie-guard's sshd jail with repeated SSH auth failures and received an escalated 14400s ban; persistent but consistent with opportunistic brute-force noise, with no evidence of successful auth or host-specific targeting.

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

  Repeat offender 129.121.96.133 (banned 3600s on 2026-10-06) again tripped shieldie-guard's sshd jail with repeated SSH auth failures and received an escalated 7200s ban; persistent but consistent with opportunistic brute-force noise rather than a targeted attack, with no evidence of successful login.

Timeline

1. Nov 5, 2026, 4:22 AM UTCLast reported
2. Nov 5, 2026, 4:17 AM UTCsshd Medium
3. Nov 1, 2026, 1:42 AM UTCsshd Low
4. Oct 28, 2026, 6:17 PM UTCsshd Low
5. Oct 26, 2026, 11:41 PM UTCsshd Low
6. Oct 24, 2026, 2:29 AM UTCsshd Low
7. Oct 22, 2026, 5:32 AM UTCsshd Low
8. Oct 18, 2026, 4:45 PM UTCsshd Low
9. Oct 17, 2026, 10:45 AM UTCsshd Low
10. Oct 13, 2026, 4:46 AM UTCsshd Low
11. Oct 12, 2026, 4:40 AM UTCsshd Low
12. Oct 11, 2026, 8:34 PM UTCsshd Low
13. Oct 11, 2026, 5:02 AM UTCsshd Low
14. Oct 10, 2026, 9:57 PM UTCsshd Low
15. Oct 6, 2026, 8:59 PM UTCFirst reported