Add SERVER_HEADER environment variable to customize the HTTP Server response header, defaulting to Apache/2.2.22 (Ubuntu). This allows the honeypot to masquerade as different web servers to attract attackers. - Add server_header field to Config dataclass - Override version_string() in Handler to return configured header - Update documentation and all deployment configs
9.4 KiB
🕷️ Krawl
A modern, customizable zero-dependencies honeypot server designed to detect and track malicious activity through deceptive web pages, fake credentials, and canary tokens.
What is Krawl? • Quick Start • Honeypot Pages • Dashboard • Todo • Contributing
Star History
What is Krawl?
Krawl is a cloud‑native deception server designed to detect, delay, and analyze malicious web crawlers and automated scanners.
It creates realistic fake web applications filled with low‑hanging fruit such as admin panels, configuration files, and exposed fake credentials to attract and identify suspicious activity.
By wasting attacker resources, Krawl helps clearly distinguish malicious behavior from legitimate crawlers.
It features:
- Spider Trap Pages: Infinite random links to waste crawler resources based on the spidertrap project
- Fake Login Pages: WordPress, phpMyAdmin, admin panels
- Honeypot Paths: Advertised in robots.txt to catch scanners
- Fake Credentials: Realistic-looking usernames, passwords, API keys
- Canary Token Integration: External alert triggering
- Real-time Dashboard: Monitor suspicious activity
- Customizable Wordlists: Easy JSON-based configuration
- Random Error Injection: Mimic real server behavior
🚀 Quick Start
Helm Chart
Install with default values
helm install krawl oci://ghcr.io/blessedrebus/krawl-chart \
--namespace krawl-system \
--create-namespace
Install with custom canary token
helm install krawl oci://ghcr.io/blessedrebus/krawl-chart \
--namespace krawl-system \
--create-namespace \
--set config.canaryTokenUrl="http://your-canary-token-url"
To access the deception server
kubectl get svc krawl -n krawl-system
Once the EXTERNAL-IP is assigned, access your deception server at:
http://<EXTERNAL-IP>:5000
Kubernetes / Kustomize
Apply all manifests with
kubectl apply -f https://raw.githubusercontent.com/BlessedRebuS/Krawl/refs/heads/main/manifests/krawl-all-in-one-deploy.yaml
Retrieve dashboard path with
kubectl get secret krawl-server -n krawl-system -o jsonpath='{.data.dashboard-path}' | base64 -d
Or clone the repo and apply the manifest folder with
kubectl apply -k manifests
Docker
Run Krawl as a docker container with
docker run -d \
-p 5000:5000 \
-e CANARY_TOKEN_URL="http://your-canary-token-url" \
--name krawl \
ghcr.io/blessedrebus/krawl:latest
Docker Compose
Run Krawl with docker-compose in the project folder with
docker-compose up -d
Stop it with
docker-compose down
Python 3.11+
Clone the repository
git clone https://github.com/blessedrebus/krawl.git
cd krawl/src
Run the server
python3 server.py
Visit
http://localhost:5000
To access the dashboard
http://localhost:5000/<dashboard-secret-path>
Configuration via Environment Variables
To customize the deception server installation several environment variables can be specified.
| Variable | Description | Default |
|---|---|---|
PORT |
Server listening port | 5000 |
DELAY |
Response delay in milliseconds | 100 |
LINKS_MIN_LENGTH |
Minimum random link length | 5 |
LINKS_MAX_LENGTH |
Maximum random link length | 15 |
LINKS_MIN_PER_PAGE |
Minimum links per page | 10 |
LINKS_MAX_PER_PAGE |
Maximum links per page | 15 |
MAX_COUNTER |
Initial counter value | 10 |
CANARY_TOKEN_TRIES |
Requests before showing canary token | 10 |
CANARY_TOKEN_URL |
External canary token URL | None |
DASHBOARD_SECRET_PATH |
Custom dashboard path | Auto-generated |
PROBABILITY_ERROR_CODES |
Error response probability (0-100%) | 0 |
SERVER_HEADER |
HTTP Server header for deception | Apache/2.2.22 (Ubuntu) |
robots.txt
The actual (juicy) robots.txt configuration is the following
Disallow: /admin/
Disallow: /api/
Disallow: /backup/
Disallow: /config/
Disallow: /database/
Disallow: /private/
Disallow: /uploads/
Disallow: /wp-admin/
Disallow: /phpMyAdmin/
Disallow: /admin/login.php
Disallow: /api/v1/users
Disallow: /api/v2/secrets
Disallow: /.env
Disallow: /credentials.txt
Disallow: /passwords.txt
Disallow: /.git/
Disallow: /backup.sql
Disallow: /db_backup.sql
Honeypot pages
Requests to common admin endpoints (/admin/, /wp-admin/, /phpMyAdmin/) return a fake login page. Any login attempt triggers a 1-second delay to simulate real processing and is fully logged in the dashboard (credentials, IP, headers, timing).
Requests to paths like /backup/, /config/, /database/, /private/, or /uploads/ return a fake directory listing populated with “interesting” files, each assigned a random file size to look realistic.
The .env endpoint exposes fake database connection strings, AWS API keys, and Stripe secrets. It intentionally returns an error due to the Content-Type being application/json instead of plain text, mimicking a “juicy” misconfiguration that crawlers and scanners often flag as information leakage.
The pages /api/v1/users and /api/v2/secrets show fake users and random secrets in JSON format
The pages /credentials.txt and /passwords.txt show fake users and random secrets
Customizing the Canary Token
To create a custom canary token, visit https://canarytokens.org
and generate a “Web bug” canary token.
This optional token is triggered when a crawler fully traverses the webpage until it reaches 0. At that point, a URL is returned. When this URL is requested, it sends an alert to the user via email, including the visitor’s IP address and user agent.
To enable this feature, set the canary token URL using the environment variable CANARY_TOKEN_URL.
Customizing the wordlist
Edit wordlists.json to customize fake data for your use case
{
"usernames": {
"prefixes": ["admin", "root", "user"],
"suffixes": ["_prod", "_dev", "123"]
},
"passwords": {
"prefixes": ["P@ssw0rd", "Admin"],
"simple": ["test", "password"]
},
"directory_listing": {
"files": ["credentials.txt", "backup.sql"],
"directories": ["admin/", "backup/"]
}
}
or values.yaml in the case of helm chart installation
Dashboard
Access the dashboard at http://<server-ip>:<port>/<dashboard-path>
The dashboard shows:
- Total and unique accesses
- Suspicious activity detection
- Top IPs, paths, and user-agents
- Real-time monitoring
The attackers' triggered honeypot path and the suspicious activity (such as failed login attempts) are logged
The top IP Addresses is shown along with top paths and User Agents
Retrieving Dashboard Path
Check server startup logs or get the secret with
kubectl get secret krawl-server -n krawl-system \
-o jsonpath='{.data.dashboard-path}' | base64 -d && echo
🤝 Contributing
Contributions welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request (explain the changes!)
⚠️ Disclaimer
This is a deception/honeypot system.
Deploy in isolated environments and monitor carefully for security events.
Use responsibly and in compliance with applicable laws and regulations.










