In the ever-evolving landscape of cybersecurity threats, staying one step ahead of malicious actors is crucial.

Introducing Chista, an open-source Cyber Threat Intelligence (CTI) Framework designed to equip users with the tools and insights needed to understand, predict, and defend against cyber threats.

In this article, we’ll delve into how Chista harnesses data from various sources to provide invaluable intelligence, monitor threats, and empower organizations to bolster their cybersecurity defenses.

Chista is an Open Source Cyber Threat Intelligence (CTI) Framework designed to help users understand, predict and defend against cyber threats.

It helps its users understand cyber threats by using data collected from various sources. This data includes IOCs, data leaks, phishing campaigns, threat group activities and CTI sources. By analyzing this data, Chista helps users understand the existence, prevalence, trends and probability of cyber threats.

  • Collecting IOCs: IOCs are signatures used to identify and track cyber threats. Chista can collect IOCs from various sources and make them available to users.
  • Monitoring Data Leaks: Chista can identify accounts that have suffered a data breach by monitoring data leaks from various sources.
  • Monitoring Phishing Campaigns: Chista detects websites created for phishing purposes and provides users with a feed in this direction.
  • Monitoring Threat Groups Activities: Threat groups are organized groups that carry out cyber attacks. By monitoring threat group activity from various sources, Chista helps organizations understand and prepare for the activities of threat groups.
  • Detection of Blacklisted IPs: Chista provides users with a feed for IPs blacklisted by various lists.
  • Detailing Threat Groups: Chista brings together details of cybercrime groups, allowing users to get detailed information about threat groups.
  • Providing Resources: Chista provides resources that can be used for threat intelligence for the benefit of users interested in Cyber Threat Intelligence.

In this document, you’ll find usage & installation guide. You can check our detailed documentation about which includes developer documentation.

Table Of Contents

  • Install Chista
  • Basic Usage
  • Contributing
  • Credits

Install Chista


  • go1.21
  • Python 3.6+
    • It is needed for OpenSquat.
  • OpenSquat
  • API ID and API KEY
    • It’s used in Phishing module and controlled in .ENV file with CENSYS_API_SECRET key. We’ll see .ENV file in the Configuration section.
  • 7777 and 7778 ports should be available
  • google-chrome” executable file should present in $PATH
    • You need to install Google Chrome and it’s executable should be found in your PATH (Environment Variables in Windows)


The tool’s configurations is controlled with .ENV file. The .ENV file should placed in root directory of the project. You can see an example .ENV file in below.

ConfigurationDefault ValueDetailsMandatory/Optional
DUMP_MODEtrueIf it’s true, the API server logs the HTTP requests. It can be useful while debugging.Mandatory
API_ONLYfalseWhen it’s false, the API server generates a WebSocket connection to the CLI tool. So, if you want to use just API part of the tool, you have to set API_ONLY=trueMandatory’s used in whois checker, the tool queries to the given Whois Server.Mandatory
PY_PATHIt’s Python’s installation path. Python used for OpenSquat. If you want to use OpenSquat, you have to provide your Python path.Optional
OPENSQUAT_PY_PATH./3rd_party/opensquatOpenSquat folder’s path. The Phishing module uses OpenSquat to generate extra typosquatting domains.Optional API Key IDOptional API Key SecretOptional

Basic Usage

You can use pre-built binaries or you can build the project and use. It’s up to your choice!

Building And Running From Source

1. Clone The Repository

git clone

2. Build And Run The API Application

First, open a Command Prompt/Terminal. Then execute the following commands.

  • For Windows:
go build -o chista.exe

For Linux:

go build -o chista

NOTE: If you cannot execute the command in Linux, you should give execute permission yourself on the file. You can use chmod +x chista. After running the API server, you’ll see the following output.

time="2024-01-12T16:12:08+03:00" level=info msg="DUMP_MODE= true" file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/logger/logger.go:54"
time="2024-01-12T16:12:08+03:00" level=error msg="WebSocket connection error while closing: Websocket Connection is nil but trying to send a WS message." file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/helpers/helpers.go:230"
[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
 - using env:   export GIN_MODE=release
 - using code:  gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /api/v1/ioc_feed          --> (6 handlers)
[GIN-debug] GET    /api/v1/phishing          --> (6 handlers)
[GIN-debug] GET    /api/v1/impersonate       --> (6 handlers)
[GIN-debug] GET    /api/v1/leak              --> (6 handlers)
[GIN-debug] GET    /api/v1/threat_profile    --> (6 handlers)
[GIN-debug] GET    /api/v1/blacklist         --> (6 handlers)
[GIN-debug] GET    /api/v1/source            --> (6 handlers)
[GIN-debug] GET    /api/v1/c2                --> (6 handlers)
[GIN-debug] GET    /api/v1/activities        --> (6 handlers)
[GIN-debug] [WARNING] You trusted all proxies, this is NOT safe. We recommend you to set a value.
Please check for details.
[GIN-debug] Listening and serving HTTP on localhost:7777
time="2024-01-12T16:12:08+03:00" level=debug msg="Starting the Apt Profiles Data Check periodic function\n" file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/helpers/helpers.go:595"
time="2024-01-12T16:12:08+03:00" level=debug msg="Starting the Ransomware Profiles Data Check periodic function\n" file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/helpers/helpers.go:595"
time="2024-01-12T16:12:08+03:00" level=debug msg="Requesting source for ransom data." file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/controller/threat_profile.go:176"
time="2024-01-12T16:12:08+03:00" level=debug msg="Starting the Ransom Data Check periodic function\n" file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/helpers/helpers.go:595"
time="2024-01-12T16:12:08+03:00" level=debug msg="Requesting source for ransom data." file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/controller/activities.go:132"
time="2024-01-12T16:12:09+03:00" level=debug msg="Ransom data has been updated." file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/controller/threat_profile.go:212"
time="2024-01-12T16:12:09+03:00" level=info msg="Ransom data is up to date. No need to write to the file." file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/controller/activities.go:158"
time="2024-01-12T16:12:10+03:00" level=info msg="Apt profiles data is up to date. No need to write to the file." file="C:/Users/ResulBozburun/Desktop/Personal/Go/chista/controller/threat_profile.go:364"

Published by Tamil S

Tamil has a great interest in the fields of Cyber Security, OSINT, and CTF projects. Currently, he is deeply involved in researching and publishing various security tools with Kali Linux Tutorials, which is quite fascinating.

Leave a comment

Your email address will not be published. Required fields are marked *