Re:Unfuck: A utility for deobfuscating Python 2.7 bytecode
by landr0id on Friday August 13, 2021 @12:52AM
(#28165591)
I haven't heard of this tool before, but I don't think it would work for obfuscated code. Check out the graph image on my wiki [1]. While this image doesn't show the exact scenario, imagine that the first instruction is a `JUMP_ABSOLUTE 100` and the rest of the instructions between offset [3,100) are just garbage or invalid.
A naive disassembler (like the `dis` module in python) interprets the bytecode linearly -- i.e. one instruction after another. Rizin's diassembler [2] seems to take the same approach. The way I do disassembly is to only disassemble code paths that are potentially executed by queueing non-conditional jumps, both targets of a conditional jump, and the next instruction when the current instruction is non-jumping instruction.
[1] https://github.com/landaire/unfuck/wiki/Obfuscation-Tricks
[2] https://github.com/rizinorg/rizin/blob/e3d1b967854c33cf9dfbb...
Re:Unfuck: A utility for deobfuscating Python 2.7 bytecode
by sharikone on Friday August 13, 2021 @04:03AM
(#28166613)
Rizin is basically the name of a fork of Radare2 disassembler after the community had particularly nasty "value" disagreements.
Re:Unfuck: A utility for deobfuscating Python 2.7 bytecode
by xvilka on Friday August 13, 2021 @06:00AM
(#28167189)
We have diverged quite a lot already, it's not a simple rename etc. See https://news.ycombinator.com/item?id=27830230
[1] https://rizin.re
[2] https://github.com/rizinorg/rizin