How u7dani/phishscope works
Project type and purpose
• PhishScope is a standalone, OSINT-defensive, batch-processing tool written in Python.
File structure
• Top-level files:
• phiscope_batch.py – the main entry point and orchestrator of the analysis pipeline
• requirements_linux.txt / requirements_windows.txt – dependency lists for each OS
• README.md, LICENSE, .gitignore – project metadata
• Implicit subfolder (per README):
• email/ – directory where .eml files are placed
• resultados_phishscope.xlsx – the generated output
README for architectural insights
• The tool is linear and batch-oriented: read emails → run analyzers → aggregate scores → output Excel.
• External interactions: DNS queries (SPF/DKIM/DMARC), HTTP HEAD requests (URL resolution).
• Core technologies: Python 3.9+, NLP embeddings library, openpyxl (or similar) for Excel.
Main components and interactions
a. Input Component
• Email Loader: scans email/ directory for .eml files
b. Processing Components (each can be a sub-module or class within phiscope_batch.py)
1. Email Parser – extracts headers, body, attachments
2. NLP Analyzer – computes semantic embeddings and urgency patterns
3. URL Resolver – extracts URLs, follows redirects via HTTP HEAD
4. Authenticator – performs DNS-based SPF, DKIM, DMARC checks
5. Attachment Scanner – hashes attachments, flags suspicious types
6. Scoring Engine – weights and aggregates all signals into PhishScore
c. Output Component
d. External Services
• DNS Servers – for SPF/DKIM/DMARC lookups
• Remote HTTP Servers – for URL redirections
Architectural patterns and design principles
• Pipeline pattern: each email flows through a fixed sequence of analyzers.
• Single process, modular components – easy to extend by adding new analyzers.
• Configuration via requirements files and optional PhishScore weight adjustments.
• CLI-driven with no persistent server or database.