CAFlames (03-12-2011),NOOBJr (03-20-2011),NotRealPro (06-23-2012),Sydney (03-12-2011)
Blue Mist ( Blue File Format )
Let me start by explaining what the blue file is.
The Blue file is a File Format created by @topblast for hacking proposes, in the creation of this file some information of the Hack / Creator can be stored in the file. This information is Compresses and Encrypted to protect it from unauthorized people and also Hex Editing. The Blue file when used correctly can be opened by double clicking which starts a loader / injector (blue capable) adding it to the list of hacks to be injected. As a result of this less work is needed on those who do not know how to operate an injector / new comers AKA noobs. The Blue File is not yet completed is still in beta form. This release contains Blue Mist 1.2 SDK. I am thinking of adding a Process control to the blue mist so that you hack can only be injected to a certain Process / Processes Should i add it?
- Simple Inject
- Allows for the injections of all stored files in the hack list
- Close on inject
- Custom Process list
- Blue Mist SDK 1.2
- MAJOR CHANGES TO THE BLUE CLASS
- Injector Class (Not going to say the functions
- Allows injection for 64Bit
- Injection for Blue / Dlls
- Logs its work
- Message Samle.blue
- Message Box DLL i made
- When Injected it Shows a MessageBox and Close
- Converted into Blue File
- Convertor
- Converts any file into a blue file
- Allows for use with Blue Mist Injector (not the releases one :P)
Last edited by topblast; 03-12-2011 at 07:20 AM.
I just like programming, that is all.
Current Stuff:
- GPU Programmer (Cuda)
- Client/Server (Cloud Server)
- Mobile App Development
CAFlames (03-12-2011),NOOBJr (03-20-2011),NotRealPro (06-23-2012),Sydney (03-12-2011)
Can you explain more about the Blue file format, What are the benefits? what is the difference? does it only show creator? is "Name" the name of the file or is that part of the blue mist format which would show the name of the hack which doesn't depend on file name? Explain on developers side what they need to do and know about this format.
Would i be incorrect in saying its a compression of dll's which stores "Strings" in either resource or EOF?
Last edited by Departure; 03-12-2011 at 07:27 AM.
Benefits, as i said are
- Encrypted file Helps protect From Hex Editing
- Starting of injectors from the Blue It Self
- Thats all i can come up with off the bat but the file is not complete()
Creator is information stored in the File, So what ever the injector does with it is up to the injectors creator/ any application using the blue mist SDK.
The NAME of the blue file can be anything, what i mean is that it is stored within the blue file and doesn't depend on the file name but if using an injector like the one i provided which only injects blue files, it converts the dll into a blue file automatically as a result of that it is forced to use the FILE name.
WOW.. really if you want to learn about the Blue mist SDK you might have to talk to me for what you do not understand from the blue class.
In storing the DLLs with in the Blue mist it is converted into a byte array, The Value of each byte in that array is used within a single string. This part is still being developed the most because this is the reason the blue file is larger than the normal file. The reason it is better because say those bytes value are you should know is only 1 byte, but the value of a single char is also 1 byte so if the value is 75 that is 2 bytes in the string blue the splitter with will be 3 bytes. The max about of bytes is 4 and the min is 2 bytes in string to 1 byte in the array. I am doing my best to Reduce the size of the blue file.
I just like programming, that is all.
Current Stuff:
- GPU Programmer (Cuda)
- Client/Server (Cloud Server)
- Mobile App Development
While I haven't downloaded the mist SDK or the injector ect.. I just wanted to understand exactly what your doing, Do you know about image headers and sections? dll headers are pretty much the same as PE headers only real difference is the entry point. SO knowing this you can use this to your advantage, add new section to dll write your stub code to decrypt the original code section and then jump to original code section to execute or save it as decrypted, changing the entry point in the header to start from your decryption then when decrypted change header entry point to start at original entry point before encrypting.
This is basically how crypters work, but if you want to keep it simple I suggest just write your strings to eof or resources with decryption/encryption done by the injector. also you can use compressing this way and still read eof strings which means you dont need to decompress to read your setting or other information you may have appended, This will actually reduce the original file size down
D-Vid the DBag (03-14-2011)
nice looks epic as long as its blue file not blue waffle
| Buy Premium MC accounts CHEAP Click here |
Respected seller.
Check my vouches in the first post of the above MC account thread ^
??? ok
I am still updating this .
I just like programming, that is all.
Current Stuff:
- GPU Programmer (Cuda)
- Client/Server (Cloud Server)
- Mobile App Development