![]() |
|
Change strings on EXE file - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45) +--- Forum: Blackhat • Red Team • Offensive Security (https://hackforums.net/forumdisplay.php?fid=447) +---- Forum: Blackhat Training (https://hackforums.net/forumdisplay.php?fid=405) +----- Forum: Reverse Engineering (https://hackforums.net/forumdisplay.php?fid=229) +----- Thread: Change strings on EXE file (/showthread.php?tid=6274748) |
Change strings on EXE file - Arnau97 - Jul 4, 2024 Hello, I recently downloaded some exe files, and the console title is for example "hello123". If I want to change it to "wawa123", how could I do it? I tried IDA freeware but I can't figure out how to use it. Thanks RE: Change strings on EXE file - terrestrial - Jul 28, 2024 Open it in something like DNSPY and if its not obfuscated search "hello123" and edit it through that software. RE: Change strings on EXE file - notagh0st - Jul 28, 2024 In IDA, open the binary, use the Strings window to find the string you're looking for, then go to that string in Hex view, right click, edit, change the values, right click, apply changes, then File -> Produce File -> Create EXE File. If you don't want to bother with IDA, download any hex editor, like 010 Editor, VS Code with the Hex Edit plugin, etc. etc. find the string, edit inline, save. RE: Change strings on EXE file - inputoutputcontrol - Oct 1, 2024 Hex editor /charsssss RE: Change strings on EXE file - SovietBastard - Oct 2, 2024 (Jul 4, 2024 04:19 AM)Arnau97 Wrote: Hello, doesn't sound like a very useful task, isn't it? btw... you can also use gdb for that which is lighter, in gdb, type "info proc map", you will see mem-info, try to find your string within those addresses, for eg: ``find 0x400000, 0x403000, "urmother"``, tis will give you the mem-address of the string if found, then use that address to change it like: ``set {char[n]} 0x402111 = "new value"``, n is the number of bytes to write, then you can ``continue`` gdb execution. |