2.57.122.150

Attacks by type

Incidents by severity: Critical 1, Medium 4, Low 10

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 4, 2026, 9:27 PM UTC

  Recidivist SSH brute-force from 2.57.122.150 (4 prior bans in recidive window, recurring [addr]/24 source seen in past incidents) tripped shieldie-guard's 'sshd' jail and drew a 57600s nftables ban; persistent opportunistic scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitNov 4, 2026, 9:27 PM UTC

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (7th ban: 6 earlier in the recidive window, refused attempts included), part of the same [addr]/24 range seen previously; shieldie-guard has applied a 230400s firewall ban, with no evidence of a successful login.

• sshdServer 3LowAI verdict: malicious1 hitNov 4, 2026, 9:26 PM UTC

  Recidivist opportunistic SSH brute-force from 2.57.122.150 (3rd ban in recidive window, recurring [addr]/24 range) was contained by shieldie-guard's sshd jail with an escalated 14400s ban; pattern indicates persistent automated scanning rather than a targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitNov 3, 2026, 1:18 AM UTC

  Recidivist SSH brute-force from 2.57.122.150 (3 prior bans in recidive window, same recurring [addr]/24 range as past incidents) tripped shieldie-guard's 'sshd' jail and received a 28800s ban — persistent opportunistic scanning rather than a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitNov 3, 2026, 1:17 AM UTC

  Recidivist opportunistic SSH brute-force from 2.57.122.150 (2nd ban in recidive window, recurring [addr]/24 range) was contained by shieldie-guard's sshd jail with a 7200s firewall ban; consistent with untargeted scanning noise, not a targeted attack.

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

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (6th ban: 5 earlier in the recidive window, refused attempts included). This is consistent with prior scanning from the same [addr]/24 range and is noise rather than a targeted attack. shieldie-guard already applied a 115200s firewall ban.

• sshdServer 2LowAI verdict: malicious1 hitOct 28, 2026, 12:46 AM UTC

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (6th ban: 5 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban; consistent with prior verdicts, noise-level scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 26, 2026, 1:07 PM UTC

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (5th ban: 4 earlier in the recidive window) re-tripped shieldie-guard's sshd jail, which applied a 57600s firewall ban; the pattern matches the same address's prior incidents and [addr]/24 neighbors, so this is consistent with untargeted mass scanning rather than a targeted attack, and no successful authentication is shown.

• sshdServer 3LowAI verdict: malicious1 hitOct 26, 2026, 1:07 PM UTC

  Repeated SSH auth failures from 2.57.122.150 tripped shieldie-guard's sshd jail (3600s ban, no prior bans of this address); the source is in the [addr]/24 range seen in earlier brute-force incidents, consistent with ongoing opportunistic scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 25, 2026, 2:20 AM UTC

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (5th ban: 4 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and drew a 57600s firewall ban, consistent with prior noise from the [addr]/24 range rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 23, 2026, 11:04 AM UTC

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (4th ban: 3 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and drew a 28800s firewall ban; it matches the prior [addr]/24 pattern and points to commodity noise, not a targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitOct 13, 2026, 6:51 AM UTC

  Persistent recidivist SSH brute-force from 2.57.122.150 (5 prior bans in the recidive window, escalating from earlier incidents) matched shieldie-guard's 'sshd' jail and was banned for 115200s; the pattern is persistent automated targeting of this host, but nothing in the evidence indicates a successful login.

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

  Recidivist opportunistic SSH credential scanning from 2.57.122.150 (9th ban: 8 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and drew a 921600s firewall ban; it matches the prior low-severity pattern from neighboring 2.57.12x.x hosts and shows no sign of targeting or successful auth.

• sshdServer 1MediumAI verdict: malicious1 hitOct 11, 2026, 2:12 AM UTC

  Persistent recidivist SSH brute-force from 2.57.122.150 (4 prior bans in the recidive window, escalating since 2026-09-21) was banned by shieldie-guard's 'sshd' jail for 57600s. This looks like a persistent automated scanner rather than a confirmed targeted attack, and there is no evidence of a successful login.

• sshdServer 1CriticalAI verdict: malicious1 hitOct 10, 2026, 2:39 PM UTC

Timeline

1. Nov 4, 2026, 9:32 PM UTCLast reported
2. Nov 4, 2026, 9:27 PM UTCsshd Medium
3. Nov 4, 2026, 9:27 PM UTCsshd Low
4. Nov 4, 2026, 9:26 PM UTCsshd Low
5. Nov 3, 2026, 1:18 AM UTCsshd Medium
6. Nov 3, 2026, 1:17 AM UTCsshd Low
7. Nov 3, 2026, 1:16 AM UTCsshd Low
8. Oct 28, 2026, 12:46 AM UTCsshd Low
9. Oct 26, 2026, 1:07 PM UTCsshd Low
10. Oct 26, 2026, 1:07 PM UTCsshd Low
11. Oct 25, 2026, 2:20 AM UTCsshd Low
12. Oct 23, 2026, 11:04 AM UTCsshd Low
13. Oct 13, 2026, 6:51 AM UTCsshd Medium
14. Oct 11, 2026, 2:12 AM UTCsshd Low
15. Oct 11, 2026, 2:12 AM UTCsshd Medium
16. Oct 10, 2026, 2:39 PM UTCsshd Critical
17. Sep 20, 2026, 9:10 AM UTCFirst reported