Killer update

Posts 1–15 of 24 · Page 1 of 2
Killer update
As some of you may know, deca just released somewhat of a hacker killer update.

This update obfuscateds client code making it undreadable.

They changed quite a bit of parameters because so far i've updated packets of my bots and it still fails to connect.

This means that RC4 keys or something are different.

I tried to look and debug to find out RC4 keys in order to make proxy and bots work again, but failed so far, because the place which provides those keys looks like this:
 
encryptConnection()
Code:
private function encryptConnection() : void
      {
         if(!_loc4_)
         {
            if(!§each continue§.§implements set package§)
            {
            }
            addr138:
            return;
         }
         §§push(§_-FN§);
         §§push("rc4");
         §§push(§_-MU§);
         §§push(§_a_-_---§);
         §§push(-1556816037);
         if(_loc3_)
         {
            §§push(§§pop() * 109 - 52 + 31);
         }
         §§push(§§pop().§_a_--_--§(§§pop()));
         §§push(0);
         if(_loc4_)
         {
            §§push((-(§§pop() * 89 + 1 - 11) + 90) * 49);
         }
         if(_loc4_)
         {
            addr58:
            while(true)
            {
               serverConnection.§_-fD§(_loc1_);
               if(!_loc3_)
               {
                  if(!_loc4_)
                  {
                  }
                  addr124:
                  serverConnection.§in implements§(_loc2_);
                  break;
               }
               break;
            }
            if(!_loc3_)
            {
            }
            §§goto(addr138);
         }
         while(true)
         {
            §§push(§_-FN§);
            §§push("rc4");
            §§push(§_-MU§);
            §§push(§_a_-_---§);
            §§push(-1556816037);
            if(_loc3_)
            {
               §§push(-(§§pop() - 1 + 108 + 1 - 1) + 1 + 1);
            }
            §§push(§§pop().§_a_--_--§(§§pop()));
            §§push(26);
            if(_loc4_)
            {
               §§push(((§§pop() - 71) * 13 + 64 - 12 - 1) * 56);
            }
            if(!_loc4_)
            {
               if(!_loc4_)
               {
                  §§goto(addr58);
               }
               §§goto(addr124);
            }
            §§goto(addr127);
         }
      }


Ofcourse its only speculation if rc4 keys changed. Maybe packet structure too.

RealmEye bots are offline for this reason too.

What do you guys think about this and how do you feel we should tackle this problem?
Discuss it here and post findings.
I think guys from RealmBot can update code, they use same method to guard Orape.
Quote Originally Posted by snadjnsanfdjanfjadfjancfd View Post
can somebody send me the new client after some genius updates the codes
Just check up on the RotMG releases page once a day or something. We're not going to go out of our way to message you the client for something you can just check yourself.
with no client im not playing
Possible end of Rotmg hack client
So, no more hacks??
Don't worry, it is just a bump in the road. It will delay hacks, that is it. They will come back out when developers finish them.
Yea Realmbot claims to have already updated their orape/krelay client on their website/cord but haven't had time to test out. At work currently so if someone wants to check it out and report back......
About time Deca steps up.
60% of realm hacks

you're doing a disservice to those who support your stupid updates anyway
just wait a few days, stop complaining it doesnt help
Seems I stepped in at an interesting time.
Posts 1–15 of 24 · Page 1 of 2

Post a Reply

Similar Threads

Tags for this Thread

None

Need help?