<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>strings - Tag - The handbag of Cryptax</title><link>https://cryptax.github.io/tags/strings/</link><description>strings - Tag - The handbag of Cryptax</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>crypto.maniak@gmail.com (Cryptax)</managingEditor><webMaster>crypto.maniak@gmail.com (Cryptax)</webMaster><lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cryptax.github.io/tags/strings/" rel="self" type="application/rss+xml"/><item><title>Linux/GoGra Payload Analysis</title><link>https://cryptax.github.io/posts/gogra_payload/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><author>cryptax</author><guid>https://cryptax.github.io/posts/gogra_payload/</guid><description>GoGra Linux Payload analysis This blog post continues our analysis of GoGra Linux variant. In a first part, we analyzed the Dropper and found out it was displaying a decoy PDF and executing another binary. In this second part, we analyze the other binary, also called payload or implant.
Pclntab The implant is stripped, so at first, Ghidra sees no function names, filenames etc.
Note that, at first, our LLM did not know at all how to deal with Go binaries.</description></item></channel></rss>