City: unknown
Region: unknown
Country: India
Internet Service Provider: Tata Teleservices Ltd
Hostname: unknown
Organization: unknown
Usage Type: unknown
| Type | Details | Datetime |
|---|---|---|
| attack | Unauthorized connection attempt from IP address 14.99.81.14 on Port 445(SMB) |
2020-04-01 01:34:32 |
| IP | Type | Details | Datetime |
|---|---|---|---|
| 14.99.81.218 | attackspam | 2020-10-12T10:13:50.935002yoshi.linuxbox.ninja sshd[3154240]: Failed password for invalid user appltest from 14.99.81.218 port 26201 ssh2 2020-10-12T10:17:11.783447yoshi.linuxbox.ninja sshd[3156592]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.99.81.218 user=root 2020-10-12T10:17:13.888599yoshi.linuxbox.ninja sshd[3156592]: Failed password for root from 14.99.81.218 port 29472 ssh2 ... |
2020-10-13 00:03:43 |
| 14.99.81.218 | attackbotsspam | Oct 12 03:43:48 firewall sshd[7090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.99.81.218 Oct 12 03:43:48 firewall sshd[7090]: Invalid user admin from 14.99.81.218 Oct 12 03:43:49 firewall sshd[7090]: Failed password for invalid user admin from 14.99.81.218 port 10893 ssh2 ... |
2020-10-12 15:26:47 |
| 14.99.81.218 | attackbots | 2020-09-18T02:44:04+0200 Failed SSH Authentication/Brute Force Attack. (Server 5) |
2020-09-18 22:57:39 |
| 14.99.81.218 | attack | 2020-09-18T02:44:04+0200 Failed SSH Authentication/Brute Force Attack. (Server 5) |
2020-09-18 15:10:03 |
| 14.99.81.218 | attack | Sep 8 20:23:56 plg sshd[23563]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.99.81.218 Sep 8 20:23:59 plg sshd[23563]: Failed password for invalid user ubnt from 14.99.81.218 port 15543 ssh2 Sep 8 20:27:14 plg sshd[23584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.99.81.218 Sep 8 20:27:16 plg sshd[23584]: Failed password for invalid user jboss from 14.99.81.218 port 22493 ssh2 Sep 8 20:30:25 plg sshd[23602]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.99.81.218 user=root Sep 8 20:30:27 plg sshd[23602]: Failed password for invalid user root from 14.99.81.218 port 12581 ssh2 ... |
2020-09-09 02:49:27 |
| 14.99.81.218 | attackspambots | sshd: Failed password for .... from 14.99.81.218 port 16165 ssh2 (10 attempts) |
2020-09-08 18:20:53 |
| 14.99.81.218 | attackbots | Aug 29 23:36:04 pkdns2 sshd\[56216\]: Address 14.99.81.218 maps to static-218.81.99.14-tataidc.co.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Aug 29 23:36:04 pkdns2 sshd\[56216\]: Invalid user down from 14.99.81.218Aug 29 23:36:05 pkdns2 sshd\[56216\]: Failed password for invalid user down from 14.99.81.218 port 10176 ssh2Aug 29 23:39:17 pkdns2 sshd\[56350\]: Address 14.99.81.218 maps to static-218.81.99.14-tataidc.co.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Aug 29 23:39:17 pkdns2 sshd\[56350\]: Invalid user henk from 14.99.81.218Aug 29 23:39:19 pkdns2 sshd\[56350\]: Failed password for invalid user henk from 14.99.81.218 port 1969 ssh2 ... |
2020-08-30 08:40:44 |
| 14.99.81.218 | attack | Aug 29 22:19:14 pkdns2 sshd\[52736\]: Address 14.99.81.218 maps to static-218.81.99.14-tataidc.co.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Aug 29 22:19:14 pkdns2 sshd\[52736\]: Invalid user tomcat from 14.99.81.218Aug 29 22:19:15 pkdns2 sshd\[52736\]: Failed password for invalid user tomcat from 14.99.81.218 port 25881 ssh2Aug 29 22:22:35 pkdns2 sshd\[52875\]: Address 14.99.81.218 maps to static-218.81.99.14-tataidc.co.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Aug 29 22:22:35 pkdns2 sshd\[52875\]: Invalid user meteor from 14.99.81.218Aug 29 22:22:38 pkdns2 sshd\[52875\]: Failed password for invalid user meteor from 14.99.81.218 port 2013 ssh2 ... |
2020-08-30 03:25:17 |
| 14.99.81.218 | attackspam | $f2bV_matches |
2020-08-25 21:44:30 |
| 14.99.81.218 | attack | SSH Brute Force |
2020-08-25 14:45:17 |
| 14.99.81.218 | attack | Invalid user rancher from 14.99.81.218 port 12872 |
2020-08-25 00:44:35 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.99.81.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50843
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;14.99.81.14. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020033101 1800 900 604800 86400
;; Query time: 101 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 01 01:34:29 CST 2020
;; MSG SIZE rcvd: 11514.81.99.14.in-addr.arpa domain name pointer static-14.81.99.14-tataidc.co.in.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
14.81.99.14.in-addr.arpa name = static-14.81.99.14-tataidc.co.in.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 36.66.156.125 | attackspam | Invalid user zimbra from 36.66.156.125 port 60126 |
2019-10-11 22:40:35 |
| 43.242.125.185 | attackspambots | 2019-10-11T13:55:40.736801abusebot-5.cloudsearch.cf sshd\[11399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.242.125.185 user=root |
2019-10-11 22:19:48 |
| 81.22.45.116 | attackspam | 2019-10-11T16:12:29.030110+02:00 lumpi kernel: [625563.710217] 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.116 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=23519 PROTO=TCP SPT=49945 DPT=1518 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-10-11 22:15:39 |
| 202.159.42.42 | attackspambots | Invalid user admin from 202.159.42.42 port 34131 |
2019-10-11 22:22:38 |
| 189.214.96.5 | attackbots | Invalid user admin from 189.214.96.5 port 40857 |
2019-10-11 22:27:14 |
| 51.15.99.106 | attack | Oct 11 15:54:43 microserver sshd[27830]: Invalid user P@$$wort@2016 from 51.15.99.106 port 56382 Oct 11 15:54:43 microserver sshd[27830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.99.106 Oct 11 15:54:44 microserver sshd[27830]: Failed password for invalid user P@$$wort@2016 from 51.15.99.106 port 56382 ssh2 Oct 11 15:58:42 microserver sshd[28467]: Invalid user P@$$w0rt!qaz from 51.15.99.106 port 40232 Oct 11 15:58:42 microserver sshd[28467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.99.106 Oct 11 16:10:25 microserver sshd[30326]: Invalid user Tour@2017 from 51.15.99.106 port 48236 Oct 11 16:10:25 microserver sshd[30326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.99.106 Oct 11 16:10:27 microserver sshd[30326]: Failed password for invalid user Tour@2017 from 51.15.99.106 port 48236 ssh2 Oct 11 16:14:31 microserver sshd[30596]: Invalid user 123Junior from 51. |
2019-10-11 22:46:59 |
| 76.27.163.60 | attackspam | 2019-10-11T15:18:02.4159221240 sshd\[31020\]: Invalid user usuario from 76.27.163.60 port 35762 2019-10-11T15:18:02.4185831240 sshd\[31020\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=76.27.163.60 2019-10-11T15:18:04.4461601240 sshd\[31020\]: Failed password for invalid user usuario from 76.27.163.60 port 35762 ssh2 ... |
2019-10-11 22:33:34 |
| 43.252.36.98 | attackbots | Invalid user test from 43.252.36.98 port 47948 |
2019-10-11 22:19:16 |
| 51.254.205.6 | attackbots | Invalid user abhishek from 51.254.205.6 port 54262 |
2019-10-11 22:35:17 |
| 211.159.152.252 | attackspam | frenzy |
2019-10-11 22:21:32 |
| 78.15.98.110 | attack | Invalid user pi from 78.15.98.110 port 52746 |
2019-10-11 22:33:09 |
| 197.251.179.132 | attack | Invalid user admin from 197.251.179.132 port 49594 |
2019-10-11 22:24:04 |
| 197.56.223.97 | attackbots | Invalid user admin from 197.56.223.97 port 60875 |
2019-10-11 22:24:31 |
| 82.149.162.78 | attackbotsspam | Invalid user anne from 82.149.162.78 port 33524 |
2019-10-11 22:51:46 |
| 45.55.12.248 | attack | 10/11/2019-08:49:52.396804 45.55.12.248 Protocol: 6 ET COMPROMISED Known Compromised or Hostile Host Traffic group 29 |
2019-10-11 22:38:04 |