<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ssh on Joshua's Notebook</title><link>https://burnett.sh/tags/ssh/</link><description>Recent content in Ssh on Joshua's Notebook</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 26 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://burnett.sh/tags/ssh/index.xml" rel="self" type="application/rss+xml"/><item><title>HoneyPi: First Attack Observation</title><link>https://burnett.sh/posts/honeypi-observation1/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://burnett.sh/posts/honeypi-observation1/</guid><description>&lt;p&gt;The full setup and configuration process behind HoneyPi was documented in the earlier parts of this series, so this post skips the build and goes straight to the first attack observation report I put together for my SANS Internet Storm Center internship. It focuses on a single attacker and walks it end to end.&lt;/p&gt;
&lt;h2 id="initial-attack-observation"&gt;Initial Attack Observation&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Time and Date of Activity:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;2026-06-15 00:00:07 UTC through 2026-06-17 02:11:21 UTC&lt;/p&gt;
&lt;p&gt;The attacker (source 87.251.64.176) was active for around 45 hours, with 114 successful logins occurring in bursts, indicating automated tooling running through a set of target IPs/hosts. Successful logins would occur in a burst, quiet down for a couple of hours then another burst. It should be noted that similar SSH-2.0-Go campaigns have been observed from other attackers since deployment of the HoneyPi, however this particular attacker was interesting because its attack pattern was persistent and observed from a single source, rather than cycling through different IPs like in other campaigns.&lt;/p&gt;</description></item></channel></rss>