Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
sshhipot — High-interaction MitM SSH honeypot | Kitploit
Tools/GitHubGitHub/magisterquis/sshhipot
Defensive ToolsNetwork SecurityPenetration TestingRed Teaming
GitHubmagisterquis/sshhipot

sshhipot

High-interaction MitM SSH honeypot

View Repository
175478 years agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Version 2 is under development. Please switch to the v2 branch, build, and run with -h.

SSHHiPot

High-interaction SSH honeypot (ok, it's really a logging ssh proxy).

Still more or less a work-in-progress. Feel free to go install this repository if you'd like to try it. Run it with -h to see more options. In particular, logging is kinda rough.

One of these days there'll be better documentation, really.

The general idea is that sshlowpot runs somewhere between the attacker and the real SSH server such that the attacker logs into the honeypot, and the honeypot logs into the server.

Contact

At this stage in its development, it's probably easier to find me on Freenode than anything, though reading the source is another option. It's not that painful. I can usually be found as magisterquis in #devious on freenode.

Installation

root@kitploit:~
go install github.com/magisterquis/sshhipot

If you don't have go available, feel free to ask me (or someone who does) for compiled binaries. They can be made for a bunch of different platforms.

Config

Most of the options should be useable as-is. The ones I expect will need to be configured:

Please note by default the server listens on port 2222. You'll have to use pf or iptables or whatever other firewall to redirect the port. It's probably a really bad idea to run it as root. Don't do that.

There is a general log which goes to stdout. More granular logs go in a directory named conns by default (-d flag). At the moment, the granular logs also go to stderr.

Contributions

Yes, please.

Windows

It's in Go, so, probably? Send me a pull request if it doesn't work.

Download Tool
OptionUse
-ckSSH identity file (i.e. id_rsa) to use to authenticate to the server.
-csServer's address. Can be loopback, even.
-cuOk, maybe root wasn't a great default. test is probably better.
-pTry 123456 or something more common than hunter2. Also see the -pf flag.
-sfFingerprint of real server's Host Key (retreivable with `ssh-keyscan hostname 2>/dev/null