<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://cakeslayers.github.io/</id><title>CakeSlayers</title><subtitle></subtitle> <updated>2023-06-18T14:44:07+08:00</updated> <author> <name>CakeSlayers</name> <uri>https://cakeslayers.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://cakeslayers.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://cakeslayers.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.3.2">Jekyll</generator> <rights> © 2023 CakeSlayers </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Defeating Epsilon Loader V0.34 Vol. 3: Packet Encryption</title><link href="https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-3/" rel="alternate" type="text/html" title="Defeating Epsilon Loader V0.34 Vol. 3: Packet Encryption" /><published>2023-06-13T00:00:00+08:00</published> <updated>2023-06-18T14:33:12+08:00</updated> <id>https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-3/</id> <content src="https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-3/" /> <author> <name>CakeSlayers</name> </author> <summary> Disclaimer The following pseudocode snippets are heavily beautified. You may not be able to instantly recognize some of these parts; lots of junk code and algorithms are unrolled. But that doesn’t really matter, as when you finish reading this article, you will have a field day breaking it (= Intro As we’ve already known, epsilon loader implemented some sorts of encryption on network packets... </summary> </entry> <entry><title>Defeating Epsilon Loader V0.34 Vol. 2: JNI Protection</title><link href="https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-2/" rel="alternate" type="text/html" title="Defeating Epsilon Loader V0.34 Vol. 2: JNI Protection" /><published>2022-03-19T00:00:00+08:00</published> <updated>2023-06-18T14:33:12+08:00</updated> <id>https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-2/</id> <content src="https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-2/" /> <author> <name>CakeSlayers</name> </author> <summary> Disclaimer The following pseudocode snippets are heavily beautified. You may not be able to instantly recognize some of these parts; lots of junk code and algorithms are unrolled. But that doesn’t really matter, as when you finish reading about this kind of protection, you will have a field day breaking it (= Intro In the last article we deobfuscated the Indys and reveal the “real invocation... </summary> </entry> <entry><title>Defeating Epsilon Loader V0.34 Vol. 1: InvokeDynamic</title><link href="https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-1/" rel="alternate" type="text/html" title="Defeating Epsilon Loader V0.34 Vol. 1: InvokeDynamic" /><published>2022-02-28T00:00:00+08:00</published> <updated>2023-06-18T14:33:12+08:00</updated> <id>https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-1/</id> <content src="https://cakeslayers.github.io/posts/Defeating-Epsilon-Loader-V0.34-Vol-1/" /> <author> <name>CakeSlayers</name> </author> <summary> Epsilon Loader V0.34 had been considered as “STRONG obfuscated” as well as “uncrackable” by the 2B2T community for a long time. It was also widely believed that the authentication and verification part of Epsilon is achieved in the DLL1. So let’s look inside the DLL and the related JVM classes to determine what role the DLL plays and find out the way to exploit it. Initial analysis of the DL... </summary> </entry> </feed>
