Talking about Antidetect Cloud Machine and clean equipment

Today, a customer had an error of not being able to connect to the network in the VMware. I realized something like this: Virtual Machine and the host are both different IP range, they can not communicate. So, CloudNetwork doesn't do anything! Another important piece of information regarding this case is that he used his iPhone to create a hotspot to connect his laptop to the network. This network was using the gateway IP address 172.20.1.1, and the laptop (the host) had an IP address of 172.20.1.2. However, even after adding the VM to the bridge network and assigning it the IP address 172.20.1.X, he still couldn't ping the host machine. I believe the problem lies in Apple's hotspot mechanism (or phones in general). There are two possible solutions: the simple is to use a common internet connection like a Wi-Fi router, or to use a virtual router.

Well, we have many people using the same platform, but each person has different needs. Some only want to use Bridge because they have a physical router that can spoof IP addresses and split the network; others only want to use NAT because they use Wi-Fi; some use hotspots... Some use VMware, others use VirtualBox. Some manage eBay accounts, others use Amazon carding, and some just want to play games... Each purpose requires a different solution, and the challenge is how a single platform can meet everyone's needs.

Vektor T13's approach: They have many presets, each of which blocks the target "stun servers" using a kind of preset registry... You might succeed the first time, the second time, but never the bulk version. If a device has been completely refreshed and cleaned, then all platforms are the same; there's no point in dividing the presets in that way.

So, what is the right path for a completely clean device that any platform can meet?

1. Always clean install. Regardless of which Windows installation method you use. Cloning an existing Windows installation leaves behind many traces that no one can be confident have completely erased.

2. Event log history reflects user behavior.

3. The list of installed software constitutes fingerprint software for the device. Previously, anti-fraud systems did not publicly disclose this, but since 2023 they have acknowledged it and officially released a Google SDK API that allows reading the list and retrieving information about installed software on a computer.

4. Virtual machine vulnerabilities. I can't say too much about this as it's a trade secret; however, installing VMware tools/Virtual Box Extensions on a virtual machine is a mistake, even if you try to modify strings and PCI, there are still vulnerabilities created by them in the firmware and kernel when the virtual machine starts up.

5. Network connections, proxies, VPNs... and information leakage vulnerabilities.

And there's much more...

I've been involved in the dark forums since 2007, developed "change pc" around 2019, and have spent many years researching and pursuing the pinnacle of technology. I also coined this name for the Antidetect Machine brand, and others have followed suit. It's safe to say that "antidetect" is an art, and the time you dedicate to researching and developing it, your passion, and your desire to conquer it are the biggest reasons I continue on this path.

Thank you for reading my rambling thoughts today!