Looking for private Faceit cheat.

[hory76]

Looking for private Faceit cheat.

It must be private and undetectable. I will buy and pay for a subscription.

[getnzt]

Long term you will want to go SMM (Mobo Firmware). Short term if you don't mind getting banned every 6-12 months - a good custom DMA firmware provider. There are private DMA providers that could be UD long term but you would need to have an invite from an insider to one of those builds. Anything Hypervisor that doesn't load on boot is likely a fake (Faceit will require secureboot and hvci in many instances). Digitally signed drivers w/ EV cert are another option but difficult to find a good provider + if their company gets blacklisted the whole group gets banned so you are relying on each user of the driver to not rage. If someone offers you a solution thats incredibly priced its likely a scam. Faceit does delayed bans so new solutions can popup and have good reviews for ~6 months then everyone gets banned.

The best way to approach this is to either find a worldclass private developer or to simply pick a solution that is logically secure by the approach itself. There is also the issue that as your get higher ranking you will be under more scrutiny. So a solution that works entry level for a while will not work in higher ranks.

Another simple test would be if the solution has aimassist. You can ask basic questions about how they get around hardware mousemovement and pixel movement irregularities (a basic non-linear / bezier curve aimassist will not work on faceit long term).

Edit: Another red flag is when developers rely on a "video" of their solution. This is a useless metric since you can easily make a video that looks like its on faceit, or actually join a faceit match on a second pc, cheat, record video, and get banned months later. Videos of the solution provide little to no evidence of their long term detect-ability. Moreover, its extremely unlikely a developer who can bypass faceit would waste their time building such a preview as they would be smart enough to understand the aforementioned point.

All in all, bypassing difficult solutions is not about being able to read its memory or move your mouse, its about being able to do that in a way that stays UD permanently.

[df90f9g8g]

+1 for nzt been ud since I started over a year ago on face1t

[vnmlike]

The mobo method described here by NZT is public. It is known, though not widely known. Nevertheless, FACEIT is certainly currently working on finding a way to best detect and block it.
If NZT claims it is not public, I will publish the relevant links. So just leave it.

[getnzt]

Originally Posted by vnmlike

The mobo method described here by NZT is public. It is known, though not widely known. Nevertheless, FACEIT is certainly currently working on finding a way to best detect and block it.
If NZT claims it is not public, I will publish the relevant links. So just leave it.

SMM has been a public method since around 1993 to be exact. DMA in 58' when IO was first utilized. Hypervisors were first used in the 60's.

The question isn't when the method became public, it's whether it's difficult to detect. Unless you are referring to public examples utilizing SMM - which you can find on EDK2/Tianocore Docs. If you understand privilege rings then you will understand why its a smart approach.

The reason its effective is that its impossible to read the memory existing in SMM unless you already are in SMM. Blocking SMM is impossible; as you would DMA through IOMMU. DMA Blocking works because IOMMU is managed in Ring 0 (or in the case of a Hypervisor potentially Ring -1) and therefore you can make modifications to the IOMMU Range or access the DMA devices either directly or indirectly thanks to how the PCI Bus operates. For SMM, this is protected by your physical CPU chip. To evade this protection and find an SMM vulnerability then ship it to users would almost certainly get your driver blacklisted and subsequently destroy the driver owners business (AC).

While Hypervisors and DMA are reasonable solutions, the amount of detection vectors and the shifting landscape of the ability to accurately action those vectors changes quite frequently. Whereas a SMM solution, if done properly, has a set amount of truly actionable heuristics and therefore doesn't require constant cat and mouse. That being said if your DMA solution ships with a customized BIOS Firmware for the motherboard, you can keep DMA quite difficult to detect.

[Relentless]