Hi There. I am new to the world of scam baiting… and I realize there are a few things you need. FireRTC and a good VM. Now, I plan to do all my scam baiting on a mac… and run my VM on Virtual Box, But I need help with the setup… Can I get some help pls?
https://www.youtube.com/watch?v=rNV5JmxtKP4 https://www.youtube.com/watch?v=lEvM-No4eQo https://www.youtube.com/watch?v=MuAVOpO7yFc
@HACKERBILL#67682 u can easily nip an ISO of any windows OS out there. I used to use VBox but i switched to VMWare. I know from experience that VMs are best with Windows 98 or above. I suggest using windows 10 though. In terms of setting up your VM, it is rather straightforward. I suggest giving around 2-4 GB of RAM for your VM. The youtube links supplied by reportingscammers007 should help you.
And if you need the ISO, you can legally obtain them by following these instructions
https://www.howtogeek.com/186775/how-to-download-windows-7-8-and-8.1-installation-media-legally/
@HACKERBILL#67682 if you need help Hackerbill let me know you can contact me on this Discord
@HACKERBILL#67682 pm me on the name @꧁Wob Leͥgeͣnͫd꧂#8919 or yes typ @Wob i m will help you amke it compleet stealty and even put some off myn junk on it
what vm on vmwere should u use
@minypony#67796 Personally, Windows 7 is my go-to VM. Grab the ISO, install it, activate it if you can, and use that as your VM.
Two critical things to do are to mask the fact it is running in a VM and second, create a snapshot so you can revert back to the original VM after they remote into it.
I am a mac user, but I need the iso… Where do I get it?
Just a note that in order to convincingly use a VM for scambaiting, you must make it “stealthy”. I have put a couple of links to videos that show this process.
For VMWare Workstation: https://www.youtube.com/watch?v=6TM45vNI4Qc&list=PLSqmwuQdazfG_L_cmBGiRHuogveV-5Pri&index=4&t=925s
For VirtualBox: https://www.youtube.com/watch?v=6TM45vNI4Qc&list=PLSqmwuQdazfG_L_cmBGiRHuogveV-5Pri&index=4&t=925s
AND
https://www.youtube.com/watch?v=gThdRKsMzvI&list=PLSqmwuQdazfG_L_cmBGiRHuogveV-5Pri&index=2
(you will have to deal with a squeaker on the second video).
For VirtualBox, watch the video until he talks about going into the BIOS, then watch the second video in order to change the BIOS for VirtualBox.
VMWare users don't have to worry about this, as the BIOS changing process is outlined in the VMWare video. (nor will they have to deal with the squeaker).
@HACKERBILL#67810 See my post above to get the ISOs
@reportingscammers007#67827 Do you need to do anything in particular with network settings or anything else for security? Also my msinfo won’t change over properly using the Jim Browning tutorial so I end up with VMWare still in my msinfo. (I’m using windows 10 outside of my VM and windows 10 for the VM)
@nickexp yes, you do want to use NAT mode not bridged in the network settings. What version of VMWare are you using?
@reportingscammers007#67852 VMware Workstation 15 Player. Just set it to use NAT mode, but that says I’m sharing the IP of my host? I mean I’ll be using a VPN anyway but that doesn’t seem secure enough? Care to give me a basic explanation since I don’t really do much of anything to do with networking.
So the mods are sleeping 
which is why I’m replying to @nickexp without his comments posted, but…here are the differences between the three options. TLDR: NAT allows your VM to use your INTERnet, but not your INTRAnet, so the chances of the host machine being tampered with are lessened.
Host-Only: The VM will be assigned one IP, but it's only accessible by the box VM is running on. No other computers can access it.
NAT: Just like your home network with a wireless router, the VM will be assigned in a separate subnet, like 192.168.6.1 is your host computer, and VM is 192.168.6.3, then your VM can access outside network like your host, but no outside access to your VM directly, it's protected.
Bridged: Your VM will be in the same network as your host, if your host IP is 172.16.120.45 then your VM will be like 172.16.120.50. It can be accessed by all computers in your host network.
To clarify NAT mode – On my machine, my HOST’s IP address is 192.168.0.2, but my VMs IP is 192.168.58.1.
My VM can reach the WWW, and allow scammers to connect into it, but my HOST cannot talk to my VM computer (ping, shares, etc.)
@reportingscammers007#67856 ah ok, that makes sense. Thanks a lot dude. I’m also having issues making my VM more stealth, msinfo specifically doesn’t seem to want to comply. Able to help with that? If you wanna move over to discord or something I’d imagine this would be sorted faster but regardless I do want to be able to get in contact with some people who actually know their crap to help me out haha
@nickexp What did you change in the .VMX file?
You need to add
SMBIOS.reflectHost = "TRUE"
To change the .VMX file - Make sure the VM is closed and not running before making the change. Typically, the file will be in C:\Users\<username>\Documents\Virtual Machines\<VM NAME>
@reportingscammers007#67859 Already did that but double checked. It’s showing SMBIOS version as 2.7 and BIOS Version/Date as VMware
Assuming you’ve rebooted the VM already, go to RegEDIT and navigate to
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTIONS\System\BIOS
Look under BIOSVendor and see if you can modify that setting (double click on it).
LOL @Markiemm#67865 I’m just messing with ya. You and the rest of the team do great work. I should be in bed…but…
EDIT: It works with VMWare, as that's how I'm currently using it.