For some reason you have hidden virtually all of the useful information from your question. However, yes it would mostly be hackers/bots searching for vulnerabilities. Some entries will be legitimate, and likely related to TCP sessions where your machine thinks the connection has been closed and forgotten, but the remote machine thinks it isn't.
Those log entries are probably from iptables log rules. If you are using UFW, know that it is just a front end for iptables. Notice that 7 out of 16 of your example list are from 79.124.62.86. Please know that particular sub-net is one of a great many that are very bad. This from my iptables rule set, where I DROP the entire sub-net:
doug@s15:~$ sudo iptables -xvnL
Chain INPUT (policy DROP 14 packets, 1478 bytes)
pkts bytes target prot opt in out source destination
...
2584 103392 DROP all -- enp1s0 * 79.124.0.0/18 0.0.0.0/0
...
Observe the rule has been hit 2584 times.
EDIT: By the way, I use the following method to find the worst players from the previous day (not including the ones I already specifically DROP):
doug@s15:~$ tail -20000 /var/log/syslog.1 | sed 's/ /\n/g' | grep "SRC=" | cut -d"." -f1,2,3,4 | sort | uniq -c | sort -g | tail -4
265 SRC=51.38.110.114
392 SRC=195.230.23.151
621 SRC=98.166.24.100
855 SRC=130.211.9.161
doug@s15:~$ tail -20000 /var/log/syslog.1 | sed 's/ /\n/g' | grep "SRC=" | cut -d"." -f1,2,3 | sort | uniq -c | sort -g | tail -4
392 SRC=195.230.23
429 SRC=162.142.125
621 SRC=98.166.24
855 SRC=130.211.9
doug@s15:~$ tail -20000 /var/log/syslog.1 | sed 's/ /\n/g' | grep "SRC=" | cut -d"." -f1,2 | sort | uniq -c | sort -g | tail -4
429 SRC=162.142
486 SRC=192.241
621 SRC=98.166
855 SRC=130.211
Note: I use tail
because I often only search the last few hundred lines.
Please, for your next question, give us more information to work with.
cat
, and look at surrounding lines:grep -A2 -B2 'SRC=' /var/log/syslog
. Usejournalctl
, a better way of handling logs. Readjournalctl
hints in my AskUbuntu profile.cat
command.