System,error,critical login failure

RouterOS Beginner Basics
1

Hello,

I just started using mikrotik recently, when i login to my router, i keep getting this

"apr/18/2019 06:04:07 system,error,critical login failure for user applmgr from 192.169.217.183 via ssh
apr/18/2019 06:04:16 system,error,critical login failure for user support from 103.99.3.201 via ssh
apr/18/2019 06:04:18 system,error,critical login failure for user support from 103.99.3.201 via ssh
apr/18/2019 06:07:14 system,error,critical login failure for user openstack from 165.227.53.51 via ssh
apr/18/2019 06:07:36 system,error,critical login failure for user pi from 217.241.30.150 via ssh
apr/18/2019 06:07:36 system,error,critical login failure for user pi from 217.241.30.150 via ssh


What could be happening…whats the course and how can i stop it.

2

It seems that you have SSH open to access the router from the outside.
So anyone who tries port tcp/22 will be logged if they have wrong password.

BUT this is some you should not do. Do not open your router Winbox/SSH/Telnet/Web for admin access on outside.

If you need to use SSH from the outside you do not have many option.

  1. VPN (best option)

  2. Open SSH but:
    a. change to other port than 22
    b. set an access list to reduce who can access it
    c. use port knocking (google it)
    d. setup some monitoring. example getting email every time some logs inn
    e. create a new user and remove admin user
    f. use a very strong password
    g. +++

3

You may use firewall rules to prevent login brute-force: https://wiki.mikrotik.com/wiki/Bruteforce_login_prevention

4

With the wiki.. on the : address-list=ssh_blacklist : do we need to create somewhere the ssh_blacklist ? or it will be creating a log or something like that.. ?

And do we just add those action in the firewall filter just before the : :
add action=drop chain=forward comment=“defconf: drop invalid” connection-state=invalid

and is just this one can do the same :
add action=drop chain=forward in-interface=bridge1 src-address=!192.168.0.0/24 comment=“Drop all that do not match LAN IP”

So with this, can it then make the service port ssh and other less problematic and be leave on .. as only being possible to log via lan ip.?

Thanks

5

i have recent problem..
someone/thing tried to login via winbox but from the router IP itself (172.26.0.1) pics attached..
please, need help..
thank you..
Screen Shot 10-22-20 at 08.37 AM.JPG

6

Hopefully, you have already disabled the admin password and only use a trusted one you created. As noted, you should set up access so that only IP addresses from within your LAN can use winbox or HTTP to the router.

7

this looks more like TheDude … Probably added the device and now its trying to log in (enabled by default). find the device and uncheck “router OS” option in the details page.

8 
00:54:00 system,error,critical login failure for user  from 192.168.72.10 via ssh 
00:54:00 system,error,critical login failure for user admin from 192.168.72.10 via ssh 
00:54:00 system,error,critical login failure for user admin from 192.168.72.10 via ssh 
00:54:00 system,error,critical login failure for user MikroTikSystem from 192.168.72.10 via ssh 
00:54:00 system,error,critical login failure for user admin from 192.168.72.10 via ssh 
00:54:01 system,error,critical login failure for user dircreate from 192.168.72.10 via ssh 
00:54:01 system,error,critical login failure for user SolucTec from 192.168.72.10 via ssh 
00:54:01 system,error,critical login failure for user EServicios from 192.168.72.10 via ssh

I had the same symptoms of trying to access hapac2 from local on my windows 10 computer.

I assume that these accesses are from antivirus software to check for vulnerabilities.
Which antivirus software do you use?
I am using the free version of Avast.