12 Jun
2016
12 Jun
'16
2:39 p.m.
Hello,
Since last months my JNOS MBOX is being attacked:
15:24:59 94.53.236.39:55248 - MBOX (supervisor) bad login
15:25:07 113.162.86.77:35247 - MBOX (support) bad login
15:25:09 190.140.17.22:53348 - MBOX (root) bad login
15:25:14 92.27.102.224:38887 - MBOX (support) bad login
15:25:14 114.109.125.48:42069 - MBOX (administrator) bad login
15:25:35 190.140.17.22:54146 - MBOX (root) bad login
15:25:50 92.27.102.224:40191 - MBOX (support) bad login
15:26:33 182.184.71.162:41259 - MBOX (root) bad login
15:26:49 182.184.71.162:41259 - MBOX (sh) bad login
15:26:50 89.22.213.165:33979 - MBOX (root) bad login
15:27:52 89.22.213.165:34979 - MBOX (root) bad login
None of the users tried have granted permit.
Installed fail2ban but not avail.
Attacking IPs change continuosly, routing to loopback no help
Due heavy load jnos eventually hangs.
Is it there any way/suggestion to stop this ?
Appreciate any help.
73, lu7abf, Pedro Converso
44.153.0.1 or conversoft.com.ar
pconver(a)gmail.com
12 Jun
12 Jun
3:01 p.m.
This is typical for hosts exposed to the general Internet; we
get hundreds of failed probing login attempts every day on our
systems at work. I don't know of any effective way to stop it
unless you restrict login ports to a small set of addresses by
firewalling or turn off logins entirely.
- Brian
On Sun, Jun 12, 2016 at 03:39:43PM -0300, Pedro Converso wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hello,
Since last months my JNOS MBOX is being attacked:
15:24:59 94.53.236.39:55248 - MBOX (supervisor) bad login
15:25:07 113.162.86.77:35247 - MBOX (support) bad login
15:25:09 190.140.17.22:53348 - MBOX (root) bad login
15:25:14 92.27.102.224:38887 - MBOX (support) bad login
15:25:14 114.109.125.48:42069 - MBOX (administrator) bad login
15:25:35 190.140.17.22:54146 - MBOX (root) bad login
15:25:50 92.27.102.224:40191 - MBOX (support) bad login
15:26:33 182.184.71.162:41259 - MBOX (root) bad login
15:26:49 182.184.71.162:41259 - MBOX (sh) bad login
15:26:50 89.22.213.165:33979 - MBOX (root) bad login
15:27:52 89.22.213.165:34979 - MBOX (root) bad login
None of the users tried have granted permit.
Installed fail2ban but not avail.
Attacking IPs change continuosly, routing to loopback no help
Due heavy load jnos eventually hangs.
Is it there any way/suggestion to stop this ?
Appreciate any help.
73, lu7abf, Pedro Converso
44.153.0.1 or conversoft.com.ar
pconver(a)gmail.com
7:02 p.m.
You can do two types of blocks with fail2ban:
1) Attempts to login with supervisor, support, root, etc., as shown
below, can be blocked on the first try. I see two repeats of most of the
IPs in that short time window. So blocking after the first one should slow
down things by at least half.
2) Perhaps there are more repeats in the log outside of that short 3
minute window. If so, then 3 x "bad login" fails should slow things down
even more and catch any login names you didn't think of in the first list.
Once you start blocking enough of the IPs, you may break the botnet's
ability to continue.
Use NAT so that port 23 is not available outside your site network. That's
not a panacea since port scanners can eventually find a port ... if they
bother to look long enough and if you allow them to look long enough. But
most attackers go for the easy targets and folks who haven't even used NAT
are easy targets.
Use your firewall or IPtables and fail2ban to detect and block port
scanning.
As Brian suggested, restrict logins by pre-defined IP address range. Or, if
you firewall has the feature, use Geo-based IP blocking. Again, not
perfect. But a combination of traps will usually get the job done.
Michael
N6MEF
-----Original Message-----
From: 44Net [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On
Behalf Of Pedro Converso
Sent: Sunday, June 12, 2016 11:40 AM
To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
Subject: [44net] Help MBOX flood
(Please trim inclusions from previous messages)
_______________________________________________
Hello,
Since last months my JNOS MBOX is being attacked:
15:24:59 94.53.236.39:55248 - MBOX (supervisor) bad login
15:25:07 113.162.86.77:35247 - MBOX (support) bad login
15:25:09 190.140.17.22:53348 - MBOX (root) bad login
15:25:14 92.27.102.224:38887 - MBOX (support) bad login
15:25:14 114.109.125.48:42069 - MBOX (administrator) bad login
15:25:35 190.140.17.22:54146 - MBOX (root) bad login
15:25:50 92.27.102.224:40191 - MBOX (support) bad login
15:26:33 182.184.71.162:41259 - MBOX (root) bad login
15:26:49 182.184.71.162:41259 - MBOX (sh) bad login
15:26:50 89.22.213.165:33979 - MBOX (root) bad login
15:27:52 89.22.213.165:34979 - MBOX (root) bad login
None of the users tried have granted permit.
Installed fail2ban but not avail.
Attacking IPs change continuosly, routing to loopback no help
Due heavy load jnos eventually hangs.
Is it there any way/suggestion to stop this ?
Appreciate any help.
73, lu7abf, Pedro Converso
44.153.0.1 or conversoft.com.ar
pconver(a)gmail.com
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
7:14 p.m.
Yes.. the sad state of the Internet. In addition to tools like
fail2ban, you can consider another, more scalable approach using RBLs
(realtime blackhole lists) where known attack hosts are blocked:
https://www.google.com/search?q=rbl+to+block+ssh+connections
Most RBLs are used for email but there are many out there also for SSH
attacks which would be very applicable to your TELNET attacks. Using
RBLs through DNS is a lighter weight approach than creating iptables
rules that can become huge over time. The use of RBLs isn't perfect
either so you might choose to go with a blended approach. Good luck.
--David
KI6ZHD
3084
days inactive
3084
days old
3 comments
4 participants
participants (4)
-
Brian Kantor -
David Ranch -
Michael Fox - N6MEF -
Pedro Converso