ZeekBox (until I have a better name)

Synopsis: an all in one traffic analysis and capture box specifically designed for OPSEC management during malware analysis, especially on a physical phone (iPhone or Android device).

My vision for this project looks something like this:

Runs on a Raspberry Pi
Connected to the internet over Ethernet
Starts a wifi access point that goes through a VPN (or list of VPNs that can be cycled through)
Runs Zeek (and Suricata?) listening to the wifi before the vpn
A few buttons (and maybe a LCD) on the physical device
One button says “start capture” and the other says “finish capture”
Basically before you run some malware you hit start and when you’re done you hit finish
After a capture, a script gathers up the Zeek logs and other info for that session and sends it to you in a report
Other useful options in the future, such as automatic mitmproxy
Useful Android tools such as Frida if you connect the device over USB

Essentially, let's say I have some malware (or potential malware) on an Android phone, but that malware has anti-analysis capabilities. I can connect my phone to the ZeekBox, which will provide a VPN protected connection (masking my true IP address) without the device itself having a VPN configured. Before I execute the malware, I hit the "start capture" button on the Pi. I run the malware and interact with it. When I'm done, I hit "stop capture." The system then analyzes the logs and delivers me an email with useful reporting information (summary info) about the session and an attachment with the Zeek logs (Zip file) and perhaps a full PCAP as well.

Pi Setup

I'm running Ubuntu Server on my pi. Here are some notes:

provision_pi.sh will attempt to set up your pi
You'll need to disable systemd listening on port 53: https://www.linuxuprising.com/2020/07/ubuntu-how-to-free-up-port-53-used-by.html
You'll need to enable SPI communication by installing raspi-config and enabling it

Usage

Bare-bones so far, just testing out how it might work. See collector.rb for the basic skeleton

Building the container

To build:

Clone the repo: git clone https://github.com/rvictory/zeek-box
Build the container: cd zeek-box && sudo docker build -t zeek_box .

To run the docker container: make run

Note: If you want to use OpenVPN username/password auth, for now you need to volume bind an auth.txt file into the container at /etc/openvpn/auth.txt with your username on one line and your password on the next. You also need to bring in your OpenVPN configuration files and add them to the container and then set the environmental variable OPEN_VPN_CONF_FILE to the path to the file. One final note: in the .ovpn files, change auth-user-pass to auth-user-pass auth.txt.

NordVPN Conf files: https://nordvpn.com/ovpn/

TODO This whole explanation above needs to be cleaned up

E-Ink Display

I'm using an eInk display from Waveshare (link to Amazon)

Things to use later:

https://github.com/SebastianJ/nordvpn-api

Test Data

Some of the test data (in tests/data/logs) has been sourced from https://github.com/brimdata/zed-sample-data and is licensed under the license terms found in that repository (Creative Commons Attribution-ShareAlike 4.0 International License as of October 9th, 2022)

Using StarVPN

Set the environmental variable "USE_STARVPN" to anything
Add your StarVPN configuration file to your open_vpn_conf_files directory (call it starvpn.ovpn)
Make sure your username and password are in the configuration file
Rotation won't work after this (TODO add API rotation)

rvictory/zeek-box