shieldie.ai

12.156.67.18

Banned

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

Ban ends: Nov 5, 2026, 7:38 AM UTC

41
confidence (0-100)
3
independent servers
3
reporter networks
47
attempts
Why
AI analyst: SSH-only brute-force across 3 networks; ordinary, no subnet activity
Attack types
sshd
First reported
Sep 28, 2026, 12:37 AM UTC
Last reported
Nov 4, 2026, 1:09 PM UTC
Network
AS7018 AT&T Enterprises, LLC
Location
United States

Attacks by type

Attack typeIncidents
sshd7

Incidents by severity: Medium 3, 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 1LowAI verdict: malicious1 hitNov 4, 2026, 1:07 PM UTC

    Persistent recidivist SSH brute-force from 12.156.67.18 (4th ban, 3 earlier in recidive window); shieldie-guard's sshd jail applied an escalated 28800s firewall ban, consistent with automated persistent scanning rather than a confirmed targeted compromise.

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

    Recidivist SSH brute-force from 12.156.67.18 (3rd ban: 2 earlier bans in the recidive window, refused attempts included); shieldie-guard's sshd jail applied an escalated 14400s firewall ban, and the pattern is consistent with persistent opportunistic noise rather than a targeted attack.

  • sshdServer 1LowAI verdict: malicious1 hitNov 1, 2026, 3:45 PM UTC

    Repeated SSH auth failures from 12.156.67.18 tripped shieldie-guard's sshd jail, which applied an escalated 7200s firewall ban; this is a repeat offender (1 earlier ban in the recidive window) but the pattern matches untargeted brute-force noise, not a targeted attack.

  • sshdServer 2LowAI verdict: malicious1 hitOct 29, 2026, 3:22 PM UTC

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

  • sshdServer 3MediumAI verdict: malicious1 hitOct 29, 2026, 11:05 AM UTC

    Persistent recidivist SSH brute-force from 12.156.67.18 (3rd ban in the recidive window, consistent with 2026-10-21 and 2026-10-28 incidents) was contained by shieldie-guard's 'sshd' jail with an escalated 14400s firewall ban; the pattern indicates a persistent automated attacker, and no successful login is evidenced.

  • sshdServer 3MediumAI verdict: malicious1 hitOct 28, 2026, 7:49 AM UTC

    Recidivist SSH brute-force from 12.156.67.18 (1 prior ban in the recidive window, consistent with the 2026-10-21 incident) resumed repeated auth failures and was banned for 7200s by shieldie-guard's 'sshd' jail; pattern indicates persistent automated scanning rather than a confirmed targeted attack.

  • sshdServer 3MediumAI verdict: malicious1 hitOct 21, 2026, 11:22 PM UTC

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

Timeline

  1. Nov 4, 2026, 1:09 PM UTCLast reported
  2. Nov 4, 2026, 1:07 PM UTCsshd Low
  3. Nov 4, 2026, 7:36 AM UTCsshd Low
  4. Nov 1, 2026, 3:45 PM UTCsshd Low
  5. Oct 29, 2026, 3:22 PM UTCsshd Low
  6. Oct 29, 2026, 11:05 AM UTCsshd Medium
  7. Oct 28, 2026, 7:49 AM UTCsshd Medium
  8. Oct 21, 2026, 11:22 PM UTCsshd Medium
  9. Sep 28, 2026, 12:37 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