City: unknown
Region: unknown
Country: Japan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 150.74.0.40
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39641
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;150.74.0.40. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012700 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 19:22:34 CST 2025
;; MSG SIZE rcvd: 104
Host 40.0.74.150.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 40.0.74.150.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 60.255.230.202 | attackbots | (sshd) Failed SSH login from 60.255.230.202 (CN/China/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Oct 30 02:34:38 host sshd[94180]: Invalid user kb from 60.255.230.202 port 38038 |
2019-10-30 18:37:51 |
| 49.234.67.23 | attack | Oct 30 10:05:42 localhost sshd\[32099\]: Invalid user nagios from 49.234.67.23 port 37960 Oct 30 10:05:42 localhost sshd\[32099\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.67.23 Oct 30 10:05:45 localhost sshd\[32099\]: Failed password for invalid user nagios from 49.234.67.23 port 37960 ssh2 ... |
2019-10-30 18:51:28 |
| 45.70.0.158 | attack | Automatic report - Port Scan Attack |
2019-10-30 19:04:33 |
| 122.51.107.182 | attack | Oct 30 05:19:06 localhost sshd\[19604\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.107.182 user=root Oct 30 05:19:09 localhost sshd\[19604\]: Failed password for root from 122.51.107.182 port 48786 ssh2 Oct 30 05:23:12 localhost sshd\[19854\]: Invalid user pentarun from 122.51.107.182 Oct 30 05:23:12 localhost sshd\[19854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.107.182 Oct 30 05:23:14 localhost sshd\[19854\]: Failed password for invalid user pentarun from 122.51.107.182 port 58396 ssh2 ... |
2019-10-30 18:30:13 |
| 89.231.29.232 | attackbotsspam | Oct 30 10:42:24 v22019058497090703 sshd[23092]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.231.29.232 Oct 30 10:42:26 v22019058497090703 sshd[23092]: Failed password for invalid user testuser from 89.231.29.232 port 5466 ssh2 Oct 30 10:46:02 v22019058497090703 sshd[23371]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.231.29.232 ... |
2019-10-30 18:26:51 |
| 148.70.81.36 | attack | Oct 30 07:28:34 firewall sshd[16694]: Failed password for invalid user modem from 148.70.81.36 port 56574 ssh2 Oct 30 07:33:26 firewall sshd[16762]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.81.36 user=root Oct 30 07:33:28 firewall sshd[16762]: Failed password for root from 148.70.81.36 port 39158 ssh2 ... |
2019-10-30 18:38:53 |
| 124.74.110.230 | attackbots | Unauthorized connection attempt from IP address 124.74.110.230 on Port 445(SMB) |
2019-10-30 18:39:39 |
| 61.19.247.121 | attackspam | $f2bV_matches |
2019-10-30 18:45:25 |
| 81.22.45.107 | attack | 2019-10-30T11:42:40.519187+01:00 lumpi kernel: [2254552.893428] INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.107 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=46561 PROTO=TCP SPT=46244 DPT=36734 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-10-30 18:50:05 |
| 117.85.49.46 | attack | Oct 29 23:47:57 esmtp postfix/smtpd[32220]: lost connection after AUTH from unknown[117.85.49.46] Oct 29 23:47:58 esmtp postfix/smtpd[32220]: lost connection after AUTH from unknown[117.85.49.46] Oct 29 23:48:00 esmtp postfix/smtpd[32220]: lost connection after AUTH from unknown[117.85.49.46] Oct 29 23:48:01 esmtp postfix/smtpd[32220]: lost connection after AUTH from unknown[117.85.49.46] Oct 29 23:48:03 esmtp postfix/smtpd[32220]: lost connection after AUTH from unknown[117.85.49.46] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=117.85.49.46 |
2019-10-30 18:41:14 |
| 80.82.77.139 | attack | ET CINS Active Threat Intelligence Poor Reputation IP group 72 - port: 9200 proto: TCP cat: Misc Attack |
2019-10-30 19:02:33 |
| 202.98.213.218 | attack | Invalid user planeacion from 202.98.213.218 port 23535 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.98.213.218 Failed password for invalid user planeacion from 202.98.213.218 port 23535 ssh2 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.98.213.218 user=root Failed password for root from 202.98.213.218 port 33000 ssh2 |
2019-10-30 18:51:41 |
| 83.7.17.140 | attack | SSH bruteforce (Triggered fail2ban) |
2019-10-30 18:31:09 |
| 159.65.62.216 | attackbots | Oct 30 04:47:40 cp sshd[2672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.62.216 |
2019-10-30 18:56:43 |
| 114.5.221.142 | attackbots | [Wed Oct 30 10:48:27.264476 2019] [:error] [pid 7559:tid 140145034290944] [client 114.5.221.142:6521] [client 114.5.221.142] 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: 503 found within RESPONSE_STATUS: 503"] [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 "karangploso.jatim.bmkg.go.id"] [uri "/index.php/profil/peta-instrumentasi"] [unique_id "XbkIC48ZrE8Gf@6lZT6dTQAAAAE"], referer: https://karangploso.jatim.bmkg.go.id/
... |
2019-10-30 18:28:28 |