City: unknown
Region: unknown
Country: Thailand
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 119.42.122.239 | attack | srvr1: (mod_security) mod_security (id:942100) triggered by 119.42.122.239 (TH/-/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_MODSEC; Logs: 2020/08/21 12:03:52 [error] 482759#0: *840352 [client 119.42.122.239] ModSecurity: Access denied with code 406 (phase 2). [file "/etc/modsecurity.d/REQUEST-942-APPLICATION-ATTACK-SQLI.conf"] [line "45"] [id "942100"] [rev ""] [msg ""] [redacted] [severity "0"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-sqli"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/66"] [tag "PCI/6.5.2"] [redacted] [uri "/forum/viewthread.php"] [unique_id "159801143266.523321"] [ref ""], client: 119.42.122.239, [redacted] request: "GET /forum/viewthread.php?thread_id=1122%27+AND+++9747+%3D+0 HTTP/1.1" [redacted] |
2020-08-22 00:21:11 |
| 119.42.122.85 | attackspambots | Unauthorized IMAP connection attempt |
2020-06-10 19:09:26 |
| 119.42.122.151 | attack | Unauthorized connection attempt detected from IP address 119.42.122.151 to port 445 |
2019-12-23 15:08:49 |
| 119.42.122.196 | attackbots | 119.42.122.196 has been banned from MailServer for Abuse ... |
2019-10-12 20:16:45 |
| 119.42.122.244 | attackbots | 445/tcp [2019-06-27]1pkt |
2019-06-27 21:22:50 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.42.122.111
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50858
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;119.42.122.111. IN A
;; AUTHORITY SECTION:
. 256 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030800 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 18:38:55 CST 2022
;; MSG SIZE rcvd: 107Host 111.122.42.119.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 111.122.42.119.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 112.85.42.173 | attackbotsspam | Dec 10 23:54:36 linuxvps sshd\[7451\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.173 user=root Dec 10 23:54:38 linuxvps sshd\[7451\]: Failed password for root from 112.85.42.173 port 9064 ssh2 Dec 10 23:54:55 linuxvps sshd\[7624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.173 user=root Dec 10 23:54:56 linuxvps sshd\[7624\]: Failed password for root from 112.85.42.173 port 44672 ssh2 Dec 10 23:54:59 linuxvps sshd\[7624\]: Failed password for root from 112.85.42.173 port 44672 ssh2 |
2019-12-11 13:25:43 |
| 106.13.1.203 | attack | Triggered by Fail2Ban at Vostok web server |
2019-12-11 13:01:01 |
| 159.192.220.125 | attackbots | Attempt to attack host OS, exploiting network vulnerabilities, on 11-12-2019 04:55:09. |
2019-12-11 13:08:53 |
| 222.186.173.238 | attack | 2019-12-11T05:30:42.976664abusebot-6.cloudsearch.cf sshd\[29627\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238 user=root |
2019-12-11 13:36:34 |
| 150.223.1.86 | attack | Invalid user hartney from 150.223.1.86 port 48577 |
2019-12-11 09:26:54 |
| 162.247.72.199 | attack | Dec 11 04:55:07 thevastnessof sshd[1454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.72.199 ... |
2019-12-11 13:14:41 |
| 80.82.77.227 | attackbots | Fail2Ban Ban Triggered |
2019-12-11 13:30:31 |
| 61.148.16.162 | attackspambots | Dec 11 00:27:10 plusreed sshd[22615]: Invalid user sveinole from 61.148.16.162 ... |
2019-12-11 13:37:25 |
| 222.186.175.215 | attackbotsspam | $f2bV_matches |
2019-12-11 13:16:49 |
| 185.176.27.118 | attack | Dec 11 06:11:20 mc1 kernel: \[199918.942083\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.118 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=46101 PROTO=TCP SPT=55867 DPT=19232 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 11 06:12:00 mc1 kernel: \[199958.685109\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.118 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=3784 PROTO=TCP SPT=55867 DPT=25873 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 11 06:19:44 mc1 kernel: \[200423.327194\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.118 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=25536 PROTO=TCP SPT=55867 DPT=54213 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-12-11 13:20:34 |
| 193.31.24.113 | attack | 12/11/2019-06:10:02.647459 193.31.24.113 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-12-11 13:21:28 |
| 77.85.169.19 | attackbotsspam | Spam trapped |
2019-12-11 13:05:10 |
| 106.13.26.40 | attackbotsspam | Dec 11 06:12:00 meumeu sshd[14931]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.26.40 Dec 11 06:12:02 meumeu sshd[14931]: Failed password for invalid user yk from 106.13.26.40 port 47540 ssh2 Dec 11 06:20:13 meumeu sshd[15960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.26.40 ... |
2019-12-11 13:26:31 |
| 189.79.115.63 | attackspambots | Dec 10 18:47:49 php1 sshd\[8290\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.79.115.63 user=root Dec 10 18:47:50 php1 sshd\[8290\]: Failed password for root from 189.79.115.63 port 42152 ssh2 Dec 10 18:55:04 php1 sshd\[9320\]: Invalid user kehaulani from 189.79.115.63 Dec 10 18:55:04 php1 sshd\[9320\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.79.115.63 Dec 10 18:55:06 php1 sshd\[9320\]: Failed password for invalid user kehaulani from 189.79.115.63 port 50110 ssh2 |
2019-12-11 13:14:21 |
| 195.93.207.75 | attackbots | SSH authentication failure x 6 reported by Fail2Ban ... |
2019-12-11 13:33:39 |