This IP address has been reported a total of
174
times from
151 distinct
sources.
202.134.242.47 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 40
reports;
Germany
with 39
reports;
France
with 20
reports.
The most common categories in these recent reports were:
SSH
160
times;
Brute-Force
159
times;
Port Scan
8
times;
Hacking
6
times;
Web App Attack
3
times;
Other
4
times.
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-10-24T13:23:46.775134+02:00 perseus sshd-session[3772156]: Failed password for root from 202.13 ...
show more2026-10-24T13:23:46.775134+02:00 perseus sshd-session[3772156]: Failed password for root from 202.134.242.47 port 55484 ssh2
2026-10-24T13:25:38.648866+02:00 perseus sshd-session[3773760]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.134.242.47 user=root
2026-10-24T13:25:40.820608+02:00 perseus sshd-session[3773760]: Failed password for root from 202.134.242.47 port 49934 ssh2
show less
2026-10-24 14:05:27 Failed password for root from 202.134.242.47 port 46042 ssh2
2026-10-24 14:07:19 ...
show more2026-10-24 14:05:27 Failed password for root from 202.134.242.47 port 46042 ssh2
2026-10-24 14:07:19 rhost=202.134.242.47 user=root
show less
2026-10-24T04:15:19.020457-06:00 derpamp-oci sshd-session[134934]: Invalid user seekcy from 202.134. ...
show more2026-10-24T04:15:19.020457-06:00 derpamp-oci sshd-session[134934]: Invalid user seekcy from 202.134.242.47 port 44964
2026-10-24T04:24:00.616769-06:00 derpamp-oci sshd-session[135244]: Invalid user mini from 202.134.242.47 port 53400
2026-10-24T04:27:36.368950-06:00 derpamp-oci sshd-session[135292]: Invalid user fuho from 202.134.242.47 port 46064
...
show less
2026-10-24T12:14:05.518192+02:00 misaka-vm-s3n-2c4g-ber sshd-session[130022]: Invalid user seekcy fr ...
show more2026-10-24T12:14:05.518192+02:00 misaka-vm-s3n-2c4g-ber sshd-session[130022]: Invalid user seekcy from 202.134.242.47 port 36516
2026-10-24T12:23:48.807011+02:00 misaka-vm-s3n-2c4g-ber sshd-session[130095]: Invalid user mini from 202.134.242.47 port 58542
2026-10-24T12:27:25.067394+02:00 misaka-vm-s3n-2c4g-ber sshd-session[130125]: Invalid user fuho from 202.134.242.47 port 43610
...
show less
Oct 24 12:12:51 [host] sshd[2500]: Disconnected from invalid user seekcy 202.134.242.47 port 53314 [ ...
show moreOct 24 12:12:51 [host] sshd[2500]: Disconnected from invalid user seekcy 202.134.242.47 port 53314 [
Oct 24 12:23:38 [host] sshd[3303]: Invalid user mini from 202.134.242.47 port 45996
Oct 24 12:23:38 [host] sshd[3303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=
Oct 24 12:23:40 [host] sshd[3303]: Failed password for invalid user mini from 202.134.242.47 port 45
Oct 24 12:23:40 [host] sshd[3303]: Disconnected from invalid user mini 202.134.242.47 port 45996 [pr
show less
TSEC Honeypot Network report. Threat score: 86/100. Categories: Port Scan, Hacking, Brute-Force, Web ...
show moreTSEC Honeypot Network report. Threat score: 86/100. Categories: Port Scan, Hacking, Brute-Force, Web App Attack, SSH. Honeypot: beelzebub. Context: Attacker IP 202.134.242.47 observed using SSH client fingerprint 'Unknown SSH Client (f555226df196)' 3 times when connecting to a financial services sector honeypot between 2026-10-24 08:21 and 202....
show less
Disconnected from authenticating user root 202.134.242.47 port 46352 [preauth]
Disconnected from aut ...
show moreDisconnected from authenticating user root 202.134.242.47 port 46352 [preauth]
Disconnected from authenticating user root 202.134.242.47 port 47826 [preauth]
Disconnected from authenticating user root 202.134.242.47 port 50274 [preauth]
Disconnected from authenticating user root 202.134.242.47 port 41756 [preauth]
Disconnected from authenticating user root 202.134.242.47 port 48998 [preauth]
show less
