-
Notifications
You must be signed in to change notification settings - Fork 48
Home
Welcome to the UnamBinder wiki!
Here I will write explanations for all the features and give examples on how to use them. I will also strive to answer the most frequently asked questions so that there is fast and easy access to information otherwise usually gained by experience.
I will write everything on a single page instead of multiple pages for a more portable navigation experience. As always you can utilize tools such as CTRL+F or the sidebar navigation menu to quickly try and find the information you're looking for.
| Navigation Menu |
|---|
|
Downloader Features |
|
FAQ |
This is where all the files it will bind and execute (if chosen to do so) are listed. You can add new ones, edit the ones already there or remove them as well.
Here you can select to either build the miner as a 32-bit native assembly written in C, or to build the miner as a managed assembly written in C#. If you build it as a native assembly and want to decrease detections then you should use a crypter, if you want to decrease the detections for a managed assembly then use an obfuscator.
Will display a fake error with the text that you enter when the file is started. You can also select the message box type, meaning what icon and style it will have.
Will pause the file for the amount of seconds chosen before dropping and executing the bound files, can bypass Windows Defender sandboxing among others.
Whether the program should be compiled to be run with administrator privileges, this is required for the "Add Windows Defender exclusions" option.
Will add exclusions to the following locations: %UserProfile% and %SystemRoot% before any files are downloaded. This means that if this option is enabled then any files dropped should not be detected by Windows Defender.
The filename that the file will be dropped with, should include the extension the file should have, like .exe, .txt, .jpg or whatever type of file it is.
The path to the file that it should bind.
The location it should drop the file in.
Whether it should execute the dropped file after it's been dropped to it's location.
These options can be used when building the file as a managed file. These are pretty self explanatory and won't require much explanation, the "Icon" option is the icon that the file will have and the "Assembly" option is the assembly information that will be used by Windows when displaying the program in different places and can also be seen when right-clicking the file and checking its properties.
If you're building it as a native assembly then you should be able to use any crypter, or if you're building it as a managed assembly then you should use an obfuscator. If you have experience with C or C# then you can also change the around the Program.c or Program.cs file respectively to reduce detections.