45.148.10.157

Attacks by type

Incidents by severity: Critical 1, Medium 13, Low 8

Incidents

The 20 newest of 22 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 5, 2026, 1:06 AM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (8th ban; 7 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 460800s firewall ban; the pattern matches prior analyses (noise, not a targeted attack), and nothing indicates a successful login.

• sshdServer 2MediumAI verdict: malicious1 hitNov 4, 2026, 3:25 PM UTC

  45.148.10.157 is a persistent SSH brute-forcer (5th ban in the recidive window, refused attempts included) from the [addr]/24 range repeatedly seen in prior incidents; shieldie-guard applied a 57600s firewall ban.

• sshdServer 2MediumAI verdict: malicious1 hitNov 4, 2026, 7:02 AM UTC

  45.148.10.157 is a persistent SSH brute-forcer (4th ban in the recidive window, refused attempts included) from the [addr]/24 range repeatedly seen in prior incidents; automated campaign noise rather than a targeted attack, already contained by shieldie-guard's 28800s ban.

• sshdServer 3MediumAI verdict: malicious1 hitNov 4, 2026, 12:56 AM UTC

  Recidivist 45.148.10.157 (7th ban in recidive window; same /24 as other recidivist [addr]) again tripped shieldie-guard's 'sshd' jail with repeated SSH auth failures; shieldie-guard applied a 230400s firewall ban — persistent automated brute-force, not evidence of a targeted compromise.

• sshdServer 2MediumAI verdict: malicious1 hitNov 3, 2026, 11:18 PM UTC

  45.148.10.157 is a repeat SSH brute-forcer (3rd ban in the recidive window, refused attempts included) from the [addr]/24 range tied to prior persistent incidents; automated campaign noise rather than evidence of a targeted compromise, now banned 14400s by shieldie-guard.

• sshdServer 2MediumAI verdict: malicious1 hitNov 3, 2026, 2:19 PM UTC

  45.148.10.157 is a repeat SSH brute-forcer (2nd ban in the recidive window, refused attempts included) from the [addr]/24 range behind prior persistent incidents, consistent with coordinated opportunistic scanning rather than a targeted attack; shieldie-guard applied a 7200s firewall ban.

• sshdServer 3MediumAI verdict: malicious1 hitNov 2, 2026, 4:56 PM UTC

  Recidivist 45.148.10.157 (5 earlier bans in the recidive window, refused attempts included) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures; persistent automated brute-force rather than random noise, already mitigated by a 115200s firewall ban.

• sshdServer 3MediumAI verdict: malicious1 hitNov 1, 2026, 10:40 PM UTC

  Recidivist 45.148.10.157 (4 earlier bans in the recidive window, refused attempts included) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures. This looks like persistent automated brute-force from a [addr]/24 cluster (sibling .141 was seen too), not a targeted attack, and shieldie-guard applied a 57600s ban.

• sshdServer 3MediumAI verdict: malicious1 hitNov 1, 2026, 1:27 PM UTC

  same as 38d27555: Recidivist [addr] (5 earlier bans in the recidive window) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures; this is a persistent automated brute-force rather than a targeted attack, and no successful login was reported.

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

  Recidivist 45.148.10.157 (2 earlier bans in the recidive window, refused attempts included) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures, and shieldie-guard applied a 14400s firewall ban. Neighbouring 45.148.10.x addresses show the same pattern, which points to a persistent automated campaign from that range rather than a host-specific targeted attack.

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

  Recidivist 45.148.10.157 (1 earlier ban in the recidive window, refused attempts included) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 7200s firewall ban; it belongs to the same [addr]/24 range seen in prior recidivist incidents (.141, .151), which points to persistent automated brute-force from one source network rather than random noise or an attack targeted at this host specifically.

• sshdServer 1LowAI verdict: malicious1 hitOct 30, 2026, 2:32 PM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (8th ban; 7 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 460800s firewall ban; the pattern matches prior noise-level verdicts and gives no sign of a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 27, 2026, 10:19 PM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (7th ban; 6 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 230400s firewall ban; the pattern matches prior noise-level scanning, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 26, 2026, 12:06 PM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (6th ban; 5 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban; the pattern is consistent with persistent automated scanning rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 25, 2026, 8:05 PM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (5th ban; 4 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 57600s firewall ban; the pattern is consistent with untargeted noise, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 25, 2026, 11:28 AM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (4th ban; 3 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 28800s nftables ban; consistent with untargeted scanning noise, not a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 25, 2026, 7:16 AM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (3rd ban; 2 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 14400s firewall ban; the pattern matches prior scanner noise from the [addr]/24 range rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 25, 2026, 3:43 AM UTC

  Recidivist opportunistic SSH credential guessing from 45.148.10.157 (2nd ban; 1 earlier ban in the recidive window) re-tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; same [addr]/24 range as prior incidents, consistent with untargeted scanning noise.

• sshdServer 2MediumAI verdict: malicious1 hitOct 12, 2026, 10:06 PM UTC

  45.148.10.157 is a persistent SSH brute-forcer (10th ban in the recidive window, refused attempts included) from the same [addr]/24 range seen in prior sshd and nginx-exploit incidents; shieldie-guard's sshd jail applied a 1843200s (~21-day) firewall ban. This looks like coordinated, recurring [path] noise from a hostile range rather than an attack targeted at this host.

• sshdServer 3CriticalAI verdict: malicious1 hitOct 9, 2026, 2:34 PM UTC

Timeline

1. Nov 5, 2026, 1:11 AM UTCLast reported
2. Nov 5, 2026, 1:06 AM UTCsshd Low
3. Nov 4, 2026, 3:25 PM UTCsshd Medium
4. Nov 4, 2026, 7:02 AM UTCsshd Medium
5. Nov 4, 2026, 12:56 AM UTCsshd Medium
6. Nov 3, 2026, 11:18 PM UTCsshd Medium
7. Nov 3, 2026, 2:19 PM UTCsshd Medium
8. Nov 2, 2026, 4:56 PM UTCsshd Medium
9. Nov 1, 2026, 10:40 PM UTCsshd Medium
10. Nov 1, 2026, 1:27 PM UTCsshd Medium
11. Nov 1, 2026, 6:41 AM UTCsshd Medium
12. Nov 1, 2026, 4:27 AM UTCsshd Medium
13. Oct 30, 2026, 2:32 PM UTCsshd Low
14. Oct 27, 2026, 10:19 PM UTCsshd Low
15. Oct 26, 2026, 12:06 PM UTCsshd Low
16. Oct 25, 2026, 8:05 PM UTCsshd Low
17. Oct 25, 2026, 11:28 AM UTCsshd Low
18. Oct 25, 2026, 7:16 AM UTCsshd Low
19. Oct 25, 2026, 3:43 AM UTCsshd Low
20. Oct 12, 2026, 10:06 PM UTCsshd Medium
21. Oct 9, 2026, 2:34 PM UTCsshd Critical
22. Sep 20, 2026, 1:07 PM UTCFirst reported