45.148.10.151

Attacks by type

Incidents by severity: Medium 16, Low 7

Incidents

The 20 newest of 23 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, 2:52 PM UTC

  45.148.10.151 is a persistent SSH brute-forcer (6th ban, 5 prior in the recidive window, refused attempts included) from the [addr]/24 range; this is automated, persistent scanning, not a targeted attack, and shieldie-guard has already applied a 115200s ban.

• sshdServer 2LowAI verdict: malicious1 hitNov 4, 2026, 8:30 AM UTC

  same as 92a32d76: Recidivist opportunistic SSH credential guessing from [addr] (7th ban; 6 earlier bans in recidive window) re-tripped shieldie-guard's sshd jail and was firewall-banned for 230400s; consistent with prior untargeted noise, no evidence of successful auth.

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

  45.148.10.151 is a persistent SSH brute-forcer (5th ban in the recidive window, refused attempts included) from the [addr]/24 range seen repeatedly in prior incidents; automated untargeted noise, already contained by shieldie-guard's 57600s ban.

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

  45.148.10.151 is a persistent SSH brute-forcer (4th ban in the recidive window, refused attempts included) from the [addr]/24 range seen repeatedly in prior incidents. It is opportunistic, recurring automated scanning, not evidence of a targeted compromise; shieldie-guard applied a 28800s firewall ban.

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

  45.148.10.151 is a repeat SSH brute-forcer (3rd ban in the recidive window, refused attempts included) from the [addr]/24 range tied to prior persistent sshd incidents; shieldie-guard applied a 14400s firewall ban. This looks like organized opportunistic scanning, not a targeted attack.

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

  45.148.10.151 is a repeat SSH brute-forcer (2nd ban in the recidive window, refused attempts included) from the [addr]/24 range behind prior persistent sshd incidents; automated campaign noise rather than a targeted attack, already contained by shieldie-guard's 7200s ban.

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

  Persistent recidivist 45.148.10.151 (8th ban in recidive window, escalating from 1 to 3 to 7 prior bans; adjacent [addr] also seen) keeps brute-forcing SSH; shieldie-guard's 'sshd' jail applied a 460800s ban, which looks like automated [path] activity from one hosting range rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitNov 1, 2026, 4:15 PM UTC

  same as e1931361: Recidivist opportunistic SSH credential guessing from [addr] (7th ban; 6 earlier bans in recidive window) re-tripped shieldie-guard's sshd jail and was firewall-banned for 230400s; consistent with prior verdicts, no sign of a targeted attack or successful login.

• sshdServer 2LowAI verdict: malicious1 hitOct 31, 2026, 7:15 AM UTC

  same as 65ec66e4: Recidivist opportunistic SSH credential guessing from [addr] (6th ban; 5 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and drew a 115200s firewall ban; the pattern fits persistent automated scanning from the [addr]/24 range rather than a targeted attack.

• sshdServer 3MediumAI verdict: malicious1 hitOct 31, 2026, 3:18 AM UTC

  Persistent recidivist 45.148.10.151 (6 prior bans in the recidive window, escalating from 1 and 3 in earlier incidents) again tripped shieldie-guard's 'sshd' jail; automated brute-force campaign from the [addr]/24 range rather than a targeted attack, now contained by a 230400s firewall ban.

• sshdServer 3MediumAI verdict: malicious1 hitOct 29, 2026, 7:02 PM UTC

  Recidivist 45.148.10.151 (5 earlier bans in the recidive window) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 115200s firewall ban; persistent automated brute-force rather than evidence of a targeted compromise.

• sshdServer 3MediumAI verdict: malicious1 hitOct 29, 2026, 2:59 AM UTC

  Recidivist 45.148.10.151 (4 earlier bans in the recidive window) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 57600s firewall ban; persistent automated brute-force rather than a targeted attack, consistent with prior verdicts.

• sshdServer 3MediumAI verdict: malicious1 hitOct 28, 2026, 6:06 PM UTC

  Recidivist 45.148.10.151 (3 earlier bans in the recidive window, refused attempts included) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 28800s firewall ban; persistent automated brute-force consistent with prior verdicts rather than a confirmed targeted attack.

• sshdServer 3MediumAI verdict: malicious1 hitOct 28, 2026, 9:28 AM UTC

  Recidivist 45.148.10.151 (2 earlier bans in the recidive window) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 14400s firewall ban; persistent automated brute-force rather than random noise, though there is no evidence of successful auth.

• sshdServer 3MediumAI verdict: malicious1 hitOct 28, 2026, 7:24 AM UTC

  Recidivist 45.148.10.151 (1 earlier ban in the recidive window) again tripped shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 7200s firewall ban; consistent with automated brute-force from the [addr]/24 range seen in prior incidents rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 24, 2026, 10:38 PM UTC

  same as 698dec34: Recidivist opportunistic SSH credential guessing from [addr] (4th ban; 3 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; the pattern is consistent with automated scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 24, 2026, 1:15 PM UTC

  same as 4e11d4a0: Recidivist opportunistic SSH credential guessing from [addr] (4th ban; 3 earlier bans in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; consistent with untargeted noise, no evidence of successful auth.

• sshdServer 2LowAI verdict: malicious1 hitOct 24, 2026, 9:09 AM UTC

  same as 1121665a: Recidivist opportunistic SSH credential guessing from [addr] (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 activity from the same /24, not a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 24, 2026, 7:03 AM UTC

  same as ec98dcf4: Recidivist opportunistic SSH credential guessing from [addr] (2nd ban; 1 earlier ban in the recidive window) re-tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; the pattern matches untargeted internet scanning, consistent with prior similar incidents (including neighboring [addr]).

• sshdServer 1MediumAI verdict: malicious1 hitOct 12, 2026, 1:12 PM UTC

  45.148.10.151 is a persistent SSH brute-forcer that tripped shieldie-guard's sshd jail again; this is the 10th ban in the recidive window, and shieldie-guard escalated it to a 1843200s (~21-day) firewall ban; it is persistent automated scanning rather than evidence of a targeted compromise.

Timeline

1. Nov 4, 2026, 2:55 PM UTCLast reported
2. Nov 4, 2026, 2:52 PM UTCsshd Medium
3. Nov 4, 2026, 8:30 AM UTCsshd Low
4. Nov 3, 2026, 10:31 PM UTCsshd Medium
5. Nov 3, 2026, 1:31 PM UTCsshd Medium
6. Nov 3, 2026, 6:44 AM UTCsshd Medium
7. Nov 3, 2026, 4:25 AM UTCsshd Medium
8. Nov 2, 2026, 7:29 PM UTCsshd Medium
9. Nov 1, 2026, 4:15 PM UTCsshd Low
10. Oct 31, 2026, 7:15 AM UTCsshd Low
11. Oct 31, 2026, 3:18 AM UTCsshd Medium
12. Oct 29, 2026, 7:02 PM UTCsshd Medium
13. Oct 29, 2026, 2:59 AM UTCsshd Medium
14. Oct 28, 2026, 6:06 PM UTCsshd Medium
15. Oct 28, 2026, 9:28 AM UTCsshd Medium
16. Oct 28, 2026, 7:24 AM UTCsshd Medium
17. Oct 24, 2026, 10:38 PM UTCsshd Low
18. Oct 24, 2026, 1:15 PM UTCsshd Low
19. Oct 24, 2026, 9:09 AM UTCsshd Low
20. Oct 24, 2026, 7:03 AM UTCsshd Low
21. Oct 12, 2026, 1:12 PM UTCsshd Medium
22. Sep 20, 2026, 1:57 PM UTCFirst reported