City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.86.134.13
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17299
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.86.134.13. IN A
;; AUTHORITY SECTION:
. 266 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020702 1800 900 604800 86400
;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 07:26:49 CST 2022
;; MSG SIZE rcvd: 10513.134.86.54.in-addr.arpa domain name pointer ec2-54-86-134-13.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
13.134.86.54.in-addr.arpa name = ec2-54-86-134-13.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 170.81.145.243 | attack | Jan 13 21:11:50 pl3server sshd[8070]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.81.145.243 user=r.r Jan 13 21:11:52 pl3server sshd[8070]: Failed password for r.r from 170.81.145.243 port 51820 ssh2 Jan 13 21:11:52 pl3server sshd[8070]: Received disconnect from 170.81.145.243: 11: Bye Bye [preauth] Jan 13 22:05:20 pl3server sshd[19488]: Invalid user classic from 170.81.145.243 Jan 13 22:05:20 pl3server sshd[19488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.81.145.243 Jan 13 22:05:22 pl3server sshd[19488]: Failed password for invalid user classic from 170.81.145.243 port 50556 ssh2 Jan 13 22:05:22 pl3server sshd[19488]: Received disconnect from 170.81.145.243: 11: Bye Bye [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=170.81.145.243 |
2020-01-14 07:25:19 |
| 198.27.67.154 | attackbots | Jan 13 22:47:53 email sshd\[16595\]: Invalid user test from 198.27.67.154 Jan 13 22:47:53 email sshd\[16595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.27.67.154 Jan 13 22:47:55 email sshd\[16595\]: Failed password for invalid user test from 198.27.67.154 port 50113 ssh2 Jan 13 22:48:17 email sshd\[16687\]: Invalid user content from 198.27.67.154 Jan 13 22:48:17 email sshd\[16687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.27.67.154 ... |
2020-01-14 06:53:03 |
| 3.6.112.148 | attack | Unauthorized connection attempt detected from IP address 3.6.112.148 to port 2220 [J] |
2020-01-14 07:03:39 |
| 2001:470:dfa9:10ff:0:242:ac11:31 | attackbotsspam | Port scan |
2020-01-14 07:16:59 |
| 5.253.17.158 | attack | Jan 13 13:49:05 Tower sshd[11853]: refused connect from 177.200.34.103 (177.200.34.103) Jan 13 16:23:08 Tower sshd[11853]: Connection from 5.253.17.158 port 60572 on 192.168.10.220 port 22 rdomain "" Jan 13 16:23:09 Tower sshd[11853]: Invalid user deon from 5.253.17.158 port 60572 Jan 13 16:23:09 Tower sshd[11853]: error: Could not get shadow information for NOUSER Jan 13 16:23:09 Tower sshd[11853]: Failed password for invalid user deon from 5.253.17.158 port 60572 ssh2 Jan 13 16:23:09 Tower sshd[11853]: Received disconnect from 5.253.17.158 port 60572:11: Bye Bye [preauth] Jan 13 16:23:09 Tower sshd[11853]: Disconnected from invalid user deon 5.253.17.158 port 60572 [preauth] |
2020-01-14 06:51:53 |
| 123.21.28.234 | attackbotsspam | Brute force attempt |
2020-01-14 07:02:57 |
| 101.89.115.211 | attackbotsspam | 21 attempts against mh-ssh on cloud.magehost.pro |
2020-01-14 06:46:32 |
| 103.6.198.77 | attackspam | WordPress wp-login brute force :: 103.6.198.77 0.152 - [13/Jan/2020:23:04:35 0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1806 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1" |
2020-01-14 07:18:31 |
| 99.23.138.7 | attackspambots | Jan 13 20:18:08 localhost sshd\[12262\]: Invalid user ftp from 99.23.138.7 port 55574 Jan 13 20:18:08 localhost sshd\[12262\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=99.23.138.7 Jan 13 20:18:10 localhost sshd\[12262\]: Failed password for invalid user ftp from 99.23.138.7 port 55574 ssh2 Jan 13 21:23:43 localhost sshd\[12729\]: Invalid user prueba from 99.23.138.7 port 59292 |
2020-01-14 06:45:54 |
| 114.119.143.163 | attackspambots | [Tue Jan 14 04:23:42.638795 2020] [:error] [pid 12632:tid 139978369603328] [client 114.119.143.163:1114] [client 114.119.143.163] ModSecurity: Access denied with code 403 (phase 4). Pattern match "^5\\\\d{2}$" at RESPONSE_STATUS. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/RESPONSE-950-DATA-LEAKAGES.conf"] [line "118"] [id "950100"] [msg "The Application Returned a 500-Level Status Code"] [data "Matched Data: 500 found within RESPONSE_STATUS: 500"] [severity "ERROR"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-disclosure"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [tag "paranoia-level/2"] [hostname "staklim-malang.info"] [uri "/index.php/profil/meteorologi/list-all-categories/4010-klimatologi/analisis-klimatologi/monitoring-dan-prakiraan-curah-hujan-dasarian-di-provinsi-jawa-timur"] [unique_id "Xhzf17DHEoqzyfUy2HCoJwAAAA4"]
... |
2020-01-14 06:45:40 |
| 54.38.180.53 | attack | Jan 13 23:48:00 localhost sshd\[13704\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.180.53 user=root Jan 13 23:48:02 localhost sshd\[13704\]: Failed password for root from 54.38.180.53 port 48838 ssh2 Jan 13 23:51:22 localhost sshd\[13939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.180.53 user=root Jan 13 23:51:24 localhost sshd\[13939\]: Failed password for root from 54.38.180.53 port 47468 ssh2 Jan 13 23:54:34 localhost sshd\[13966\]: Invalid user ftpadmin from 54.38.180.53 Jan 13 23:54:34 localhost sshd\[13966\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.180.53 ... |
2020-01-14 07:16:03 |
| 78.128.113.173 | attackbotsspam | smtp auth brute force |
2020-01-14 07:15:48 |
| 92.222.204.120 | attackspam | 92.222.204.120 was recorded 13 times by 7 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 13, 27, 153 |
2020-01-14 07:22:11 |
| 222.186.30.187 | attack | Jan 14 00:39:14 server2 sshd\[16824\]: User root from 222.186.30.187 not allowed because not listed in AllowUsers Jan 14 00:39:14 server2 sshd\[16826\]: User root from 222.186.30.187 not allowed because not listed in AllowUsers Jan 14 00:39:15 server2 sshd\[16828\]: User root from 222.186.30.187 not allowed because not listed in AllowUsers Jan 14 00:39:15 server2 sshd\[16829\]: User root from 222.186.30.187 not allowed because not listed in AllowUsers Jan 14 00:48:41 server2 sshd\[17497\]: User root from 222.186.30.187 not allowed because not listed in AllowUsers Jan 14 00:48:41 server2 sshd\[17495\]: User root from 222.186.30.187 not allowed because not listed in AllowUsers |
2020-01-14 06:50:45 |
| 209.97.180.213 | attackbotsspam | Unauthorized connection attempt detected from IP address 209.97.180.213 to port 2220 [J] |
2020-01-14 07:11:04 |