87.106.87.87

Attacks by type

Incidents by severity: High 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 1HighAI verdict: malicious6 hitsNov 12, 2026, 3:43 AM UTC
• sshdServer 2LowAI verdict: malicious1 hitOct 28, 2026, 3:28 AM UTC

  Repeat SSH brute-force from 87.106.87.87 (second ban, prior on 2026-10-25) plus related 87.106.x.x sources suggest persistent automated scanning from one provider range, contained by shieldie-guard's 7200s escalated ban.

• sshdServer 3LowAI verdict: malicious1 hitOct 26, 2026, 1:37 AM UTC

  Repeated SSH auth failures from 87.106.87.87 (no prior bans in the recidive window) matched shieldie-guard's 'sshd' jail, which applied a 3600s firewall ban; consistent with routine opportunistic scanning (same 87.106.x.x range seen in prior incidents) rather than a targeted attack.

• sshdServer 1LowAI verdict: malicious1 hitOct 25, 2026, 3:52 PM UTC

  Opportunistic SSH credential guessing from 87.106.87.87 (first ban, 0 prior in recidive window) tripped shieldie-guard's sshd jail, which applied a deterministic 3600s firewall ban; it matches the recurring pattern of untargeted scanning from the [addr]/16 range.

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

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

Timeline

1. Nov 12, 2026, 3:46 AM UTCLast reported
2. Nov 12, 2026, 3:43 AM UTCsshd High
3. Oct 28, 2026, 3:28 AM UTCsshd Low
4. Oct 26, 2026, 1:37 AM UTCsshd Low
5. Oct 25, 2026, 3:52 PM UTCsshd Low
6. Oct 25, 2026, 11:00 AM UTCFirst reported
7. Oct 25, 2026, 10:58 AM UTCsshd Low