HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MegaManSec
SSH-Snake
Shell2024–2024
MegaManSec / SSH-Snake

SSH-Snake

SSH-Snake is a self-propagating, self-replicating, file-less script that automates the post-exploitation task of SSH private key and host discovery.

Command LineSecurity & PrivacyNetworking
Explore on GitHubRead Hacker News discussions
2Distinct people
6Mentions
0Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SSH-Snake is a self-propagating, self-replicating, file-less script that automates the post-exploitation task of SSH private key and host discovery.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval6 dated mentions

Observed mentions: 2024-01-02 17:31:03 UTC to 2024-01-06 15:38:10 UTC.

0122024-01-02 12:00:00 UTC to 2024-01-02 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2, 12:002024-01-02 18:00:00 UTC to 2024-01-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-03 00:00:00 UTC to 2024-01-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-03 06:00:00 UTC to 2024-01-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-03 12:00:00 UTC to 2024-01-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-03 18:00:00 UTC to 2024-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-04 00:00:00 UTC to 2024-01-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-04 06:00:00 UTC to 2024-01-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-04 12:00:00 UTC to 2024-01-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 4, 12:002024-01-04 18:00:00 UTC to 2024-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-05 00:00:00 UTC to 2024-01-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-05 06:00:00 UTC to 2024-01-05 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-05 12:00:00 UTC to 2024-01-05 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-05 18:00:00 UTC to 2024-01-06 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-06 00:00:00 UTC to 2024-01-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-06 06:00:00 UTC to 2024-01-06 12:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-06 12:00:00 UTC to 2024-01-06 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 6, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 2, 12:002024-01-02 12:00:00 UTC2024-01-02 18:00:00 UTC101
Jan 2, 18:002024-01-02 18:00:00 UTC2024-01-03 00:00:00 UTC000
Jan 3, 00:002024-01-03 00:00:00 UTC2024-01-03 06:00:00 UTC000
Jan 3, 06:002024-01-03 06:00:00 UTC2024-01-03 12:00:00 UTC000
Jan 3, 12:002024-01-03 12:00:00 UTC2024-01-03 18:00:00 UTC000
Jan 3, 18:002024-01-03 18:00:00 UTC2024-01-04 00:00:00 UTC000
Jan 4, 00:002024-01-04 00:00:00 UTC2024-01-04 06:00:00 UTC000
Jan 4, 06:002024-01-04 06:00:00 UTC2024-01-04 12:00:00 UTC000
Jan 4, 12:002024-01-04 12:00:00 UTC2024-01-04 18:00:00 UTC000
Jan 4, 18:002024-01-04 18:00:00 UTC2024-01-05 00:00:00 UTC000
Jan 5, 00:002024-01-05 00:00:00 UTC2024-01-05 06:00:00 UTC000
Jan 5, 06:002024-01-05 06:00:00 UTC2024-01-05 12:00:00 UTC110
Jan 5, 12:002024-01-05 12:00:00 UTC2024-01-05 18:00:00 UTC000
Jan 5, 18:002024-01-05 18:00:00 UTC2024-01-06 00:00:00 UTC110
Jan 6, 00:002024-01-06 00:00:00 UTC2024-01-06 06:00:00 UTC000
Jan 6, 06:002024-01-06 06:00:00 UTC2024-01-06 12:00:00 UTC202
Jan 6, 12:002024-01-06 12:00:00 UTC2024-01-06 18:00:00 UTC101

What Hacker News says

6 sources
mmsc·Jan 6, 2024
or for example, if the config file sets `PubkeyAcceptedAlgorithms=+ssh-rsa` which is necessary It already does this: https://github.com/MegaManSec/SSH-Snake/blob/7ae7ef0afe0e067... and https://github.com/MegaManSec/SSH-Snake/blob/7ae7ef0afe0e067... I see no downside to just using the hostname from the config file It already does this: https://github.com/MegaManSec/SSH-Snake/blob/main/Snake.sh#L... the config file specifies a port besides 22, it won't be able to connect to that host This shouldn't be hard to implement and can certainly be added in a later version.
In SSH-Snake: Automated SSH-Based Network Traversal

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.