Open-Source Intelligence Apparatus
Centralize and expedite OSINT investigations
View the roadmap
Bitcrook is an open-source intelligence apparatus that aims to centralize all of the tools necessary to carry out an investigation. Although investigations will still require human interaction to connect the dots, the interface can be tailored to an individual’s needs to expedite the process of due diligence. Some packages do require an authentication key and others do not. See the Package Types tables for more information. Bitcrook can be integrated within your application OR it can be used directly from the terminal/web browser.
It is the end user's responsibility to obey all applicable local, state, and federal laws. Developers assume no liability and are not responsible for any misuse or damage caused by this program. By using Bitcrook, you agree to the previous statements.
Bitcrook v2.0.0 has been released as of October 11, 2023, only one day after v1.0.0 due to some significant changes to project structure. Here are some highlights of the recent changes in the v1.0.0 and v2.0.0 releases:
go install
git clone https://github.com/ax-i-om/bitcrook.git
or
go install github.com/ax-i-om/bitcrook@latest
cd
go run main.go
cd
go run main.go server
http://127.0.0.1:6174
You can also host the Bitcrook webapp via docker:
cd
docker build -t bitcrook .
docker run --restart always --env-file .env --name bitcrook -d -p 6174:6174 bitcrook
http://127.0.0.1:6174
Some packages require an API key. Bitcrook will run without specifying any API keys; however, if you would like to implement these functionalites, create a file named .env
and format it like so:
BITCROOK_MLSA=UNSPECIFIED
BITCROOK_HIBP=UNSPECIFIED
BITCROOK_IPTL=UNSPECIFIED
Replace the instances of UNSPECIFIED
with the corresponding API key.
From top to bottom, these environment variables should correspond with the API keys for the services Melissa, HaveIBeenPwned, and IP2Location. Insure that the environnment variables are passed/exported after making any changes. For Docker, append --env-file .env
to the arguments. In Linux, run the command: export $(xargs <.env)
. Results may vary depending on your operating system/shell.