https://github.com/juanvilla424/anisakys
Open Phishing Monitor Daemon. Scan similar domains based on world keys. Report to Abuse Inbox, Threat Hunt.
https://github.com/juanvilla424/anisakys
blue cannon hunting monitor phishing python red scan security security-tools tool
Last synced: 7 months ago
JSON representation
Open Phishing Monitor Daemon. Scan similar domains based on world keys. Report to Abuse Inbox, Threat Hunt.
- Host: GitHub
- URL: https://github.com/juanvilla424/anisakys
- Owner: JuanVilla424
- License: gpl-3.0
- Created: 2025-02-23T19:51:52.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2025-03-31T00:42:39.000Z (7 months ago)
- Last Synced: 2025-04-09T05:33:23.724Z (7 months ago)
- Topics: blue, cannon, hunting, monitor, phishing, python, red, scan, security, security-tools, tool
- Language: Python
- Homepage:
- Size: 154 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
README
# 🔍 Anisakys
[](https://www.gnu.org/licenses/gpl-3.0.en.html)
## Overview
Anisakys is an automated phishing detection engine that identifies suspicious domains through combinatorial analysis and content pattern matching. Designed for blue teams and security analysts, it generates domain permutations from keyword lists and scans for phishing indicators.
## 📚 Table of Contents
- [Features](#-features)
- [Getting Started](#-getting-started)
- [Prerequisites](#-prerequisites)
- [Installation](#-installation)
- [Usage](#-usage)
- [Contributing](#-contributing)
- [License](#-license)
- [Contact](#-contact)
## 🌟 Features
- 🌀 Dynamic domain permutation generation
- 🔍 Content-based phishing pattern detection
- ⚡ Multi-threaded scanning (20 concurrent workers)
- 📊 Smart logging with duplicate prevention
- 🛡️ DNS failure noise reduction
- 🔄 Continuous scanning mode with configurable intervals
## 🚀 Getting Started
### 📋 Prerequisites
**Before you begin, ensure you have met the following requirements**:
- Python 3.10+
- Linux/macOS (Windows not recommended)
### 🔨 Installation
1. **Clone the Repository:**
```bash
git clone https://github.com/JuanVilla424/anisakys.git
cd anisakys
```
2. **Create a Virtual Environment**
```bash
python -m venv venv
```
3. **Activate the Virtual Environment**
On Unix or MacOS:
```bash
source venv/bin/activate
```
4. **Upgrade pip**
```bash
python -m ensurepip
pip install --upgrade pip
```
5. **Install Dependencies**
```bash
pip install -r requirements.txt
```
- or if u prefer use poetry:
```bash
pip install poetry
poetry lock
poetry install
```
- **When you're done**, deactivate the environment:
```bash
deactivate
```
6. **Set Up Environment Variables**
- Rename the `.env.example` file to `.env`:
```bash
cp .env.example .env
```
- Open the `.env` file and configure the environment variables as needed.
## 🛠️ Usage
### 🪃 **Running App**
- Run the container with the necessary environment variables:
```bash
cd anisakys
python anisakys.py --timeout 20 --log-level INFO
```
### 🕸️ **Select Site as Phishing**
- Report Thread can be managed externally from scan by invoke main script again using --report
```bash
cd anisakys
python anisakys.py --report "https://sub.domain.com"
```
**Make Sure the Site is 100% a Phishing Site**
### 👾 **Report Selected Phishing Sites**
- as --report, --process-reports run detached from scan.
```bash
cd anisakys
python anisakys.py --process-reports --attachment attachments/law_file.pdf --cc="email@domain.com,email2@domain.com"
```
### ➿ **Continuous Subsequently Reports**
- System has ability to run without scans just doing manual reporting by --report and perform continuous reports on critical sites needing attention by resend reports auto.
```bash
cd anisakys
python anisakys.py --threads-only
```
## 🤝 Contributing
**Contributions are welcome! To contribute to this repository, please follow these steps**:
1. **Fork the Repository**
2. **Create a Feature Branch**
```bash
git checkout -b feature/your-feature-name
```
3. **Commit Your Changes**
```bash
git commit -m "feat(): your feature commit message - lower case"
```
4. **Push to the Branch**
```bash
git push origin feature/your-feature-name
```
5. **Open a Pull Request into** `dev` **branch**
Please ensure your contributions adhere to the Code of Conduct and Contribution Guidelines.
# _Disclaimer_
The contents of this repository are provided "as is" for informational purposes only. The authors and contributors make no warranties—express or implied—regarding the accuracy, completeness, or suitability of the information herein. Use of this repository is at your own risk, and no liability is assumed for any errors or omissions.
## 📫 Contact
For any inquiries or support, please open an issue or contact [r6ty5r296it6tl4eg5m.constant214@passinbox.com](mailto:r6ty5r296it6tl4eg5m.constant214@passinbox.com).
---
## 📜 License
2025 - This project is licensed under the [GNU General Public License v3.0](https://www.gnu.org/licenses/gpl-3.0.en.html). You are free to use, modify, and distribute this software under the terms of the GPL-3.0 license. For more details, please refer to the [LICENSE](LICENSE) file included in this repository.