shieldie.ai

201.124.171.198

Reported

Reported, waiting for confirmation by more independent servers.

34
confidence (0-100)
2
independent servers
2
reporter networks
38
attempts
Attack types
sshd
First reported
Nov 1, 2026, 1:39 AM UTC
Last reported
Nov 5, 2026, 6:22 AM UTC
Network
AS8151 Uninet S.A. de C.V.
Location
Mexico

Attacks by type

Attack typeIncidents
sshd7

Incidents by severity: Medium 1, Low 6

Incidents

These incidents come from 2 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, 6:19 AM UTC

    Persistent recidivist opportunistic SSH brute-force from 201.124.171.198 (5th ban, 4 prior in recidive window) re-tripped shieldie-guard's sshd jail, which applied an escalated 57600s firewall ban; no evidence of successful auth or targeting.

  • sshdServer 1LowAI verdict: malicious1 hitNov 4, 2026, 7:33 PM UTC

    Persistent opportunistic SSH brute-force from recidivist 201.124.171.198 (4th ban; prior bans incl. 2026-11-01 and 2026-11-04) re-tripped shieldie-guard's sshd jail, which applied an escalated 28800s firewall ban; no sign of successful auth or targeting beyond repeated noise.

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

    Recidivist opportunistic SSH brute-force from 201.124.171.198 (3rd ban in recidive window, consistent with prior 2026-11-01 and 2026-11-04 incidents) re-tripped shieldie-guard's sshd jail, which applied an escalated 14400s firewall ban; persistent but untargeted noise, no evidence of successful auth.

  • sshdServer 1LowAI verdict: malicious1 hitNov 4, 2026, 6:31 AM UTC

    Recidivist opportunistic SSH brute-force from 201.124.171.198 (2nd ban; same source previously banned 2026-11-01) re-tripped shieldie-guard's sshd jail, which applied an escalated 7200s firewall ban; consistent with untargeted noise, no evidence of successful auth.

  • sshdServer 2MediumAI verdict: malicious1 hitNov 1, 2026, 11:07 AM UTC

    Recidivist SSH brute-force from 201.124.171.198 (1 prior ban in the recidive window, consistent with the earlier 2026-11-01 3600s ban) resumed repeated auth failures and was banned again for 7200s by shieldie-guard's 'sshd' jail; the pattern looks like persistent automated scanning, not a targeted attack.

  • sshdServer 2LowAI verdict: malicious1 hitNov 1, 2026, 7:14 AM UTC

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

  • sshdServer 1LowAI verdict: malicious1 hitNov 1, 2026, 1:36 AM UTC

    Untargeted SSH brute-force noise: repeated auth failures from 201.124.171.198 tripped shieldie-guard's sshd jail, which applied a deterministic 3600s firewall ban; first ban of this address (0 prior in recidive window), consistent with prior similar incidents.

Timeline

  1. Nov 5, 2026, 6:22 AM UTCLast reported
  2. Nov 5, 2026, 6:19 AM UTCsshd Low
  3. Nov 4, 2026, 7:33 PM UTCsshd Low
  4. Nov 4, 2026, 2:04 PM UTCsshd Low
  5. Nov 4, 2026, 6:31 AM UTCsshd Low
  6. Nov 1, 2026, 11:07 AM UTCsshd Medium
  7. Nov 1, 2026, 7:14 AM UTCsshd Low
  8. Nov 1, 2026, 1:39 AM UTCFirst reported
  9. Nov 1, 2026, 1:36 AM UTCsshd Low

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