City: unknown
Region: unknown
Country: United States
Internet Service Provider: Amazon Technologies Inc.
Hostname: unknown
Organization: unknown
Usage Type: Data Center/Web Hosting/Transit
| Type | Details | Datetime |
|---|---|---|
| attackspambots | Sending out Netflix spam from IP 54.240.14.174 (amazon.com / amazonaws.com) I have NEVER been a Netflix customer and never asked for this junk. The website spammed out is https://www.netflix.com/signup/creditoption?nftoken=BQAbAAEBEA77T6CHfer3tv8qolkSAduAkLFC%2FFYUyiUS4Sdi62TDOAptLP7WiMxUQK74rIuN%2BRXrWDnwU8vxCNSC2khWG0ZmflN2tsqMsqNHMDWRdKmlf6XFVqwlgd%2BFLY2Nz88IH4y3pcuOeFYD5X9L4G9ZZfbRHvrmZF%2FjsAyUI1f5mpTFg3eEFWfNQayYDiVrbb%2FU65EF%2B0XXrVI0T4jKa2zmCB8w5g%3D%3D&lnktrk=EMP&g=AEF2F71097E503EBEB44921E2720235C64526E40&lkid=URL_SIGNUP_CREDIT IPs: 54.69.16.110, 54.70.73.70, 54.149.101.155, 54.201.91.38, 54.213.182.74, 52.37.77.112, 52.41.20.47, 52.41.193.16 (amazon.com / amazonaws.com) amazon are pure scumbags who allow their customers to send out spam and do nothing about it! Report via email and website at https://support.aws.amazon.com/#/contacts/report-abuse |
2019-09-26 17:32:18 |
| IP | Type | Details | Datetime |
|---|---|---|---|
| 52.37.77.98 | attack | 10/23/2019-07:08:19.685071 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-23 17:21:46 |
| 52.37.77.98 | attackbots | 10/20/2019-06:59:07.265649 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-20 19:16:18 |
| 52.37.77.98 | attackspambots | 10/17/2019-18:44:02.135696 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-18 00:44:57 |
| 52.37.77.98 | attackbotsspam | 10/16/2019-05:24:02.019609 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-16 17:03:14 |
| 52.37.77.98 | attack | 10/15/2019-21:59:07.653389 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-16 04:47:57 |
| 52.37.77.98 | attack | 10/15/2019-08:56:13.262699 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-15 15:08:00 |
| 52.37.77.98 | attackbots | 10/12/2019-22:57:10.943099 52.37.77.98 Protocol: 6 SURICATA TLS invalid record/traffic |
2019-10-13 05:12:12 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.37.77.112
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25128
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;52.37.77.112. IN A
;; AUTHORITY SECTION:
. 424 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019092600 1800 900 604800 86400
;; Query time: 116 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 26 17:32:12 CST 2019
;; MSG SIZE rcvd: 116112.77.37.52.in-addr.arpa domain name pointer ec2-52-37-77-112.us-west-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
112.77.37.52.in-addr.arpa name = ec2-52-37-77-112.us-west-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 104.236.214.8 | attack | $f2bV_matches |
2019-12-13 23:27:01 |
| 201.215.176.8 | attackspambots | Invalid user yoyo from 201.215.176.8 port 52568 |
2019-12-13 23:34:11 |
| 92.118.38.55 | attackbots | 2019-12-13T14:54:14.539396beta postfix/smtpd[7947]: warning: unknown[92.118.38.55]: SASL LOGIN authentication failed: authentication failure 2019-12-13T14:54:37.105293beta postfix/smtpd[7947]: warning: unknown[92.118.38.55]: SASL LOGIN authentication failed: authentication failure 2019-12-13T14:55:05.188430beta postfix/smtpd[7947]: warning: unknown[92.118.38.55]: SASL LOGIN authentication failed: authentication failure ... |
2019-12-13 23:27:57 |
| 62.210.206.48 | attackspambots | 62.210.206.48 was recorded 13 times by 7 hosts attempting to connect to the following ports: 25141,45154. Incident counter (4h, 24h, all-time): 13, 13, 53 |
2019-12-13 23:51:58 |
| 157.245.76.36 | attack | Automatic report - Port Scan |
2019-12-13 23:26:09 |
| 152.136.122.130 | attack | SSH bruteforce |
2019-12-13 23:55:31 |
| 180.241.41.237 | attack | 1576222902 - 12/13/2019 08:41:42 Host: 180.241.41.237/180.241.41.237 Port: 445 TCP Blocked |
2019-12-13 23:18:44 |
| 106.13.56.72 | attack | Dec 13 16:37:22 [host] sshd[6360]: Invalid user fernie from 106.13.56.72 Dec 13 16:37:22 [host] sshd[6360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.56.72 Dec 13 16:37:24 [host] sshd[6360]: Failed password for invalid user fernie from 106.13.56.72 port 50728 ssh2 |
2019-12-13 23:51:15 |
| 85.175.100.1 | attackspam | $f2bV_matches |
2019-12-13 23:56:11 |
| 170.239.101.4 | attackspam | Dec 13 13:59:51 MK-Soft-Root1 sshd[32676]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.101.4 Dec 13 13:59:52 MK-Soft-Root1 sshd[32676]: Failed password for invalid user webmaster from 170.239.101.4 port 41070 ssh2 ... |
2019-12-13 23:36:18 |
| 42.118.254.166 | attack | Scanning |
2019-12-13 23:33:52 |
| 187.72.118.191 | attackbots | 2019-12-13T14:55:24.060136shield sshd\[28780\]: Invalid user schaer from 187.72.118.191 port 35954 2019-12-13T14:55:24.065762shield sshd\[28780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.72.118.191 2019-12-13T14:55:26.323547shield sshd\[28780\]: Failed password for invalid user schaer from 187.72.118.191 port 35954 ssh2 2019-12-13T15:04:33.963576shield sshd\[29678\]: Invalid user 123456 from 187.72.118.191 port 33228 2019-12-13T15:04:33.969427shield sshd\[29678\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.72.118.191 |
2019-12-13 23:15:08 |
| 106.13.117.17 | attackbotsspam | $f2bV_matches |
2019-12-13 23:37:49 |
| 202.175.46.170 | attackspambots | $f2bV_matches |
2019-12-13 23:21:58 |
| 164.52.12.210 | attackspam | Dec 13 12:51:53 vpn01 sshd[20898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.52.12.210 Dec 13 12:51:55 vpn01 sshd[20898]: Failed password for invalid user aabb654 from 164.52.12.210 port 52605 ssh2 ... |
2019-12-13 23:41:38 |