shieldie.ai

20.235.157.149

Banned

On the shared blocklist: servers in the shieldie network block it.

Ban ends: Nov 6, 2026, 2:40 AM UTC

41
confidence (0-100)
3
independent servers
3
reporter networks
25
attempts
Why
AI analyst: SSH-only brute-forcing across three networks, no subnet activity
Attack types
sshd
First reported
Oct 3, 2026, 7:32 PM UTC
Last reported
Nov 5, 2026, 2:40 AM UTC
Network
AS8075 Microsoft Corporation
Location
India

Attacks by type

Attack typeIncidents
sshd4

Incidents by severity: Medium 1, Low 3

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, 2:37 AM UTC

    Recidivist opportunistic SSH brute-force from 20.235.157.149 (2nd ban: 1 earlier in the recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail, which applied a deterministic 7200s firewall ban; the pattern matches untargeted internet noise, not a targeted attack.

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

    Recidivist SSH brute-force from 20.235.157.149 (1 prior ban in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail, which applied a 7200s firewall ban; consistent with opportunistic automated scanning rather than a targeted attack.

  • sshdServer 1LowAI verdict: malicious1 hitOct 26, 2026, 10:34 PM UTC

    Recidivist opportunistic SSH brute-force from 20.235.157.149 (3rd ban, 2 earlier in the recidive window) re-tripped shieldie-guard's sshd jail and received a 14400s firewall ban; consistent with untargeted credential scanning, no evidence of successful auth.

  • sshdServer 3LowAI verdict: malicious1 hitOct 19, 2026, 10:25 PM UTC

    Repeat SSH brute-force from 20.235.157.149 (second ban; previously banned 2026-10-03) tripped shieldie-guard's sshd jail, which applied an escalated 7200s firewall ban with attempts refused; it looks like persistent opportunistic scanning, not a targeted attack.

Timeline

  1. Nov 5, 2026, 2:40 AM UTCLast reported
  2. Nov 5, 2026, 2:37 AM UTCsshd Low
  3. Oct 29, 2026, 2:06 PM UTCsshd Medium
  4. Oct 26, 2026, 10:34 PM UTCsshd Low
  5. Oct 19, 2026, 10:25 PM UTCsshd Low
  6. Oct 3, 2026, 7:32 PM UTCFirst reported

Shown: attack type, severity, AI verdict and a short redacted summary as reported by shieldie servers. Server names, addresses, user names and log lines are never published.

New search