<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://echo01409.github.io//</id><title>Ben H</title><subtitle>A minimal, responsive and feature-rich Jekyll theme for technical writing.</subtitle> <updated>2026-04-03T13:37:50+01:00</updated> <author> <name>Ben Hopkins</name> <uri>https://echo01409.github.io//</uri> </author><link rel="self" type="application/atom+xml" href="https://echo01409.github.io//feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://echo01409.github.io//"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Ben Hopkins </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Mustang Panda - When Operationalising IoCs Don't Go To Plan</title><link href="https://echo01409.github.io//posts/mustang-panda/" rel="alternate" type="text/html" title="Mustang Panda - When Operationalising IoCs Don&amp;apos;t Go To Plan" /><published>2026-01-28T00:00:00+00:00</published> <updated>2026-01-28T00:00:00+00:00</updated> <id>https://echo01409.github.io//posts/mustang-panda/</id> <content type="text/html" src="https://echo01409.github.io//posts/mustang-panda/" /> <author> <name>Ben Hopkins</name> </author> <category term="CTI" /> <category term="Nation State" /> <category term="China" /> <summary>Overview Recently I’ve been looking to improve my threat actor infrastructure tracking capabilities, and dust off my IOC pivoting skills—given I’ve spent considerable time lately building infrastructure as code and exploring AI capabilities rather than pure threat analysis full time. To that end, I found a great writeup by Kaspersky where they explored one of the latest campaigns conducted by ...</summary> </entry> <entry><title>XenoRAT - Builder Analysis</title><link href="https://echo01409.github.io//posts/xenorat/" rel="alternate" type="text/html" title="XenoRAT - Builder Analysis" /><published>2026-01-24T00:00:00+00:00</published> <updated>2026-01-24T00:00:00+00:00</updated> <id>https://echo01409.github.io//posts/xenorat/</id> <content type="text/html" src="https://echo01409.github.io//posts/xenorat/" /> <author> <name>Ben Hopkins</name> </author> <category term="Malware" /> <category term="RATs" /> <category term="Builder" /> <category term="DotNet" /> <summary>Overview So, its been a few weeks since I’ve done any analysis given we’ve just come off the christmas break. Before then, I was neck deep into North Korean malware. Coming off the back of Christmas, I wanted to warm myself back up and get this blog rolling properly. I routinely scan dark web sources for new remote access trojan (RAT) leaks, data leaks, and any high quality information that I ...</summary> </entry> <entry><title>Return of the Phemedrone Stealer - Part Two</title><link href="https://echo01409.github.io//posts/phenedrome-part-2/" rel="alternate" type="text/html" title="Return of the Phemedrone Stealer - Part Two" /><published>2025-07-13T00:00:00+01:00</published> <updated>2025-07-13T00:00:00+01:00</updated> <id>https://echo01409.github.io//posts/phenedrome-part-2/</id> <content type="text/html" src="https://echo01409.github.io//posts/phenedrome-part-2/" /> <author> <name>Ben Hopkins</name> </author> <category term="Malware" /> <category term="Loader" /> <category term="DotNet" /> <summary>Overview In the last blog, I covered a campaign that was being conducted by a cybercriminal using the Phenedrome stealer, which hasn’t been seen in a while. In the last blog, I covered the fake AnyDesk website stood up by the threat actor, and how that was used to socially engineer a victim into downloaded a loader for Phenedrome. If you want to read that blog first, feel free to go to the lin...</summary> </entry> <entry><title>Return of the Phemedrone Stealer - Part One</title><link href="https://echo01409.github.io//posts/phenedrome-part-1/" rel="alternate" type="text/html" title="Return of the Phemedrone Stealer - Part One" /><published>2025-06-20T00:00:00+01:00</published> <updated>2025-06-20T00:00:00+01:00</updated> <id>https://echo01409.github.io//posts/phenedrome-part-1/</id> <content type="text/html" src="https://echo01409.github.io//posts/phenedrome-part-1/" /> <author> <name>Ben Hopkins</name> </author> <category term="Malware" /> <category term="Loader" /> <category term="DotNet" /> <summary>Overview A few days ago, I was scrolling X (formally Twitter) where I follow other people in the cyber community, and came across a post about a threat actor impersonating the AnyDesk website to socially engineer victims into downloading malware. AnyDesk is a remote mangement and monitoring (RMM) tool that has platform-independant remote access solutions that IT support can use to service user...</summary> </entry> <entry><title>Async RAT - Analysis</title><link href="https://echo01409.github.io//posts/async-rat/" rel="alternate" type="text/html" title="Async RAT - Analysis" /><published>2025-02-15T00:00:00+00:00</published> <updated>2025-06-15T16:54:38+01:00</updated> <id>https://echo01409.github.io//posts/async-rat/</id> <content type="text/html" src="https://echo01409.github.io//posts/async-rat/" /> <author> <name>Ben Hopkins</name> </author> <category term="Malware" /> <category term="RATs" /> <summary>Overview AsyncRAT is a remote access trojan (RAT) built to remotely monitor and control other computers through a secure, encrypted connection. The name “AsyncRAT” comes from its core functionality—’async’ means it performs its operations asynchronously, which means it is capable of executing several tasks simultaneously. AsyncRAT has been observed as being bought, sold, and deployed for years...</summary> </entry> </feed>
