[IMG]http://i41.[censored].com/a5cec3.png[/IMG]
Pretty simple code explaining how everything is done. The builder is fully commented so you should be able to understand how to create your own builder and stub. Added a couple of tips as well. Basically just loads words from the builder, but you can do a lot more.
[dl]http://#.com/files/251510232/VaqxBuilderEx.rar[/dl]
Credits to JapaBrz for helping me with my builder.
Enjoy.
many thank's(too short.....)
excellent. Ive been meaning to make a builder
Romeo, try using If Else, if it uses the words then continue, if it doesn't then exit.
It is very hard to find builders in VB 2008, so
this is very good for the learners! =)
ok, ive gone through this and made my own working builder
I'm still confused at how this whole process works, and the role that the stub and the filesplit play
do you have any other resources on this?
No, I don't. Sorry.
Basically, the builder reads the stub, writes your data in, and then creates the output file.
It's simple if you look at it enough :D
(Jul 3, 2009 03:00 PM)Vaqxine Wrote: No, I don't. Sorry.
Basically, the builder reads the stub, writes your data in, and then creates the output file.
It's simple if you look at it enough :D
alright. Ive taken a little bit more of a look
I thought at first the stub had to be a quasi-copy of the builder
then, I experimented changing the GUI, and also removing this code from the stub
Code ' FileOpen(1, Application.ExecutablePath, OpenMode.Binary, OpenAccess.Read, OpenShare.Shared)
' yourfile = Space(LOF(1))
' FileGet(1, yourfile)
' FileClose(1)
' word1 = Split(yourfile, FileSplit)(1)
' word2 = Split(yourfile, FileSplit)(2)
So, the stub could really be anything, then, right? and the builder just re-creates the stub replacing the variables word1 and word2
meaning one builder could act as a template for other programs
or am I wrong
You need the stub for it to work. And I'm not sure what you mean, but I guess the stub could be anything...?
(Jul 3, 2009 03:14 PM)Vaqxine Wrote: You need the stub for it to work. And I'm not sure what you mean, but I guess the stub could be anything...?
im going to try turn the stub into a phishing program to test what i meant. Ill get back to you
Okay.
Just dumping my sources.
Very nice, Will look over the source.
(Jul 3, 2009 03:09 PM)MC Wrote: alright. Ive taken a little bit more of a look
I thought at first the stub had to be a quasi-copy of the builder
then, I experimented changing the GUI, and also removing this code from the stub
Code ' FileOpen(1, Application.ExecutablePath, OpenMode.Binary, OpenAccess.Read, OpenShare.Shared)
' yourfile = Space(LOF(1))
' FileGet(1, yourfile)
' FileClose(1)
' word1 = Split(yourfile, FileSplit)(1)
' word2 = Split(yourfile, FileSplit)(2)
So, the stub could really be anything, then, right? and the builder just re-creates the stub replacing the variables word1 and word2
meaning one builder could act as a template for other programs
or am I wrong
you cant remove this code, otherwise it wont get the code written on the exe.
this is the only piece of code that must be unchanged, the rest you can change as you want
It's also a good idea to use the stub as a resource then drop it when you need it, if you know how to do that.
It saves there being two files and it makes it harder to be analyzed/scanned.
YAY!!! I SOOO NEED THIS :)
|
