This IP address has been reported a total of
28
times from
13 distinct
sources.
81.213.158.164 was first reported on
, and the most recent report was
.
Recent Reports:
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
2026-09-01T19:44:30.602626-04:00 site sshd-session[181243]: Invalid user quarkus from 81.213.158.164 ...
show more2026-09-01T19:44:30.602626-04:00 site sshd-session[181243]: Invalid user quarkus from 81.213.158.164 port 40234
2026-09-01T22:01:02.447564-04:00 site sshd-session[181767]: Invalid user apy from 81.213.158.164 port 60695
2026-09-02T02:35:22.190027-04:00 site sshd-session[182818]: Invalid user dynamodb from 81.213.158.164 port 45506
...
show less
2026-09-01T20:47:21.936541 telos sshd[3879326]: Invalid user xtz from 81.213.158.164 port 59502
2026 ...
show more2026-09-01T20:47:21.936541 telos sshd[3879326]: Invalid user xtz from 81.213.158.164 port 59502
2026-09-01T23:02:06.158708 telos sshd[3882145]: Invalid user efnet from 81.213.158.164 port 51654
2026-09-02T01:17:52.580114 telos sshd[3883083]: Invalid user quarkus from 81.213.158.164 port 43888
show less
2026-09-01T20:20:56.138804+00:00 sgp01 sshd[1419954]: Invalid user xtz from 81.213.158.164 port 4702 ...
show more2026-09-01T20:20:56.138804+00:00 sgp01 sshd[1419954]: Invalid user xtz from 81.213.158.164 port 47028
2026-09-01T21:44:32.462279+00:00 sgp01 sshd[1423778]: Invalid user efnet from 81.213.158.164 port 45495
2026-09-01T22:35:24.545814+00:00 sgp01 sshd[1425728]: Invalid user efnet from 81.213.158.164 port 39198
2026-09-01T23:59:41.613710+00:00 sgp01 sshd[1429452]: Invalid user quarkus from 81.213.158.164 port 37721
2026-09-02T00:50:57.997173+00:00 sgp01 sshd[1431586]: Invalid user quarkus from 81.213.158.164 port 59651
...
show less
Automated sensor: 21 SSH brute-force attempts over the last 24h (latest 2026-09-01T19:07Z). Username ...
show moreAutomated sensor: 21 SSH brute-force attempts over the last 24h (latest 2026-09-01T19:07Z). Usernames tried: root, 161.35.112, dot, wallet.
show less
2026-09-01T10:44:03.711563shield sshd\[28768\]: Invalid user crypto from 81.213.158.164 port 55271
2 ...
show more2026-09-01T10:44:03.711563shield sshd\[28768\]: Invalid user crypto from 81.213.158.164 port 55271
2026-09-01T10:44:03.863829shield sshd\[28768\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=nukserver.nukleer.com.tr
2026-09-01T10:44:06.196810shield sshd\[28768\]: Failed password for invalid user crypto from 81.213.158.164 port 55271 ssh2
2026-09-01T10:52:00.035858shield sshd\[30375\]: Invalid user crypto from 81.213.158.164 port 51764
2026-09-01T10:52:00.172789shield sshd\[30375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=nukserver.nukleer.com.tr
show less
2026-08-31T12:44:39.215396-04:00 site sshd-session[160198]: Invalid user 208.68.39 from 81.213.158.1 ...
show more2026-08-31T12:44:39.215396-04:00 site sshd-session[160198]: Invalid user 208.68.39 from 81.213.158.164 port 43962
2026-08-31T15:08:38.510842-04:00 site sshd-session[160604]: Invalid user ledger from 81.213.158.164 port 36598
2026-08-31T17:34:28.625815-04:00 site sshd-session[161111]: Invalid user 208.68.39 from 81.213.158.164 port 57389
...
show less
2026-08-31T15:14:43.549449+00:00 sgp01 sshd[1329172]: Invalid user 157.245.51 from 81.213.158.164 po ...
show more2026-08-31T15:14:43.549449+00:00 sgp01 sshd[1329172]: Invalid user 157.245.51 from 81.213.158.164 port 45409
2026-08-31T16:47:14.779046+00:00 sgp01 sshd[1333279]: Invalid user 159.89.208 from 81.213.158.164 port 49968
2026-08-31T17:37:34.880907+00:00 sgp01 sshd[1334995]: Invalid user ledger from 81.213.158.164 port 37996
2026-08-31T19:11:16.079831+00:00 sgp01 sshd[1338786]: Invalid user ledger from 81.213.158.164 port 42601
2026-08-31T20:02:33.796467+00:00 sgp01 sshd[1340835]: Invalid user 157.245.51 from 81.213.158.164 port 58805
...
show less
Brute-Force
SSH
Anonymous
2026-08-31T13:07:05.446603+00:00 mail sshd[923106]: Invalid user op from 81.213.158.164 port 48593
2 ...
show more2026-08-31T13:07:05.446603+00:00 mail sshd[923106]: Invalid user op from 81.213.158.164 port 48593
2026-08-31T15:29:35.950857+00:00 mail sshd[924056]: Invalid user 167.71.51 from 81.213.158.164 port 41179
2026-08-31T17:52:38.058016+00:00 mail sshd[924967]: Invalid user ledger from 81.213.158.164 port 33756
...
show less
2026-08-31T12:40:12.054618 telos sshd[3844028]: Invalid user op from 81.213.158.164 port 54971
2026- ...
show more2026-08-31T12:40:12.054618 telos sshd[3844028]: Invalid user op from 81.213.158.164 port 54971
2026-08-31T15:02:36.067294 telos sshd[3845382]: Invalid user 161.35.191 from 81.213.158.164 port 47585
2026-08-31T17:25:30.282712 telos sshd[3846437]: Invalid user ledger from 81.213.158.164 port 40139
show less
Automated sensor: 27 SSH brute-force attempts over the last 24h (latest 2026-08-31T11:22Z). Username ...
show moreAutomated sensor: 27 SSH brute-force attempts over the last 24h (latest 2026-08-31T11:22Z). Usernames tried: 161.35.112, root, node, ripple.
show less
Brute-Force
SSH
Showing 1 to
15
of 28 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩