This IP address has been reported a total of
199
times from
145 distinct
sources.
134.122.72.52 was first reported on
, and the most recent report was
.
Old Reports:
The most recent abuse report for this IP address is from
. It is possible that this IP is no longer involved in abusive activities.
Honeypot hit: HTTP/1.1 request on 8081
GET /
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:142.0) ...
show moreHoneypot hit: HTTP/1.1 request on 8081
GET /
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate; 8081 [2] TCP
show less
Blocked by UFW (TCP on 10000)
Source port: 61012
TTL: 236
Packet length: 44
TOS: 0x08
This report ( ...
show moreBlocked by UFW (TCP on 10000)
Source port: 61012
TTL: 236
Packet length: 44
TOS: 0x08
This report (for 134.122.72.52) was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
2025-12-05T03:40:47.857288+02:00 ns1 postfix/submission/smtpd[3574302]: improper command pipelining ...
show more2025-12-05T03:40:47.857288+02:00 ns1 postfix/submission/smtpd[3574302]: improper command pipelining after CONNECT from unknown[134.122.72.52]: \026\003\003\001\247\001\000\001\243\003\003\335g\264wM\221\321\244l\353o\360\306\301R\3618iz?\215\330\262\252\355\363\220I\3147>` \272\v\324\362q\322\034\037\251\262\223P\034\214\301\036"\220\344q\016\bT\376\260\202N\275a\337\3663\000\212\000\026\0003\000g\300\236\300\242\000\236\0009\000k\300\237\300\243\000\237
2025-12-05T03:40:47.965006+02:00 ns1 postfix/submission/smtpd[3574302]: improper command pipelining after CONNECT from unknown[134.122.72.52]: \026\003\003\001\247\001\000\001\243\003\003\366\262[m\253=\357\272$]\266\342!PS\006\b\213\331\b\027\233\230\360\252\023\273\203\022\347\033\t \243K\216\306<\375\347l?K\223"\207\337\370\032\313\022\327B\221\261\320\0042\261\030\361a@j\240\000\212\000\005\000\004\000\a\000\300\000\204\000\272\000A\000\235\300\241\300\235\000=
...
show less
2025-12-04T23:20:47.486686+00:00 nl postfix/smtpd[19786]: improper command pipelining after CONNECT ...
show more2025-12-04T23:20:47.486686+00:00 nl postfix/smtpd[19786]: improper command pipelining after CONNECT from unknown[134.122.72.52]: \026\003\003\001\244\001\000\001\240\003\003\036\215\273\263\255\252\373\321\210\n\330\366\365"\310\r\t\322h\3264\307\2706\232\230\216M{\220z\313 ^\266,\321\363\321u\236\263\000\000\251m\236\367\002\231w\231c\227?\351\307[QN*\357v\373\247\000\212\000\026\0003\000g\300\236\300\242\000\236\0009\000k\300\237\300\243\000\237
2025-12-04T23:20:47.512800+00:00 nl postfix/smtpd[19786]: improper command pipelining after CONNECT from unknown[134.122.72.52]: \026\003\003\001\244\001\000\001\240\003\003\372MMX^E\376Sp\261\306i3\177\003=\364\332=\304\231\340\303\363.H \334>\031\323\023 \207\027c\224{\257%\336\316\b\374G\352\300$\277\344\242\214\361s\256Q\325Y\367\ah<\267\370\371\000\212\000\005\000\004\000\a\000\300\000\204\000\272\000A\000\235\300\241\300\235\000=
2025-12-04T23:20:47.556562+00:00 nl postfix/smtpd[19786]: improper command pipelining after CONNECT from unk
...
show less
Dec 4 23:58:11 www postfix/smtpd\[6430\]: lost connection after CONNECT from unknown\[134.122.72.52 ...
show moreDec 4 23:58:11 www postfix/smtpd\[6430\]: lost connection after CONNECT from unknown\[134.122.72.52\]
show less
2025-12-04T23:53:27.530040+01:00 immelmann sshd[2916038]: Connection closed by 134.122.72.52 port 48 ...
show more2025-12-04T23:53:27.530040+01:00 immelmann sshd[2916038]: Connection closed by 134.122.72.52 port 48578 [preauth]
...
show less
Brute-Force
SSH
Showing 1 to
15
of 199 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩