EvilZone

So I have a few questions, first is how is this different than ophcracks rainbow tables? If we are brute forcing a password, don't we also need a dictionary file?

You mentioned walking in with a USB and doing this. Time and the machine that you are working with really matters. If you only have a few minutes, and the target machine is a 2.0 GHz dual core, then simply extracting the SAM file and cracking it offsite with a gpu based tool like oclhashcat may be faster and safer. Yet still, maybe just walking out with the entire damn machine would be easier. Hell if I'm already physically on the network, then there are so many other possibilites other than sitting there and toiling away brute forcing some password.

This also seems like an aweful lot of work for just one password. Maybe it would be easier to walk in with a malicious USB that spawns a shell to your box, then keylog. We could get really creative and buy a fancy keyboard, modify it with a trojan, and mail it to the IT department.

As far as Windows security goes, Windows 10 has new security methods that make it more difficult to pull the passwords out of memory with tools like mimikatz. Here are the links to the limited amount of research that I have done.

Talks about the security methods:
https://adsecurity.org/?p=1535

Talks about a potential for a remote exploit:
https://www.blackhat.com/docs/us-15/materials/us-15-Brossard-SMBv2-Sharing-More-Than-Just-Your-Files-wp.pdf

Hey JustSomeBrHUE.

Since this is a somewhat important project for school, you should get the terminology right first. Only then we will know that we actually talk about the same things.

(actually, I'm trying an worm)

A worm is a malware that spreads on its own via the network, often by using exploits or sending itself via email. This is not trivial to write and not so good to demonstrate to others. Furthermore, the risk of actually infecting and damaging the network is too high. Morris tried that too (creating a harmless worm) and it ended in a disaster, see https://en.wikipedia.org/wiki/Morris_worm
I strongly advise you against the creation of a worm.

A malware is only called virus if it infects other files. That means it will search for a host file and append, prepend or replace the host file's code with its own code (see file infection strategies in the image below). The resulting infected file is also infectious. The behaviour of host infection is similar to parasites in nature, which is why we call this kind of malware "parasitic". A virus makes sure to be executed again by infecting host files that are opened by the system or the user. E.g. the user opens the infected notepad.exe and the virus code will be executed this way. This is one way to get persistence.



But there are a lot of ways to gain persistence. The most usual ones by non-parasitic malware are the startup folder of Windows (everything in it will be run after login) and autorun entries in the registry. The most commonly used autorun entries are:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce

You can use regedit.exe or autoruns.exe to check these entries on your system and see how it looks like for programmes that use them. There are some of these entries on every system.

Anyways, what you need clear up is: What malware type shall it actually be: virus, worm, trojan, backdoor, ...?

Please note that creating an effective virus with powershell and batch is not possible. To be effective, it would have to infect host files that are often executed on the system and these are usually EXE and DLL files. You cannot put a batch script in those. Viruses are often written in C or assembly.
But maybe you don't need it to be effective. Afterall, it is a school project, and minimizing the risk of misusing your code would be a good thing to do. E.g. if you create a powershell virus that infects powershell source files, it would not be effective and the chance of misuse is very low, but it is enough to demonstrate how it works.

I want a "pacific" virus, so it can't be harmful or cause any damage to the computer or files

A virus is always harmful. A virus modifies host files so that these host files become infectious themselves. This is considered damage, even if the payload doesn't do anything.
The same is true for a worm. It will spread to other machines without asking their owners. This is in itself harmful, even if you don't cause such problems as Morris did with his worm.

Do you have any questions?

I've had an idea a while ago, but never researched about it
So basically you could "infect" every single shortcut found on the desktop etc, so that when the users clicks on it, it starts the worm along with the selected software. I guess it could be made by adding the path to the worm in the shortcut or something along those lines.
Of course it wouldn't work if the users opens his program by another way (eg searching the program's name in the research bar in windows etc)

Before starting to think about hacking something like gmail you have to know your limitations. Bruteforcing or attacking server side login system via bruteforce by its known to be stupid idea.. Why? Since everyone since year 1990 knows that site's block/ban ip's and accounts on which more then 5 wrong attempts have been made. So you ask me how? One way is by spreading keyloger on user computer. But of course here you will face with a problem of proper distribution or malware detection.
There are alwasy ways to bypass improper login system without actually need of using correct password.... like with SQL injection, XSS,, and so.. on..

Bruteforcing now days is more or less done on client side attack.... not server side. That is the reason why i think your source code is of no use...


bye N

Hello:

[Problem]
I'm learning a lot the last time but it's getting too much to remember all the commands. I made a how to for myself for the install of arch and configuring, but for the commands of for eg airmon or iw i would like to create a cheat sheet.

[Background]
I've learned many commands but have it heard to remember.

[Things I have tried]
Install cribr in Arch with wine. Was no success. Installed cribr in Windows, doesn't look good.

I've been looking for alternatives but I don't trust all the online options (some of them force you to publish your cheat sheet).

Latex is named as an option on several internet website, but it seems to have a steep learning curve. As I'm now finally learning other things, I would like to learn Latex as a last thing.

[Where I am stuck]

How do you guys remember all those different commands? I know man exists but knowing the commands is much faster.

What or how do you guys keep track off all your know commands?

I'm not talking about installing or configuring things, I have a how to for this, but about the commands like iw, airmon, knowing you should change /etc/resolv.conf for NS, etc..

I don't have a problem with sharing my finally created cheat sheet, but as I'm very beginning I don't know you could use it