There was a successful sign-in from this address, and the same address was flagged by other defences — or a file check, the antivirus or a newly opened port fired right after it. Worth confirming that the sign-in was yours.
| Time | Severity | Source | Message | Count |
|---|---|---|---|---|
| 13.10.2026 04:13 | Warning | ssh |
SSH: login from a new address deploy@198.51.100.32
|
1 |
| 13.10.2026 08:29 | Warning | fail2ban |
Fail2ban: new bans 198.51.100.31, 198.51.100.32, 198.51.100.33, 198.51.100.34
|
8 |
Events that carry no address: their source does not know who did it. Shown for the span this address was active, plus six hours after it.
| 13.10.2026 04:39 | Critical | falco |
Falco: critical events Read of sensitive file /etc/shadow
|
| 13.10.2026 08:43 | Critical | service | Protection service stopped: suricata |