I've searched this file thought downloading a random mirror of the Citadel leaked package in hope to find it inside.
And since i've downloaded the leaked Citadel package... let's see about the Builder.
It can be interesting to make a post about it.
This file is packed with UPX:
Same for the Citadel Backconnect Server and the Hardware ID generator.
But when we try to unpack it via UPX we have an exception:
UPX told us that there is something wrong with the file header, aquabox used a lame trick.
With an hexadecimal editor we can clearly see that there is a problem with the DOS Header:
We have 0x4D 0x5A ... 00 ... and a size of 0xE8 for the memory.
e_lfanew is null, so let's fix it at 18h by 0x40
Same tricks for the Hardware ID Calculator and the Citadel Backconnect Server, i will get back on these two files later.
Now that we have a clear code we can know the Time/Date Stamp, view the ressources, but more interesting: see how Citadel is protected
Viewing the strings already give us a good insight:
But we don't even really need to waste time trying to know how the generation is made.
Although you can put a breakpoint at the beginning of the calculation procedure (0x4013F2)
At the end, you will be here, this routine will finalise your HID:
From another side, you can also have a look on the Hardware ID Calculator.
I've got a problem with this file, the first layer was a SFX archive:
Malware embedded (stealer):
Conclusion: Don't rush on leaked stuff.
Alright, now that you have extracted/unpacked the good HID Calculator you can open it in olly.
The code is exactly the same as the one you can find on the Citadel Builder, it may help to locate the calculation procedure on the builder although it's really easy to locate it.
That was just a short parentheses, to get back on the builder, after that the generation end you will have multiple occasions to view your HID on the stack like here:
When the Citadel package of Citab got leaked (see this article for more information) an important file was also released:
The HID of the original machine who was running the builder, so you just have to replace your HID by this one, just like this:
And this is how the protection of Citadel become super weak and can generate working malwares
The problem that every crackers was facing on leaked Citadel builders is to find the good HID key.
Citadel builders who was previously leaked wasn't leaked with HID key.
e.g: vortex1772_second - 188.8.131.52
And you can't just 'force' the procedure to generate a bot because the Citadel stub is encrypted inside, that why when the package got leaked with the correct HID, a easy way to crack the builder appeared.
Without having the good HID you can still bruteforce it till you break the key but this is much harder and time wasting, this solution would be also a more great achievement and respected in scene release.
To finish, let's get back on the Citadel backconnect server who was requested on kernelmode.info
This script was also leaked with the Citab package:
It's for Windows box, and it's super secure... oh wait..
Brief, happy new year guys :)