45.78.204.246

Attacks by type

Incidents by severity: Medium 1, Low 4

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 12, 2026, 2:35 AM UTC
• sshdServer 2LowAI verdict: malicious1 hitNov 4, 2026, 3:48 PM UTC

  Recidivist opportunistic SSH brute-force from 45.78.204.246 (5th ban; 4 earlier in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a 57600s firewall ban; consistent with internet-wide noise, not a targeted attack.

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

  Persistent repeat offender 45.78.204.246 (4th ban in recidive window, also seen [path]; neighboring [addr] seen 2026-10-22) again tripped shieldie-guard's sshd jail and was given a 28800s firewall ban; the pattern indicates automated, persistent brute-force from the 45.78.x.x range rather than a targeted attack, with no evidence of successful auth.

• sshdServer 2LowAI verdict: malicious1 hitOct 17, 2026, 8:20 PM UTC

  Repeat offender 45.78.204.246 (2 earlier bans in the recidive window, previously seen [path]) again tripped shieldie-guard's sshd jail with repeated SSH auth failures and received an escalated 14400s ban; this looks like persistent automated brute-force noise, not a targeted attack, with no evidence of a successful login.

• sshdServer 3LowAI verdict: malicious1 hitOct 14, 2026, 3:34 AM UTC

  First-time source 45.78.204.246 (0 prior bans in the recidive window) triggered shieldie-guard's 'sshd' jail on repeated SSH auth failures and received a 3600s firewall ban; consistent with opportunistic brute-force noise, though the [path] range has recurred in prior incidents.

Timeline

1. Nov 12, 2026, 2:37 AM UTCLast reported
2. Nov 12, 2026, 2:35 AM UTCsshd Medium
3. Nov 4, 2026, 3:48 PM UTCsshd Low
4. Oct 24, 2026, 3:18 AM UTCsshd Low
5. Oct 17, 2026, 8:20 PM UTCsshd Low
6. Oct 14, 2026, 3:34 AM UTCsshd Low
7. Oct 7, 2026, 8:29 AM UTCFirst reported