Skip to main content

threat hunting | finding beacons - part 2

beacon check is based on connection delta, session size or both. rita tool and its helpful easy command will help you to find beacons quite easily. 

RITA

rita | less         

(list all of rita's commands.)

rita list            

lab1

lab2

lab3

(list all of the known databases. pcap lab files need to import into                         rita.)

rita import <zeek log files>       

(it will import zeek log files.) 

rita | grep beacons 

rita show-beacons lab1 -H | less -S   

(lab1 is your dataset that you import                                                              earlier) 

anything that score starting from 0.8, please investigate. 


Now using that two ip's, check with dns logs.

first two dns query comes with nothing. that means these two ip's is not resolving dns names. thats kind of suspicious. so lets search for what service they try to reach. 

1st one says http and 2nd one says nothing. which is weird. 


 

 

conn_state means --> what tcp flags zeek seen in the packet. 

OTH means --> it did not see 3 tcp packet at the beginning and fin/ack or RST at the end. just see established connection in the middle. all 72 connections use same source port and same destination port. zeek by default has 5 minutes sesison time out. this is why it is unable to decode service. if zeek does not see any packet goes by on that session for 5 minutes then remove that entry from its state table and starts from a newer one when same session starts communicating again. change it to 60 minutes or higher. 

 

rita show-beacons-fqdn lab1  

(show beacons between internal ip and external fqdn)

rita show-beacons-proxy lab1  

(all of my internal ip are going to same proxy server. from that proxy server they go to internet. from that proxy where they trying to go out to, this command will find you that)

 

Avi

 

Comments

Post a Comment

Popular posts from this blog

Install Nessus from docker

The below two commands you need to run first one by one:  docker run -itd --name=ramisec_nessus -p 8834:8834 ramisec/nessus docker exec -it ramisec_nessus /bin/bash /nessus/update.sh Username: admin And you need to change the password: #Enter the command line of the docker container docker exec -it ramisec_nessus bash #Execute the following commands in sequence # Enter this directory cd /opt/nessus/sbin # List logged in users ./nessuscli lsuser # Modify the password of the specified user (take admin as an example) ./nessuscli chpasswd admin After access to the nessus, make sure you turn off the automatic updates otherwise crack will not work after some time. Before any scan you need to run the update.sh command (shown above) to have the latest plugins. Now everytime your system reboots, your docker instance will be shutdown. You need to up it again manually. Here are the commands.  1. docker ps -a    Now note down the container id. 2. docker start <container id> C
Post a Comment
Read more

net command cheat sheet

  To see what users present in the system: net user To see local groups in the system: net localgroup To see domain groups. This should be run on a domain controller: net group To see the details of a user along with his/her group membership: net user mahim To see who are the members of a particular group (local machine): net localgroup "administrators"    (These are not case sensitive. You can use administrators or Administrators. Both will give you same result. To see who are the members of a particular group (domain machine): net group "domain admins" Create a local user: net user localuser1 MyP@ssw0rd /add Create a domain user: net user domainuser1 MyP@ssw0rd /add /domain Add the local user to local admin group: net localgroup Administrators localuser1 /add Add the user to domain admin group: net group "Domain Admins" domainuser1 /add /domain Avi
Post a Comment
Read more