A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.

New answers tagged


Just a brief analyze of data samples you provided. First: 7b0fc4f83d3fc320ef3865a1b472caeba3f0b60e09f257c61f34af77a7ff57adTB5QO8kXU18KUIgZGXblGYAOC7qbRzizHLGpGdUPbywggHncAkwJVe4M/0w7Dy9svucGrEgYbud0OY5iCFlTalho9j9SWzGMXlWjqU0wrFApBh+/Rqy8v93q1gBlpwLsuj7WBppuWItBmhoOyxkyKLv8Vm6AVVeXxndd4kklq+E= Second: ...


try: printf '\x31\x09\x32' | xargs python script.py


You cannot simply make pyinstaller gui.py. You should resolve all dependencies: or installing packages using pip, or pulling them from extracted PYZ archive folder. In the PYZ folder you can find all files, but you need to rename it and rearrange to modules.


You can extract some file from .exe using pyi-archive_viewer, modify them and put back. But be attention, all files in .exe are compressed using DEFLATE (zlib.compress() - you can watch this in source code of PyInstaller). So, when putting back you need compress file to the exact size, that was when you extracted it.


I did something similar on the past, here is the idea you need to carry: You create the python script that you want to execute and obfuscate: print('Some string') Another script opens the previous script, encrypts the content and base64 the encryption, and finally put in a variable like: text = "cHJpbnQoJ1NvbWUgc3RyaW5nJyk=" On another python file, you ...


The solution that I found is: analyze(currentProgram) Just after the disassembly.

Top 50 recent answers are included