malboxes
malboxes copied to clipboard
GoSecure
Builds malware analysis Windows VMs so that you don't have to.
Admin credentials should be stored in the Vagrantfile that is packaged in the box. I don't see a security issue doing so and I see a usability issue not doing...
Was made aware of this tool that can disable defender on recent Windows versions: https://github.com/APTortellini/unDefender
Tracking bug - [x] x64dbg (saneki/chocolatey-packages/issues/1) - [ ] ollydbg2 - [x] npcap (#2) - [ ] [cutter](https://github.com/radareorg/cutter) - [ ] malboxes itself
I had to have a windows 32 bit VM so I went for the win7_x86_analyst profile but SP1 is not installed. Automatic updates are turned off and that seems reasonable...
These are additions to malboxes to support KVM. I have added the KVM builder and changed win10_x64_analyst.json and win10_x86_analyst.json. I've made a config.js which specifies KVM to test the profile....
After seeing recent [performance discrepancies](https://openbenchmarking.org/embed.php?i=1812203-PTS-VIRTUALI66&sha=473274f&p=2) between kvm and virtualbox, I'm tempted to give another shot at kvm support. I know that @ProloG-Shaman has done a PoC of it. I wonder...
I personally had a use case for installing python and pip packages. I thought it would be cool to do that automatically like `choco_packages` but `python_packages`. Modifications would be like:...
While spinning up a `win10_1607_x64_analyst` I saw that x64dbg was not installed. While looking at the logs, I found this: ``` virtualbox-iso: Progress: Downloading x64dbg.portable 20190901.1737... 100% virtualbox-iso: virtualbox-iso: x64dbg.portable...
Some old programs versions can be found [here](http://www.oldversion.com/) if someone needs them to test old exploits for instance.
Did some tests yesterday for a multi-machine setup with the `Vagrantfile` built by the spin command. There are some challenges around the networking setup since Vagrant insists on being on...