[Unofficial] List of Legit / Scam EFT Cheat Providers

Quote:

Originally Posted by Simpliciti Uhh, modern *trash* spoofers. Clearing your OS key is ridiculous lol

VGK, EAC, BE and tarkov launcher all log your OS key

Quote:

Originally Posted by MarshallTM VGK, EAC, BE and tarkov launcher all log your OS key

Spoofing and *clearing* OS key are NOT the same.

Quote:

Originally Posted by Simpliciti Spoofing and *clearing* OS key are NOT the same.

They totally are. every spoofer you use for modern games will clear traces

give up dude

Quote:

Originally Posted by MarshallTM They totally are. every spoofer you use for modern games will clear traces give up dude

Doesn’t matter how much you larp it won’t change the fact. Been using the best spoofer on market and never ONCE has my OS license cleared lmfao

Quote:

Originally Posted by Clutch-Solution we never had these features ^^ but instead of fuser esp we offer chams without fuser. Undetected since release.

There are no distinguishing features from other providers, but it costs nearly twice as much.

Quote:

Originally Posted by Simpliciti No he had a point. Foxyz spoofer messed my hardware after shutdown/reset. It invalidated my damn OS key.

Hey mate, pressing "Restore Registry" & "Unload" on the loader then opening your Windows activation page will result with your key being restored as it was before spoofing!

Quote:

Originally Posted by MarshallTM VGK, EAC, BE and tarkov launcher all log your OS key

BE: Harddrives serials only, does gather motherboard info but never uses it for bans. Think it was disabled and never fixed after some bad stuff happened xd

Battlestate launcher: Gets multiple things and creates a hash, so you can literally just change your harddrives serials and be fine

OS Key is never used for the big 3 for legal reasons. Some experimental stuff on certain games might use it, but it is illegal in many countries and huge risk for lawsuits. Same reason that EAC and VGK has started clearing HWID bans after certain periods of time

Quote:

Originally Posted by ZSOFTWARE BE: Harddrives serials only, does gather motherboard info but never uses it for bans. Think it was disabled and never fixed after some bad stuff happened xd Battlestate launcher: Gets multiple things and creates a hash, so you can literally just change your harddrives serials and be fine OS Key is never used for the big 3 for legal reasons. Some experimental stuff on certain games might use it, but it is illegal in many countries and huge risk for lawsuits. Same reason that EAC and VGK has started clearing HWID bans after certain periods of time

Sure but legally not at all.

Anti cheats historically have never followed the right to be forgotten clause in the GDPR and unless challenged probably aren't even required todo so

I am not sure what you're referencing but logging an OS key would be 100% justified in the EU/US for an anti-cheat company.

Quote:

Originally Posted by ZSOFTWARE BE: Harddrives serials only, does gather motherboard info but never uses it for bans. Think it was disabled and never fixed after some bad stuff happened xd Battlestate launcher: Gets multiple things and creates a hash, so you can literally just change your harddrives serials and be fine OS Key is never used for the big 3 for legal reasons. Some experimental stuff on certain games might use it, but it is illegal in many countries and huge risk for lawsuits. Same reason that EAC and VGK has started clearing HWID bans after certain periods of time

For BSG launcher, the hash is just used as a signature - everything is sent in clear text. Unknown what is used for HWID ban, but rumors are mainboard swap suffices.

Quote:

Originally Posted by n3rdsupreme For BSG launcher, the hash is just used as a signature - everything is sent in clear text. Unknown what is used for HWID ban, but rumors are mainboard swap suffices.

I have tested it, my spoofer only changes harddrives serials for battleye and it gets right around it

Quote:

Originally Posted by MarshallTM Sure but legally not at all. Anti cheats historically have never followed the right to be forgotten clause in the GDPR and unless challenged probably aren't even required todo so I am not sure what you're referencing but logging an OS key would be 100% justified in the EU/US for an anti-cheat company.

Them not following GDPR is outdated information. Last 2 - 3 years they have tighten up signficantly. Not just with hardware related info, but also what they pick up from peoples pc's in relation to detections and how long they keep it

Windows License keys fall under the category of a credential. Rules for credentials are infinitely more restrictive.

They also have to account for data minimisation, where there is a strong argrument that other things like your hardware id's (which arent credentials) are more effective. Therefore it becomes even more of a slippery slope

So because of data minimisation and that it is a credential, it is basically a lawsuit waiting if they collect it. Let me remind you the penalty can be upto 4% of annual revenue, so no serious anti cheat is willing to take that risk

Quote:

Originally Posted by n3rdsupreme For BSG launcher, the hash is just used as a signature - everything is sent in clear text. Unknown what is used for HWID ban, but rumors are mainboard swap suffices.

Just open bsg launcher in dnSpy. The code is (or at least was) as clear as day.

Quote:

Originally Posted by SauceMachine Just open bsg launcher in dnSpy. The code is (or at least was) as clear as day.

How do you determine from BSGLaunchers code what they use on their side to hwid ban? Everything they collect is sent to their servers in cleartext and not as was previously mentioned only a hash of it. What they do with that information we cannot deduce from dnSpy.

Adding to that the game itself now also sends a bunch of PCIe and mainboard serials when you launch it so previous methods may or may not suffice to circumvent bans.

Quote:

Originally Posted by n3rdsupreme How do you determine from BSGLaunchers code what they use on their side to hwid ban? Everything they collect is sent to their servers in cleartext and not as was previously mentioned only a hash of it. What they do with that information we cannot deduce from dnSpy. Adding to that the game itself now also sends a bunch of PCIe and mainboard serials when you launch it so previous methods may or may not suffice to circumvent bans.

I haven't looked at the code in years though, the last time I had a look at it the hash was the only thing shipped off. That being said there are more at play recently in addition to what's collected by the launcher that no one seems to be aware of which I won't really get in to here.

Quote:

Originally Posted by MarshallTM VGK, EAC, BE and tarkov launcher all log your OS key

Quote:

Originally Posted by MarshallTM Sure but legally not at all. Anti cheats historically have never followed the right to be forgotten clause in the GDPR and unless challenged probably aren't even required todo so I am not sure what you're referencing but logging an OS key would be 100% justified in the EU/US for an anti-cheat company.

BE's entire HWID is just checking \\Device\\Harddisk0 through deviceioncontrol and then verifying it against SMART_RCV_DRIVE_DATA. They don't grab any other HWID, leave any traces. Its a single disk drive serial, you can remove the diskdrive 0 from your machine and bypass their HWID. This is common knowledge. Battleye hasn't done a meaningful update in the past half a decade so idk why you are spouting such rubbish. Also why would anyone want your windows CD key when you have a good 30 hardware backed serials you can use that are in fact locked to physical hardware. Windows leaves a bunch of traces to lock your windows key to. They have a full offline DRM using files storing hardware information.

Server space doesn't grow on trees and backend engineers come in all shapes and colours, before you know it you end up paying absurd amounts to maintain your backend. Storage servers aren't local anymore, you use third party hosted (Normally AWS which is extortionate) databases on dedicated database servers. You then pay for AWS to scale your servers to which comes with an even more extortionate price tag as you horizontally scale a cross server database. Doing so also adds delay due to mutexs and scattered data. Utilised data is expensive to store but very valuable. At no point is any major AC throwing away your data or deleting it, People thinking your hwid bans expire due to GDPR have never worked backend. Your hwid expires because its moved onto a redundant storage machine. They will have dedicated servers for ploughing through database instances, seeing when data was last used, old banned data and if its old, unused or simply infrequently used; it gets moved onto a massive storage server. Having dedicated servers doing this, creates latency for your AC servers that need to go through the same data but its constantly being locked under mutex mid query. So when you are spending half a million a month on servers and backend engineers and someone comes up with this bright idea to store data that can be changed by changing a fucking registry key, i would expect them to get a message from HR about them getting sacked within the week. The actual retardation to store such unnecessary data. AI telemetric data is worth a whole load fucking more than another shitty hardware identifier. Storing stupid data costs a lot. The most valuable data will always be AI trainable data. Everything thats done in anti cheats of massive proportions such as EAC have to go through multiple dev teams and managers before it will ever get agreed on, storing stupid data will instantly get rejected. The anti cheat team can't just decide to add new things to the databases as so much other infrastructure will then need updating by the backend team and that needs layers of approval by none technical managers and team leaders.

The reward from collecting HWID is only as good as the algorithm that connects serials to accounts. BE just uses a diskdrive serial which makes it very simple, just ban someone with that disk serial if the disk serial was logged in on an account within the past year. When you are logging 30 hwids, you now have to start judging if someone just bought this component off facebook marketplace 2nd hand. The anti cheat needs to then go through all this data and start making judgements off of if its a sold part or someone evading bans. Theres a reason why vanguard historically let you play with banned disk serials if enough other stuff changed but EAC didn't. Better devs make better algorithms, doesn't matter how much you collect if theres a dev diff. The more indepth you want to scan and compare, the more you are going to hold up your threads. Resources are precious. EAC has to service 2.2 billion unique devices a month, they don't have time for suboptimal data and retarded devs.

Serials are checked for formats/manufacturer rules. Perm spoofers that leave your serials with default_string or other horseshit get you choked out when the AC then compares against other people with that same device that actually have hardware ids on the same device name. Then you get to automatically flag them as a known cheater as you know they ran some shitty firmware editor tool. You can't do that for windows keys since most people use KMS to activate; so the data holds little to no value at all. Anyone can edit them in registry, theres no value to it. THere is no "I got you editting this!!", its simply useless. You are better off using an identifier that has a dual purpose. These clueless kids selling perm spoofers really did fuck up the market with their pasted junk. When your entire userbase can get wiped out by checking if serials conform to standards is a meme. Just another datapoint for ACs to plot.

Thats enough of a lesson in backend engineeering for you. Your post history shows you constantly trying to undermine cheat devs. Larping when you clearly have no development background, lack the most basic knowledge on the most primitive anti cheat really isn't helping your case. Arguing with cheat devs seems to be your go to.

As you want to argue with people that correct you, how about you devirtualize the BE daisy binary? last time i checked it didn't even update to 3.10 yet. All VMP has done in the past 5 years is add basic MBA on their gates, only on 100% VM complexity, and the VM handlers now have their shitty operator substitution they put in their "mutation" and their awful junk bytes. The VMP 3.5.1 source leak gives you everything you need to lift all their VM obfuscation to then get bare VM handlers and gates and throw it back into VTIL. Their VM gate obfuscation is legit the same as the prototype one in the 3.5.1 leak. Its trivial to mitigate all their shitty new protections to get VTIL to work on it again, or simply just run it through mergen since it should still be on 3.8.1. You could also check UC but since you want to argue with people, you should check for yourself as you might not believe the countless reversals.

Quote:

Originally Posted by Tubzzz BE's entire HWID is just checking \\Device\\Harddisk0 through deviceioncontrol and then verifying it against SMART_RCV_DRIVE_DATA. They don't grab any other HWID, leave any traces. Its a single disk drive serial, you can remove the diskdrive 0 from your machine and bypass their HWID. This is common knowledge. Battleye hasn't done a meaningful update in the past half a decade so idk why you are spouting such rubbish. Also why would anyone want your windows CD key when you have a good 30 hardware backed serials you can use that are in fact locked to physical hardware. Windows leaves a bunch of traces to lock your windows key to. They have a full offline DRM using files storing hardware information.

Amazing, I didn't expect multiple paragraph's because i added BE to my list by accident.

Anyway i will not take anything you say seriously given your rise to fame was exit scamming a csgo product called "oreo" and a pasted eft product

Thanks anyway.

Quote:

Originally Posted by ZSOFTWARE I have tested it, my spoofer only changes harddrives serials for battleye and it gets right around it Them not following GDPR is outdated information. Last 2 - 3 years they have tighten up signficantly. Not just with hardware related info, but also what they pick up from peoples pc's in relation to detections and how long they keep it Windows License keys fall under the category of a credential. Rules for credentials are infinitely more restrictive. They also have to account for data minimisation, where there is a strong argrument that other things like your hardware id's (which arent credentials) are more effective. Therefore it becomes even more of a slippery slope So because of data minimisation and that it is a credential, it is basically a lawsuit waiting if they collect it. Let me remind you the penalty can be upto 4% of annual revenue, so no serious anti cheat is willing to take that risk

I am glad they're taking more robust steps when it comes to handling HWID information. but none of it is coming from any EU pressure or GDPR regulations unfortunately

The GDPR doesn't mention anything about credentials being "infinitely more restrictive". an OS key also doesn't fit the meaning of credentials for Art.4 or anywhere else in the GDPR

Microsoft themselves do not regard keys as credentials -> [Only registered and activated users can see links. Click Here To Register...]


also for the point of anti cheats like EAC or VGK clearing hwid information after x about of time, this is purely for internal reasons. they aren't compelled by the GDPR to wipe this data. even if requested it can just be anonymized and stored

BE & FACEIT both mention they store data like hwid indefinitely "for the entire duration of the provision of its services for a game" <- battleye

if you want to test it write them an email and see how long it takes them to wipe your data or even reply, shocker they wont...