pyinstxtractor VS pyinstaller-hooks-contrib

I have used pyinstxtractor to extract the *.pyc files, and then the uncomplyle6 to decompile the *.pyc files. Which has led me to the actual source code of the binary:

Also, be real, you mention you use it once in the credits at the bottom of your readme while also advertising your mate's tool that ALSO looks like it uses identical code to the original, this time without even mentioning it. And given he also makes CS:GO cheat tools by the looks of it, I struggle to understand why any of you think you have the moral high ground in any of this...

It's a Pyinstaller binary.(I have used it once before, so I just knew it by checking the file.) Use https://github.com/extremecoders-re/pyinstxtractor to extract its source code archive in binary (by just running python pyinstxtractor.py ./backdoor or something), now many .pyc files are extracted. Find src.pyc and it's malformed as Python3.9, so https://github.com/rocky/python-uncompyle6/ denies to decompile. But challenge information says it's Python3.8, so I write helloworld python script and execute it with Python3.8. It yields Python3.8 .pyc file. Analyze it and find signature is \x55. Change src.pyc's signature from \x61 to \x55 and decompile by running uncompyle6 backdoor-src.38.pyc > backdoor-src.py

If it's a pyinstaller blob, you can crack it open with tools like https://github.com/extremecoders-re/pyinstxtractor

auto-py-to-exe is a GUI interface for PyInstaller (a famous freezer packager for python projects). While very user friendly, it should be noted that the .exe made using PyInstaller (or auto-py-to-exe) is very easy to reverse engineer (https://github.com/extremecoders-re/pyinstxtractor).

which boils down to slapping the Python Interpreter + the code in an executable form it is trivially easy to access the code inside such executables: https://github.com/extremecoders-re/pyinstxtractor

I understand that at one point there was a problem with pyinstaller and it's importing of openCV but from what I read it sounds as if it had been solved? https://github.com/pyinstaller/pyinstaller-hooks-contrib/pull/469

pyinstaller has the ability to "hook" how it handles different packages that require special handling like boto3. Which sounds like a lot of work, but it should just work, since it comes with a hook for boto3 and friends.

I haven't checked the pyinstaller hooks in a while but if they aren't working for cv2 you'll need to pass in the compiled cv2 module to Pyinstaller with the --paths flag when building.