Thats right appending 0's to EOF(End OF File) does nothing, but it does change the hash value of the total file, NOOB made "ByteCipher" after I suggested this would change the crc value when some random bytes are added to EOF, while this is a good quick an easy method, the propper way to do is add random bytes in the code section of of the dll, then recalculate the crc value and write that to the header section which overwrite the original crc value. because when the dll gets loaded into memory it will not load your random byte EOF, these are ignored as they don't belong to any section of module(dll). SO if Nexon ever scanned memory for hash value this would not work, if you actually wrote the random byte to a code section it would work in memory also, lucky for now nexon only scan the dll on disk and hash that to there banned list, hence why the byte at EOF file works(for now)
Originally Posted by luistupapixD
