shieldie.ai

193.32.162.84

Banned

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

Ban ends: Nov 11, 2026, 8:45 AM UTC

41
confidence (0-100)
3
independent servers
3
reporter networks
65
attempts
Why
AI analyst: Active SSH-only brute-forcing across three networks; no wider pattern
Attack types
sshd
First reported
Sep 20, 2026, 9:10 AM UTC
Last reported
Nov 5, 2026, 5:12 AM UTC
Network
AS47890 UNMANAGED LTD
Location
Netherlands

Attacks by type

Attack typeIncidents
sshd12

Incidents by severity: Medium 4, Low 8

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, 5:08 AM UTC

    Recidivist opportunistic SSH credential scanning from 193.32.162.84 (5th ban; 4 earlier in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and was banned for 57600s; consistent with prior untargeted noise.

  • sshdServer 2MediumAI verdict: malicious1 hitNov 5, 2026, 5:08 AM UTC

    Persistent recidivist SSH brute-force from 193.32.162.84 (5th ban, 4 prior in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail, which applied a 57600s firewall ban; the pattern is consistent with automated scanning rather than a confirmed targeted attack, and there is no evidence of a successful login.

  • sshdServer 1LowAI verdict: malicious1 hitNov 4, 2026, 5:40 PM UTC

    Recidivist opportunistic SSH credential scanning from 193.32.162.84 (4th ban; 3 earlier in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and was banned for 28800s; no evidence of successful auth or targeting.

  • sshdServer 2MediumAI verdict: malicious1 hitNov 4, 2026, 8:41 AM UTC

    Persistent recidivist SSH brute-force from 193.32.162.84 (5th ban, 4 prior in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail, which applied a 57600s firewall ban; the pattern fits automated opportunistic scanning, not a targeted attack, and there is no evidence of a successful login.

  • sshdServer 1LowAI verdict: malicious1 hitNov 4, 2026, 8:40 AM UTC

    Recidivist opportunistic SSH credential scanning from 193.32.162.84 (3rd ban; 2 earlier in recidive window) re-tripped shieldie-guard's sshd jail and was banned for 14400s; consistent with prior verdict, no sign of targeted attack or successful auth.

  • sshdServer 1LowAI verdict: malicious1 hitOct 27, 2026, 9:25 PM UTC

    Recidivist opportunistic SSH credential scanning from 193.32.162.84 (3rd ban; 2 earlier in recidive window, refused attempts included) re-tripped shieldie-guard's sshd jail and was banned for 14400s; consistent with untargeted internet noise, not a targeted attack.

  • sshdServer 2MediumAI verdict: malicious1 hitOct 27, 2026, 9:25 PM UTC

    Persistent SSH brute-force from recidivist 193.32.162.84 (5th ban, 4 prior in the recidive window) matched shieldie-guard's 'sshd' jail, which applied a 57600s nftables ban; it is consistent with prior verdicts and looks like automated persistent scanning, not evidence of a targeted compromise.

  • sshdServer 3LowAI verdict: malicious1 hitOct 27, 2026, 9:24 PM UTC

    Persistent recidivist SSH brute-force from 193.32.162.84 (seen since 2026-09-23, 3 prior bans in recidive window) tripped shieldie-guard's sshd jail and received a 28800s ban; pattern matches opportunistic scanning noise, not evidence of a targeted attack or successful login.

  • sshdServer 2MediumAI verdict: malicious1 hitOct 18, 2026, 4:06 AM UTC

    Persistent recidivist SSH brute-force from 193.32.162.84 (6th ban, 5 prior in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail, which applied an escalated 115200s firewall ban; the source has kept coming back for weeks, but there is no evidence of a successful login, so this looks like automated persistent scanning rather than a confirmed targeted compromise.

  • sshdServer 3LowAI verdict: malicious1 hitOct 18, 2026, 4:06 AM UTC

    Persistent recidivist SSH brute-force source 193.32.162.84 (seen since 2026-09-23, now 4th ban in the recidive window) tripped shieldie-guard's sshd jail and got an escalated 28800s firewall ban; this looks like automated scanning noise, not a targeted attack, and nothing shows a successful login.

  • sshdServer 3LowAI verdict: malicious1 hitOct 12, 2026, 11:44 PM UTC

    Recidivist SSH brute-force source 193.32.162.84 (3rd ban in recidive window, previously seen 2026-09-23) tripped shieldie-guard's sshd jail and received a 14400s firewall ban; persistent automated scanning rather than a targeted attack, with no evidence of successful auth.

  • sshdServer 1LowAI verdict: malicious1 hitOct 8, 2026, 5:39 PM UTC

    193.32.162.84 re-tripped shieldie-guard's sshd jail with repeated SSH auth failures after 8 prior bans in the recidive window. shieldie-guard has already applied a 921600s firewall ban. This is persistent automated brute-force noise rather than evidence of a targeted attack, and nothing indicates a successful login.

Timeline

  1. Nov 5, 2026, 5:12 AM UTCLast reported
  2. Nov 5, 2026, 5:08 AM UTCsshd Low
  3. Nov 5, 2026, 5:08 AM UTCsshd Medium
  4. Nov 4, 2026, 5:40 PM UTCsshd Low
  5. Nov 4, 2026, 8:41 AM UTCsshd Medium
  6. Nov 4, 2026, 8:40 AM UTCsshd Low
  7. Oct 27, 2026, 9:25 PM UTCsshd Low
  8. Oct 27, 2026, 9:25 PM UTCsshd Medium
  9. Oct 27, 2026, 9:24 PM UTCsshd Low
  10. Oct 18, 2026, 4:06 AM UTCsshd Medium
  11. Oct 18, 2026, 4:06 AM UTCsshd Low
  12. Oct 12, 2026, 11:44 PM UTCsshd Low
  13. Oct 8, 2026, 5:39 PM UTCsshd Low
  14. Sep 20, 2026, 9:10 AM 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