What is a honeypot:
In computer terminology, a honeypot is a computer security mechanism set to detect, deflect, or, in some manner, counteract attempts at unauthorized use of information systems. Generally, a honeypot consists of data (for example, in a network site) that appears to be a legitimate part of the site that seems to contain information or a resource of value to attackers, but actually, is isolated and monitored and enables blocking or analyzing the attackers. This is similar to police sting operations, colloquially known as “baiting” a suspect.
Why set up a honeypot:
Many bad bots will try to attack/DDoS your site. Those same bots will also go to other sites. So, with this honeypot, you can help other people by warning them.
How to set it up:
- Remix the project here.,
- Get a AbuseIPDB API key here.
- Place the AbuseIPDB key in the .env file under
ABUSEIPDB_API_KEY. It looks like this:
ABUSEIPDB_API_KEY=<PLACE API KEY HERE>
How to add more traps:
All traps are stored in
routes.js. A normal entry looks something like:
"/path/to/trap": ["15,19","A normal description."]
If you visit PROJECT_NAME.glitch.me/path/to/trap, then you would be reported for “A normal description.” with the tags ‘Hacking’ and ‘Bad web bot’
This explains more:
"/trap": ["category,category", "Description"]
- “/trap”: The path to the trap (website.com/trap)
- “category,category”: are the nubers assoicated with categories of attacks. Can be found here
- “Description”: The description of the attack
Thanks @RiversideRocks for the traps and the main idea.
You can also see the honeypot in action by going to my profile at: https://www.abuseipdb.com/user/49168
GitHub URL: https://github.com/aboutDavid/honeypot