This IP address has been reported a total of
35
times from
6 distinct
sources.
133.242.49.140 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.
Aug 22 13:05:27 [host] sshd[159183]: Failed password for [user] from 133.242.49.140 port 49832 ssh2
...
show moreAug 22 13:05:27 [host] sshd[159183]: Failed password for [user] from 133.242.49.140 port 49832 ssh2
Aug 22 13:05:55 [host] sshd[159198]: Failed password for [user] from 133.242.49.140 port 35874 ssh2
Aug 22 13:06:22 [host] sshd[159268]: Invalid user ghost from 133.242.49.140 port 59264
Aug 22 13:06:25 [host] sshd[159268]: Failed password for invalid user ghost from 133.242.49.140 port 59264 ssh2
Aug 22 13:06:52 [host] sshd[159284]: Invalid user student from 133.242.49.140 port 44960
Aug 22 13:02:14 [host] sshd[158718]: Connection closed by 133.242.49.140 port 49594
Aug 22 13:03:41 [host] sshd[158796]: Connection closed by 133.242.49.140 port 53298 [preauth]
Aug 22 13:05:25 [host] sshd[159183]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.49.140 user=[user]
Aug 22 13:05:28 [host] sshd[159183]: Connection closed by authenticating user root 133.242.49.140 port 49832 [preauth]
Aug 22 13:05:53 [host] sshd[159198]: pam_unix(sshd:auth): auth
show less
Aug 22 11:03:37 Ubuntu-2204-jammy-amd64-base sshd[1924475]: Connection closed by 133.242.49.140 port ...
show moreAug 22 11:03:37 Ubuntu-2204-jammy-amd64-base sshd[1924475]: Connection closed by 133.242.49.140 port 41856 [preauth]
...
show less
Active SSH brute-force detected. Logs: 2026-08-20T18:43:02.558364+00:00 Prism sshd[93280]: Failed pa ...
show moreActive SSH brute-force detected. Logs: 2026-08-20T18:43:02.558364+00:00 Prism sshd[93280]: Failed password for invalid user jira from 133.242.49.140 port 44862 ssh2 2026-08-20T18:43:24.663807+00:00 Prism sshd[93282]: pam_unix(sshd:auth): authentication...
show less
Active SSH brute-force detected. Logs: Aug 20 19:53:57 scars sshd[714949]: pam_unix(sshd:auth): auth ...
show moreActive SSH brute-force detected. Logs: Aug 20 19:53:57 scars sshd[714949]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.49.140 Aug 20 19:53:56 scars sshd[714949]: Invalid user deploy from 133.242.49.1...
show less
Active SSH brute-force detected. Logs: 2026-08-20T22:52:17.377815+05:30 Va1kVirginia sshd-session[21 ...
show moreActive SSH brute-force detected. Logs: 2026-08-20T22:52:17.377815+05:30 Va1kVirginia sshd-session[2169965]: Failed password for root from 133.242.49.140 port 59078 ssh2 2026-08-20T22:52:23.989237+05:30 Va1kVirginia sshd-session[2170098]: Invalid user c...
show less
Active SSH brute-force detected. Logs: 2026-08-20T16:33:07.203631+00:00 oregon-1.xera.ca sshd[552463 ...
show moreActive SSH brute-force detected. Logs: 2026-08-20T16:33:07.203631+00:00 oregon-1.xera.ca sshd[552463]: Failed password for invalid user gao from 133.242.49.140 port 55890 ssh2 2026-08-20T16:33:29.257461+00:00 oregon-1.xera.ca sshd[553905]: Invalid user...
show less
SSH
Brute-Force
Showing 1 to
15
of 35 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩