TheKrimlin wrote:Now to the point, I have basic knowledge and usage of windows batch files for basic admin stuff to make my job easy.
TheKrimlin wrote:My instructor in my intro to info sec class told us that batch files don't have the flexibility of other scripts when it comes to viruses
TheKrimlin wrote:furthermore ... that batch files can never be logic bombs.
TheKrimlin wrote:My mission is to create a kickass virus in batch file format and drop it on our demo computer to get my point across. Now I've got 2 weeks to do this and I want to get it done so I can shoot for honors credit for the course.
TheKrimlin wrote:My idea is to write a batch file that takes data like log files (or some other kind of computer generated reports that build up rather quick) store these in a place to overload the ram causing a crash. The kicker is I want it to also take the crash dump files and store them back on ram after recovery to keep the process in a constant crash loop.
TheKrimlin wrote:My questions are:
Is this even possible?
TheKrimlin wrote:What kinda delivery methods are available for batch files?
TheKrimlin wrote:How to get them in there stealthy and where to store them?
TheKrimlin wrote:How to make a batch file auto exec at a certain point?
centip3de wrote:Wait, so, you guys don't use Linux? That's odd. Most servers run Linux and beyond that, most information security classes use Linux. Although I suppose it's possible to use Windows for both, it's just fairly rare.
centip3de wrote:Eh? Batch is a pretty shitty language, it's just odd to hear them compared in terms of virii making.
centip3de wrote:Once again, eh? If you're defining a logic bomb by the Wikipedia definition, then your professor would be right, unless of course your making software out in Batch (then you'd have to define what 'software' is, and it gets all kinds of meta).
centip3de wrote:Something tells me that you won't be getting more credit for destroying a computer...
centip3de wrote:Uh, why not just write a fork bomb that puts itself in the startup folder? Seems much simpler. If you still want to keep the fork bomb aspect of it (i.e. it goes off when someone launches a program/deletes a file, etc.), then why not just monitor a certain file and then launch the fork bomb if it changes?
centip3de wrote:Well seeing as batch is turing complete, technically anything is possible... but practically, yes, it should be.
centip3de wrote:What kind of delivery methods are available? Do you mean, how to get a batch file onto a system? In theory, it's the same way you'd get any other virii onto a persons computer, with the added benefit that an AV most likely won't pick you up.
centip3de wrote:If you have physical access, why not just a USB? As to where to store them, you could always just make a massive folder tree, or just store it in a usually inconspicuous place like in the files for a random program.
centip3de wrote:Depends on what you want to do. If you just want to check for changes in/on something, you can setup a simple conditional in the batch file and then put it in the task scheduler to run every 30 seconds or so.
Goatboy wrote:In addition to what centip3de said (99% of which I agree with), it seems like you're biting off more than you can chew. You've got some misused terminology going on and I think the cause of that is some serious misunderstanding. RAM doesn't really get expended by having a lot of files on the disk; you'd have to open them all at once and that's about as inelegant as it gets. You are also not only not going to get points for this, but if your school is like many of the others you will get in trouble. Even if it is a demo computer.<br><br>My suggestion? Read some papers about actual virii in C and ASM. Batch is simply not the tool for the job here.
cmd /k mystupidbatchfile.bat
Users browsing this forum: No registered users and 0 guests