![]() |
|
#31
|
|||
|
|||
|
I do not know if the place is right or not but do you have any android packer source code
|
| The Following User Says Thank You to nimaarek For This Useful Post: | ||
Indigo (07-19-2019) | ||
|
#32
|
|||
|
|||
|
Quote:
Code:
https://github.com/woxihuannisja/Bangcle https://sourceforge.net/p/proguard/code/ci/default/tree/ |
| The Following 4 Users Say Thank You to CryptXor For This Useful Post: | ||
Gladiyator (06-28-2019), Indigo (07-19-2019), niculaita (06-23-2019), nimaarek (08-20-2019) | ||
|
#33
|
||||
|
||||
|
Quote:
Code:
https://github.com/ZSShen/AppChameleon |
| The Following User Says Thank You to Mahmoudnia For This Useful Post: | ||
nimaarek (04-08-2020) | ||
|
#34
|
|||
|
|||
|
Recently, I have a topic on how to defeat API hook.
Some protector can work as I want. So, I gona to read these open source protectors code. |
|
#35
|
||||
|
||||
|
YZPACK was open source.
|
|
#36
|
||||
|
||||
|
YZPack 1.1 by UsAr
YZPack - Simple OpenSource PE Packer writen on MASM32 based on LZMA compression method (library from packman) |
| The Following User Says Thank You to dj-siba For This Useful Post: | ||
Mahmoudnia (04-24-2021) | ||
|
#37
|
||||
|
||||
|
Quote:
— bedrock |
|
#38
|
|||
|
|||
|
Quote:
https://www.upload.ee/files/18221202/bambam_v.0.04.rar.html |
| The Following 3 Users Say Thank You to wx69wx2023 For This Useful Post: | ||
|
#39
|
|||
|
|||
|
ExeSax 0.9.1 - C++
Code:
-- WHAT IS EXESAX? Key features: * Small decryption code (usually 50-200 bytes) * Random encryption algorithm and decryptor code * Decryptor can be put in a "cave" or a new section * Pure X86 assembly language - No WinAPI, DLL calls, etc. * Keeps extra data at the end of the EXE * Console and graphical interface ExeSax is an EXE encryptor that has a very small randomly generated decryptor code. The decryptor is so small (50-200 bytes) that it usually can be placed in the padding (or the "cave") after the code section, which means that the file size won't change. If the cave is too small, or absent (which always is the case for UPX compressed files), ExeSax will create a new section and put the decryption code there (this can be a bit buggy, see below). -- NOTES * If you compress your files, do that before you ExeSax them. Most compressors won't compress ExeSax'ed files very well. ExeSax will only increase the file size by at most 552 bytes (and often it won't change it at all) * If your files don't work after encrypting, try compressing them with UPX (or another compressor) BEFORE encrypting them. -- KNOWN ISSUES * 64-bit EXEs are not yet supported * Sometimes ExeSax creates broken EXEs when it has to create a new section (when there's no cave in the file or "Always use new section" is selected) -- CHANGELOG 0.9.1 - 2006-09-18 - Fixed a section alignment bug that (= less broken EXEs) Added icon to GUI exe 0.9.0 - 2006-09-17 - Initial release |
| The Following 3 Users Say Thank You to REPUBLiC For This Useful Post: | ||
|
#40
|
|||
|
|||
|
PolyEnE 0.01 - ASM
Note: This is not the original source code, I have changed some file to make the executable packed file worked with newer versions of Windows Code:
PolyEnE - Polymorphic Encryptor for Executeables (c) 2001 Lennart Hedlund Tested under Win98 & Win2k. http://hem.passagen.se/polyene PolyEnE is able to compress and encrypt most of your programfiles while leaving them in an executeable state. To accomplish this, PolyEnE compress and encrypts most parts of the program and then appends a piece of code that runs when you start the program. This piece of code decrypts, decompresses and fixes some other stuff in memory before it finally jump to the original entrypoint of the program. PolyEnE is free for both commercial and non-commercial use. I am NOT responsible of any damage it causes in your system. It creates a backup, don't remove this before you've tested the program in all environments you would like to use it in. If you see the message "An exception occured while restructurizing resources" or if the "New section size"-progressbar increases faster than "This section", the program is probably already packed and the output may be non-functional. Settings: File to encrypt Hmm, the file to encrypt. Select it by browsing or use drag'n'drop. Randomization seed Chooses seed for the randomization algorithm. You can use a pseudorandom seed, or enter your own between 0 and 2^32-1. Compression Selects windowsize of compressionalgorithm. Bigger windowsize results in better but slower compression. Decompression should not be effected in other ways than a bigger possibility of cache misses. Add junkcode Inserts some code in the loader that doesn't do anything. Used to confuse disassemblers or people tracing your program in a debugger. Scramble loader *Disabled* - To buggy, see bugs-section. A normal loader runs in a linear mode with the following instruction coming directly after the current one. A scrambled loader runs a few instructions and then uses a JMP-instruction to go on with the following instructions at a totally different place in the loader. Used to confuse people. Today there are many compressors/encryptors/"protectors" (let's call them "wrappers") available for PE-files. For most of them, there are also unwrappers available to the public written by and for people that wishes to examine your original file. These unwrappers must get quite much information about the original file by examining the wrapped one. The unwrapper then has to rely on the fact that the wrapper have them stored in the wrapped file and that they have to be used by the wrapper's loader for the inmemory decryption. By knowing where in the loader the data is accessed, the unwrapper can grab them easily. Most wrappers uses a static loader, and because of that the offsets that the unwrapper needs to know are also static. To aviod this, the wrapper needs a dynamic loader, that will look different for every encrypted file. The data that the unwrapper wants should rather be stored as immediate operands than in structured tables. The decryption-algorithms should be polymorphic and should use randomized registers as source and destination parameters. This is harder to make a generic unwrapper for. This is PolyEnE. (The early versions are not so hard to unwrap though.. To come.) So far: Sometime in Started to write on a polymorphic codegenerator for fun. February -01 My military service doesn't leave me much time for it. March - 01 Got an idea to use the (still not ready) codegenerator in an executeable-encryptor. Not much was done due to lack of time. Summer -01 Not really interested in programming. It's summer outside. Wrote on it when it was raining and I had time for it. 5/7 -01 PolyEnE works with most programs under Win9x, but encrypted programs doesn't seem to run under Win2k.. 14/7 -01 Resource-restructuring now supports named resources. Wow. 20/7 -01 Solved importtable-troubles for programs created by some linkers. 03/8 -01 PolyEnE now handles BSS- and TLS-sections without problems (I hope). 29/8 -01 Fixed the biggest Win2k-problem. Some programs won't run under Win2k anyway. 13/9 -01 The processing of the executeable now runs in it's own thread fixing problems of lagging GUI. 15/9 -01 Fixed a problem with programs containing a bound import directory. 10/10 -01 PolyEnE now saves the settings. Commandline-support. Use: polyene.exe |
| The Following User Gave Reputation+1 to REPUBLiC For This Useful Post: | ||
dj-siba (08-24-2026) | ||
![]() |
| Thread Tools | |
| Display Modes | |
|
|