what's the matter babe, you've barely touched your sylveon kombucha
| Blog | https://ruscur.au |
| GitHub | https://github.com/ruscur |
| Bluesky (dead) | https://bsky.app/profile/ruscur.au |
| Twitter (deader) | https://twitter.com/ruscurdotau |
| Blog | https://ruscur.au |
| GitHub | https://github.com/ruscur |
| Bluesky (dead) | https://bsky.app/profile/ruscur.au |
| Twitter (deader) | https://twitter.com/ruscurdotau |
incredibly, this one isn't really my fault! variable length instructions trip up capstone here and it disassembles incorrectly, so I can't match the call instruction.
incorrect on left, correct on right
looking at II first.
my script is looking for the mulss instruction (shown below) after this function call in order to find the address of the battle speed. it's finding a mulss between two registers instead, so I need to figure out why it's gotten lost.
the victim code is present in the DLL, which is good news, it's my script that's wrong and not the DLL that's substantially changed