This IP address has been reported a total of
44
times from
23 distinct
sources.
202.158.42.134 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-02T15:53:29.604747 telos sshd[3896150]: Invalid user blockchain from 202.158.42.134 port 509 ...
show more2026-09-02T15:53:29.604747 telos sshd[3896150]: Invalid user blockchain from 202.158.42.134 port 50940
2026-09-02T16:27:32.065864 telos sshd[3898068]: Invalid user doc from 202.158.42.134 port 43268
2026-09-02T20:57:56.229172 telos sshd[3911387]: Invalid user culture from 202.158.42.134 port 55192
show less
Brute-Force
SSH
Anonymous
2026-09-02T14:03:48.446206 VOSTOK sshd[15605]: pam_unix(sshd:auth): authentication failure; logname= ...
show more2026-09-02T14:03:48.446206 VOSTOK sshd[15605]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
2026-09-02T14:03:50.524158 VOSTOK sshd[15605]: Failed password for invalid user conference from 202.158.42.134 port 40970 ssh2
2026-09-02T14:27:30.390919 VOSTOK sshd[26050]: Invalid user bernard from 202.158.42.134 port 54888
2026-09-02T14:27:30.616280 VOSTOK sshd[26050]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
2026-09-02T14:27:32.243776 VOSTOK sshd[26050]: Failed password for invalid user bernard from 202.158.42.134 port 54888 ssh2
...
show less
Detected by SiberKapan threat intelligence platform (siberkapan.org). Attack types: fail2ban_ban. So ...
show moreDetected by SiberKapan threat intelligence platform (siberkapan.org). Attack types: fail2ban_ban. Sources: fail2ban. First seen: 2026-09-01. Risk score: 60/100.
show less
2026-09-02T10:57:05.269890-04:00 site sshd-session[189142]: User root from 202.158.42.134 not allowe ...
show more2026-09-02T10:57:05.269890-04:00 site sshd-session[189142]: User root from 202.158.42.134 not allowed because not listed in AllowUsers
2026-09-02T12:21:41.509756-04:00 site sshd-session[192438]: Invalid user crypto from 202.158.42.134 port 43940
2026-09-02T12:38:09.998782-04:00 site sshd-session[193149]: Invalid user doc from 202.158.42.134 port 54780
...
show less
2026-09-02T14:39:31.512984+00:00 sgp01 sshd[1470744]: Invalid user solana from 202.158.42.134 port 4 ...
show more2026-09-02T14:39:31.512984+00:00 sgp01 sshd[1470744]: Invalid user solana from 202.158.42.134 port 48346
2026-09-02T15:36:34.270804+00:00 sgp01 sshd[1475152]: Invalid user cloud from 202.158.42.134 port 33906
2026-09-02T15:44:40.816506+00:00 sgp01 sshd[1475818]: Invalid user blockchain from 202.158.42.134 port 57790
2026-09-02T15:54:04.666076+00:00 sgp01 sshd[1476546]: Invalid user blockchain from 202.158.42.134 port 60212
2026-09-02T16:34:05.261733+00:00 sgp01 sshd[1479784]: Invalid user crypto from 202.158.42.134 port 54428
...
show less
Successful SSH login observed on Cowrie honeypot. Targeted username: solana. Observed at: 2026-09-02 ...
show moreSuccessful SSH login observed on Cowrie honeypot. Targeted username: solana. Observed at: 2026-09-02T14:47:31.431035Z. Session: a97aa4b529b0.
show less
Brute-Force
SSH
Anonymous
2026-09-02T13:55:46.188030 ARES sshd[5670]: Invalid user crypto from 202.158.42.134 port 57448
2026- ...
show more2026-09-02T13:55:46.188030 ARES sshd[5670]: Invalid user crypto from 202.158.42.134 port 57448
2026-09-02T13:55:46.444918 ARES sshd[5670]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
2026-09-02T13:55:48.485562 ARES sshd[5670]: Failed password for invalid user crypto from 202.158.42.134 port 57448 ssh2
...
show less
Automated sensor: 51 SSH brute-force attempts over the last 24h (latest 2026-09-02T13:08Z). Username ...
show moreAutomated sensor: 51 SSH brute-force attempts over the last 24h (latest 2026-09-02T13:08Z). Usernames tried: booker, cleveland, cloudflare, cloudfront.
show less
[Auto ban] Fail2Ban jail sshd on host: 3 failures in 2h. Excerpt: 2026-09-02T09:11:51.450831+00:00 U ...
show more[Auto ban] Fail2Ban jail sshd on host: 3 failures in 2h. Excerpt: 2026-09-02T09:11:51.450831+00:00 Ubuntu-Toronto1 sshd[2018449]: Invalid user cleveland from 202.158.42.134 port 60910
2026-09-02T09:43:39.132727+00:00 Ubuntu-Toronto1 sshd[2034675]: Invalid user vincenzo from 202.158.42.134 port 48268
2026-09-02T11:13:19.383392+00:00 Ubuntu-Toronto1 sshd[2077265]: Invalid user panel from 202.158.42.134 port 54702
show less
2026-09-02T10:05:21.724896+00:00 ssh sshd[195393]: Failed password for invalid user shayne from 202. ...
show more2026-09-02T10:05:21.724896+00:00 ssh sshd[195393]: Failed password for invalid user shayne from 202.158.42.134 port 58808 ssh2
2026-09-02T10:14:02.375247+00:00 ssh sshd[198771]: Invalid user vincenzo from 202.158.42.134 port 47604
2026-09-02T10:14:02.615342+00:00 ssh sshd[198771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
2026-09-02T10:14:04.582283+00:00 ssh sshd[198771]: Failed password for invalid user vincenzo from 202.158.42.134 port 47604 ssh2
...
show less
Sep 2 10:09:10 nervous-edison8 sshd[382738]: pam_unix(sshd:auth): authentication failure; logname= ...
show moreSep 2 10:09:10 nervous-edison8 sshd[382738]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
Sep 2 10:09:12 nervous-edison8 sshd[382738]: Failed password for invalid user cleveland from 202.158.42.134 port 44902 ssh2
Sep 2 10:32:31 nervous-edison8 sshd[385294]: Invalid user salvatore from 202.158.42.134 port 37834
Sep 2 10:32:31 nervous-edison8 sshd[385294]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
Sep 2 10:32:33 nervous-edison8 sshd[385294]: Failed password for invalid user salvatore from 202.158.42.134 port 37834 ssh2
...
show less
Brute-Force
SSH
Anonymous
Sep 2 04:22:56 wp sshd[531977]: Invalid user salvatore from 202.158.42.134 port 57962
Sep 2 04:22: ...
show moreSep 2 04:22:56 wp sshd[531977]: Invalid user salvatore from 202.158.42.134 port 57962
Sep 2 04:22:58 wp sshd[531977]: Failed password for invalid user salvatore from 202.158.42.134 port 57962 ssh2
Sep 2 04:24:28 wp sshd[532306]: Invalid user cleveland from 202.158.42.134 port 43874
...
show less
2026-09-02T08:17:09.719421shield sshd\[3118\]: Invalid user cleveland from 202.158.42.134 port 50548 ...
show more2026-09-02T08:17:09.719421shield sshd\[3118\]: Invalid user cleveland from 202.158.42.134 port 50548
2026-09-02T08:17:09.949133shield sshd\[3118\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
2026-09-02T08:17:11.484472shield sshd\[3118\]: Failed password for invalid user cleveland from 202.158.42.134 port 50548 ssh2
2026-09-02T08:24:43.486418shield sshd\[4847\]: Invalid user salvatore from 202.158.42.134 port 60938
2026-09-02T08:24:43.826574shield sshd\[4847\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.158.42.134
show less
Brute-Force
SSH
Showing 1 to
15
of 44 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩