193.47.62.69

Attacks by type

Incidents by severity: Medium 9, Low 14

Incidents

The 20 newest of 23 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 1MediumAI verdict: malicious1 hitNov 5, 2026, 12:09 AM UTC

  Persistent recidivist SSH brute-force from 193.47.62.69 (7 prior bans in recidive window, seen since 2026-10-22) matched shieldie-guard's 'sshd' jail and was banned for 460800s; consistent with prior [path] verdicts and no evidence of successful auth.

• sshdServer 2LowAI verdict: malicious1 hitNov 4, 2026, 11:47 PM UTC

  Persistent untargeted SSH brute-force from known recidivist 193.47.62.69 (5 earlier bans in recidive window) tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban; consistent with prior noise-level verdicts.

• sshdServer 2LowAI verdict: malicious1 hitNov 4, 2026, 7:10 AM UTC

  Persistent automated SSH brute-force from known recidivist 193.47.62.69 (4 prior bans in recidive window, repeatedly seen since 2026-10-12) tripped shieldie-guard's sshd jail, which applied a 57600s ban; the pattern looks like opportunistic scanning noise rather than a targeted attack, and the evidence shows no successful login.

• sshdServer 2LowAI verdict: malicious1 hitNov 3, 2026, 10:18 PM UTC

  Persistent untargeted SSH brute-force from known recidivist 193.47.62.69 (3 earlier bans in recidive window, prior ~21-day escalation on 2026-10-12) tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; consistent with automated scanning noise rather than a targeted attack.

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

  Repeat SSH brute-force from known recidivist 193.47.62.69 (2 earlier bans in recidive window, previously escalated to a ~21-day ban on 2026-10-12) tripped shieldie-guard's sshd jail, which applied a 14400s firewall ban; the pattern is consistent with persistent automated scanning, not a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitNov 3, 2026, 5:25 AM UTC

  Repeat SSH brute-force from 193.47.62.69 (1 prior ban in recidive window; the same address was previously recorded on 2026-10-12 at its 10th ban) tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban. This looks like a persistent opportunistic scanner, not a targeted attack.

• sshdServer 1MediumAI verdict: malicious1 hitNov 2, 2026, 8:05 AM UTC

  Persistent recidivist SSH brute-force from 193.47.62.69 (7th ban, 6 prior in recidive window, seen since 2026-10-22) matched shieldie-guard's 'sshd' jail and was banned for 230400s (64h); likely automated, not targeted, with no evidence of successful auth.

• sshdServer 1MediumAI verdict: malicious1 hitOct 31, 2026, 8:51 PM UTC

  Persistent recidivist SSH brute-force from 193.47.62.69 (5 prior bans in recidive window, seen since 2026-10-22) matched shieldie-guard's 'sshd' jail and was banned for 115200s; this pattern looks like sustained automated scanning, not a targeted compromise.

• sshdServer 1MediumAI verdict: malicious1 hitOct 30, 2026, 12:19 PM UTC

  Persistent recidivist SSH brute-force from 193.47.62.69 (5 prior bans in recidive window, seen since 2026-10-22) matched shieldie-guard's 'sshd' jail and was banned for 115200s; the sustained single-source persistence suggests a targeted or dedicated scanner rather than random noise, with no evidence of successful auth.

• sshdServer 1MediumAI verdict: malicious1 hitOct 29, 2026, 8:08 PM UTC

  Persistent recidivist SSH brute-force from 193.47.62.69 (4 prior bans in recidive window, seen since 2026-10-22) matched shieldie-guard's 'sshd' jail and was banned for 57600s; pattern indicates automated, persistent scanning rather than a confirmed targeted compromise.

• sshdServer 3LowAI verdict: malicious1 hitOct 27, 2026, 4:09 AM UTC

  Recidivist opportunistic SSH credential scanning from 193.47.62.69 (7th ban; 6 earlier bans in the recidive window, consistent with prior incidents) re-tripped shieldie-guard's sshd jail, which applied a 230400s firewall ban; no evidence of a targeted attack or successful login.

• sshdServer 3LowAI verdict: malicious1 hitOct 25, 2026, 6:50 PM UTC

  Recidivist opportunistic SSH credential scanning from 193.47.62.69 (6th ban; 5 earlier bans in the recidive window, consistent with prior incidents) re-tripped shieldie-guard's sshd jail, which applied a 115200s firewall ban; the pattern indicates persistent automated noise, not a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 25, 2026, 2:01 AM UTC

  Recidivist opportunistic SSH credential scanning from 193.47.62.69 (5th ban; 4 earlier bans in the recidive window, consistent with prior incidents) re-tripped shieldie-guard's sshd jail, which applied a 57600s firewall ban; no evidence of a targeted attack or successful login.

• sshdServer 3LowAI verdict: malicious1 hitOct 24, 2026, 5:09 PM UTC

  Recidivist opportunistic SSH credential scanning from 193.47.62.69 (4th ban; 3 earlier bans in the recidive window, consistent with prior incidents) re-tripped shieldie-guard's sshd jail, which applied a 28800s firewall ban; the pattern indicates persistent automated noise rather than a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 24, 2026, 1:08 PM UTC

  Recidivist opportunistic SSH credential scanning from 193.47.62.69 (3rd ban; 2 earlier bans in the recidive window, consistent with its prior incident) re-tripped shieldie-guard's sshd jail, which applied a 14400s firewall ban; it looks like persistent untargeted scanning, not a targeted attack.

• sshdServer 3LowAI verdict: malicious1 hitOct 24, 2026, 7:59 AM UTC

  Recidivist opportunistic SSH credential scanning from 193.47.62.69 (2nd ban; 1 earlier ban in the recidive window) re-tripped shieldie-guard's sshd jail, which applied a 7200s firewall ban; no evidence of successful auth or targeting.

• sshdServer 1MediumAI verdict: malicious1 hitOct 23, 2026, 9:03 AM UTC

  Persistent recidivist SSH brute-force from 193.47.62.69: this is its 4th ban by shieldie-guard's 'sshd' jail (3 prior in the recidive window, seen 2026-10-22 and 2026-10-23); it now carries a 28800s firewall ban. The behavior is persistent automated scanning, and nothing in the evidence shows targeting or a successful login.

• sshdServer 1MediumAI verdict: malicious1 hitOct 23, 2026, 12:47 AM UTC

  Recidivist SSH brute-force from 193.47.62.69 (2 prior bans in recidive window, previously seen 2026-10-22) matched shieldie-guard's 'sshd' jail and was banned for 14400s; persistent automated scanning rather than evidence of a targeted attack or compromise.

• sshdServer 1MediumAI verdict: malicious1 hitOct 22, 2026, 6:08 PM UTC

  Repeat SSH brute-force from recidivist 193.47.62.69 (1 prior ban in the recidive window, refused attempts included) matched shieldie-guard's 'sshd' jail and was banned for 7200s; consistent with opportunistic internet-wide scanning rather than a targeted attack.

• sshdServer 2LowAI verdict: malicious1 hitOct 12, 2026, 1:23 PM UTC

  Persistent SSH brute-force from 193.47.62.69 (10th ban in recidive window) tripped shieldie-guard's sshd jail, which applied an escalated 1843200s (~21-day) firewall ban; the pattern matches prior low-severity verdicts and shows automated, persistent scanning with no evidence of a successful login.

Timeline

1. Nov 5, 2026, 12:14 AM UTCLast reported
2. Nov 5, 2026, 12:09 AM UTCsshd Medium
3. Nov 4, 2026, 11:47 PM UTCsshd Low
4. Nov 4, 2026, 7:10 AM UTCsshd Low
5. Nov 3, 2026, 10:18 PM UTCsshd Low
6. Nov 3, 2026, 1:03 PM UTCsshd Low
7. Nov 3, 2026, 5:25 AM UTCsshd Low
8. Nov 2, 2026, 8:05 AM UTCsshd Medium
9. Oct 31, 2026, 8:51 PM UTCsshd Medium
10. Oct 30, 2026, 12:19 PM UTCsshd Medium
11. Oct 29, 2026, 8:08 PM UTCsshd Medium
12. Oct 27, 2026, 4:09 AM UTCsshd Low
13. Oct 25, 2026, 6:50 PM UTCsshd Low
14. Oct 25, 2026, 2:01 AM UTCsshd Low
15. Oct 24, 2026, 5:09 PM UTCsshd Low
16. Oct 24, 2026, 1:08 PM UTCsshd Low
17. Oct 24, 2026, 7:59 AM UTCsshd Low
18. Oct 23, 2026, 9:03 AM UTCsshd Medium
19. Oct 23, 2026, 12:47 AM UTCsshd Medium
20. Oct 22, 2026, 6:08 PM UTCsshd Medium
21. Oct 12, 2026, 1:23 PM UTCsshd Low
22. Sep 20, 2026, 1:47 PM UTCFirst reported