| 34.120.202.146 |
attackbots |
RU spamvertising, health fraud - From: GlucaFIX
UBE 185.176.220.179 (EHLO gopxk.imkeeperr.com) 2 Cloud Ltd.
Spam link redfloppy.com = 185.246.116.174 Vpsville LLC – phishing redirect:
a) aptrk13.com = 35.204.93.160 Google
b) www.ep20trk.com = 34.120.202.146 Google
c) www.glucafix.us = 104.27.187.98, 104.27.186.98, 172.67.201.182 Cloudflare
d) glucafix.us = ditto
Images -
- http://redfloppy.com/web/imgs/mi1tb6fg.png = dailybetterhealth.com = 104.27.138.27, 104.27.139.27, 172.67.218.161 Cloudflare
- http://redfloppy.com/web/imgs/24sc48jt.png = unsub; no entity/address |
2020-10-03 12:06:19 |
| 189.154.176.137 |
attack |
Oct 3 00:41:28 ift sshd\[40748\]: Invalid user dr from 189.154.176.137Oct 3 00:41:30 ift sshd\[40748\]: Failed password for invalid user dr from 189.154.176.137 port 41832 ssh2Oct 3 00:45:24 ift sshd\[41531\]: Invalid user gaurav from 189.154.176.137Oct 3 00:45:27 ift sshd\[41531\]: Failed password for invalid user gaurav from 189.154.176.137 port 52752 ssh2Oct 3 00:49:25 ift sshd\[41718\]: Invalid user demon from 189.154.176.137
... |
2020-10-03 07:07:00 |
| 170.239.226.27 |
attack |
Oct 2 16:26:59 josie sshd[27931]: Did not receive identification string from 170.239.226.27
Oct 2 16:26:59 josie sshd[27930]: Did not receive identification string from 170.239.226.27
Oct 2 16:26:59 josie sshd[27932]: Did not receive identification string from 170.239.226.27
Oct 2 16:26:59 josie sshd[27933]: Did not receive identification string from 170.239.226.27
Oct 2 16:27:04 josie sshd[27961]: Invalid user admina from 170.239.226.27
Oct 2 16:27:04 josie sshd[27959]: Invalid user admina from 170.239.226.27
Oct 2 16:27:04 josie sshd[27956]: Invalid user admina from 170.239.226.27
Oct 2 16:27:04 josie sshd[27958]: Invalid user admina from 170.239.226.27
Oct 2 16:27:04 josie sshd[27961]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.226.27
Oct 2 16:27:04 josie sshd[27959]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.226.27
Oct 2 16:27:04 josie sshd[27956]:........
------------------------------- |
2020-10-03 06:56:44 |
| 52.191.166.171 |
attackbotsspam |
Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Invalid user ftpuser1 from 52.191.166.171
Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171
Oct 2 21:41:38 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Failed password for invalid user ftpuser1 from 52.191.166.171 port 36892 ssh2
Oct 2 22:41:04 Ubuntu-1404-trusty-64-minimal sshd\[619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171 user=git
Oct 2 22:41:06 Ubuntu-1404-trusty-64-minimal sshd\[619\]: Failed password for git from 52.191.166.171 port 60674 ssh2 |
2020-10-03 07:20:35 |
| 46.101.7.41 |
attackbots |
20 attempts against mh-ssh on air |
2020-10-03 07:19:11 |
| 183.166.170.133 |
attack |
Oct 2 22:30:45 srv01 postfix/smtpd\[1755\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 2 22:34:11 srv01 postfix/smtpd\[6490\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 2 22:37:37 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 2 22:41:03 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 2 22:41:14 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
... |
2020-10-03 07:11:24 |
| 1.255.48.197 |
attack |
(From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call.
$24.99/mo Flat Fee Credit Card Processing (Unlimited)
1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware?
New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019.
Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees.
2) You're legally able to demand this new option.
Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options?
We repre |
2020-10-03 06:58:51 |
| 92.50.249.166 |
attack |
Oct 3 00:30:07 meumeu sshd[1265891]: Invalid user gb from 92.50.249.166 port 34472
Oct 3 00:30:07 meumeu sshd[1265891]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.166
Oct 3 00:30:07 meumeu sshd[1265891]: Invalid user gb from 92.50.249.166 port 34472
Oct 3 00:30:10 meumeu sshd[1265891]: Failed password for invalid user gb from 92.50.249.166 port 34472 ssh2
Oct 3 00:31:43 meumeu sshd[1265949]: Invalid user tt from 92.50.249.166 port 34552
Oct 3 00:31:43 meumeu sshd[1265949]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.166
Oct 3 00:31:43 meumeu sshd[1265949]: Invalid user tt from 92.50.249.166 port 34552
Oct 3 00:31:45 meumeu sshd[1265949]: Failed password for invalid user tt from 92.50.249.166 port 34552 ssh2
Oct 3 00:33:20 meumeu sshd[1266035]: Invalid user testing from 92.50.249.166 port 34630
... |
2020-10-03 07:16:52 |
| 27.151.115.81 |
attackbots |
port scan and connect, tcp 1433 (ms-sql-s) |
2020-10-03 12:13:57 |
| 179.197.71.132 |
attack |
1601671289 - 10/02/2020 22:41:29 Host: 179.197.71.132/179.197.71.132 Port: 445 TCP Blocked |
2020-10-03 07:02:00 |
| 41.207.7.240 |
attackspambots |
Lines containing failures of 41.207.7.240
Oct 2 22:24:45 new sshd[31337]: Did not receive identification string from 41.207.7.240 port 57604
Oct 2 22:24:45 new sshd[31338]: Did not receive identification string from 41.207.7.240 port 57607
Oct 2 22:24:48 new sshd[31341]: Did not receive identification string from 41.207.7.240 port 57651
Oct 2 22:24:48 new sshd[31339]: Invalid user dircreate from 41.207.7.240 port 57884
Oct 2 22:24:48 new sshd[31339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.7.240
Oct 2 22:24:50 new sshd[31339]: Failed password for invalid user dircreate from 41.207.7.240 port 57884 ssh2
Oct 2 22:24:50 new sshd[31343]: Invalid user dircreate from 41.207.7.240 port 57893
Oct 2 22:24:50 new sshd[31343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.7.240
Oct 2 22:24:50 new sshd[31339]: Connection closed by invalid user dircreate 41.207.7.240 port ........
------------------------------ |
2020-10-03 12:07:22 |
| 61.133.232.253 |
attack |
2020-10-03T05:25:55.716294vps773228.ovh.net sshd[1872]: Invalid user teste from 61.133.232.253 port 9428
2020-10-03T05:25:55.729431vps773228.ovh.net sshd[1872]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.253
2020-10-03T05:25:55.716294vps773228.ovh.net sshd[1872]: Invalid user teste from 61.133.232.253 port 9428
2020-10-03T05:25:57.226373vps773228.ovh.net sshd[1872]: Failed password for invalid user teste from 61.133.232.253 port 9428 ssh2
2020-10-03T05:34:12.163060vps773228.ovh.net sshd[1912]: Invalid user michael from 61.133.232.253 port 39112
... |
2020-10-03 12:13:07 |
| 14.200.208.244 |
attackbots |
SSH Invalid Login |
2020-10-03 07:10:31 |
| 188.131.131.59 |
attackspambots |
SSH bruteforce |
2020-10-03 12:08:40 |
| 200.140.234.142 |
attackbotsspam |
SSH Honeypot -> SSH Bruteforce / Login |
2020-10-03 07:20:11 |