I have a bit more time for this useless thread now, I'm going to explain you what you looked at since you don't even understand the simplest language.
Evilcheats.io is owned and operated by Invictus-Load.in which is operated by the company behind all of that. ACUS isn't a ruski name, I'm sorry that I have to destroy your picture of me but I'm sadly not a Russian.
First of all, I have to admit that our client (loader) isn't a RAT. You saying it like I'm sitting on my PC and checking for new connections on the API server with a list of files where I have to click upload. That's very far away from what our client (loader) is actually doing, besides that my time is worth more than sitting there and checking every new connection to our API server. We have a pretty basic hash check, the client (loader) did never upload a file, all it does upload is parts of files and hashes. If a hash is considered suspicious, the data will be saved for manual review.
If the client (loader) would take an hour to open no one would use our cheat/client (loader).
We communicated very openly that we changed our name from Invictus-Load to Evilcheats, we had other reasons for that change. I already explained why the client (loader) uses Invictus-Load.in to connect with us, not because we forgot about it, it's because we wanted it to be the global API for everything.
You had a look at our client (loader), did you ever deobfuscate a .NET assembly? Putting it into some public tool to switch unicode chars with smaller random classnames does not generate a cleaned .NET assembly. The file you decided to put online and declare as a cleaned version is a good example of your knowledge, it's drag and drop of the file into a public tool. Congrats!
Not saying that it is not enough, but you saying it like it is something special. Creating a very good obfuscation for managed code?
I will stay with not trusting the client and validating everything serverside, that does not need good obfuscation, it needs good development skills and understanding of how everything works.
"pretty much no u cant get the cheat it will import it when u try inject or some shit like that."
I'm sure that our client (loader) is very good when it comes to network encryption and communication between the managed code and our native dll`s. But ofc, you didn't say anything about that since you have no clue about anything you looked at, using a 3rd party program for deobfuscation isn't the problem, the problem is that you think that you have knowledge about stuff you didn't even work with. Since you only posted our "cleaned" client (loader) your knowledge doesn't seem to be good enough to get a devirtualized and cleaned version of you API_x64.dll, which actually should be more in your interest since it's native code and who would code a RAT (which you are trying to proof here) in managed code?
If you are actually the guy who wrote to me in Discord then you should know that we inform users about it.
"i want to see if the cheat also steals shit."
It's hard to crack stuff when you have no instruction for it. gl..
. it got exposed for being a rat since you would use the loader and it scanned so much shit u would site there for a hour while he took shit and uploaded it to his server. 
