125.142.37.91

Attacks by type

Incidents by severity: Medium 3, Low 5

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, 3:55 AM UTC

  Persistent recidivist SSH brute-force from 125.142.37.91 (3rd ban: 2 prior bans in recidive window, seen 2026-10-11 and 2026-11-01, refused attempts included) matched shieldie-guard's 'sshd' jail, which applied an escalated 14400s firewall ban; pattern indicates automated persistent scanning rather than a confirmed targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitNov 1, 2026, 10:59 AM UTC

  Recidivist SSH brute-force from 125.142.37.91 (1 prior ban in the recidive window, also seen 2026-10-11) matched shieldie-guard's 'sshd' jail, which applied a 7200s firewall ban; it looks like persistent automated scanning, not a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 27, 2026, 10:24 AM UTC

  Persistent automated SSH brute-force from recidivist 125.142.37.91 (4 prior bans in recidive window, previously analyzed 2026-10-24) re-tripped shieldie-guard's sshd jail, which applied an escalated 57600s firewall ban; the pattern fits opportunistic scanning rather than a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 26, 2026, 8:32 AM UTC

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

• sshdServer 2LowAI verdict: malicious1 hitOct 24, 2026, 1:19 AM UTC

  Recidivist automated SSH brute-force from 125.142.37.91 (3 prior bans in recidive window, previously seen 2026-10-18) re-tripped shieldie-guard's sshd jail and was blocked with a 28800s firewall ban; it looks like persistent opportunistic scanning, not a targeted attack, and there's no evidence of a successful login.

• sshdServer 2LowAI verdict: malicious1 hitOct 18, 2026, 3:24 PM UTC

  Recidivist automated SSH brute-force from 125.142.37.91 (5th ban; 4 prior in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 57600s firewall ban. This is persistent opportunistic scanning, not evidence of a targeted attack or compromise.

• sshdServer 2LowAI verdict: malicious1 hitOct 13, 2026, 5:18 PM UTC

  Recidivist SSH auth-failure scanning from 125.142.37.91 (4th ban; 3 prior in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; persistent automated noise rather than evidence of a targeted attack, with no sign of a successful login.

• sshdServer 1MediumAI verdict: malicious1 hitOct 11, 2026, 7:06 AM UTC

  Repeated SSH auth failures from 125.142.37.91 (no prior bans in the recidive window) matched shieldie-guard's 'sshd' jail, which applied a 3600s firewall ban; this is consistent with opportunistic brute-force scanning rather than a targeted attack.

Timeline

1. Nov 5, 2026, 4:00 AM UTCLast reported
2. Nov 5, 2026, 3:55 AM UTCsshd Medium
3. Nov 1, 2026, 10:59 AM UTCsshd Medium
4. Oct 27, 2026, 10:24 AM UTCsshd Low
5. Oct 26, 2026, 8:32 AM UTCsshd Low
6. Oct 24, 2026, 1:19 AM UTCsshd Low
7. Oct 18, 2026, 3:24 PM UTCsshd Low
8. Oct 13, 2026, 5:18 PM UTCsshd Low
9. Oct 11, 2026, 7:06 AM UTCsshd Medium
10. Sep 24, 2026, 1:03 AM UTCFirst reported