Many honeypots are no longer maintained and it has become hard to run and test them as libraries and packages evolve.
In an aim to preserve them, we have started adopting some honeypots. What does this mean? The adoption work involves forking or migrating the code to our GitHub organisation, improving the documentation when appropriate, creating a docker image or package that can be used to run the honeypot without having dependencies issues and providing LTS.
The honeypots below have been adopted, are working and have a usable package or Docker image that can be used to run the honeypot without dependencies issues.
| Honeypot | Adopter | Docker Image | Last commit | DockerHub pulls |
|---|---|---|---|---|
| Delilah | @verovaleros | Yes |  |
 |
| Honeyprint | @verovaleros | Yes |  |
 |
| NoSQLpot | @verovaleros | Yes |  |
 |
| wordpot | @verovaleros | Yes |  |
 |
-
If you created a honeypot and do not wish to maintain it anymore, create an issue to get in contact with us to coordinate the adoption. Please include:
- the honeypot name
- the type of the honeypot (database honeypot, service honeypot, web honeypot, etc)
- the interaction level (high, medium, low)
- the language in which the honeypot is written
- the link to the code
-
If you found an orphan honeypot, please create an issue with its details so we can take a look at it and investigate the possibility of adopting it.