kernel mode anti cheat
Find a file
2023-10-13 03:33:39 +11:00
debuglib fix up pool reporting system 2023-09-18 13:15:26 +10:00
driver reference counts 2023-10-12 22:27:40 +11:00
include pool scan changes 2023-09-17 13:14:02 +10:00
server c: 2023-10-04 03:03:55 +11:00
service some stuffffffff 2023-09-24 21:13:20 +10:00
user working!!! qwoooo 2023-10-12 03:05:29 +11:00
.gitattributes Add .gitattributes, .gitignore, and README.md. 2023-08-15 22:02:15 +10:00
.gitignore Add .gitattributes, .gitignore, and README.md. 2023-08-15 22:02:15 +10:00
ac.sln pool scan changes 2023-09-17 13:14:02 +10:00
dblayout.drawio e 2023-09-08 03:49:36 +10:00
README.md update readme 2023-10-13 03:33:39 +11:00

ac

some things to note:

  • open source anticheat (oxymoron)
  • currently only tested on 10 19045 and since offsets are currently hardcoded u may experience technical difficulties. This will be fixed in the future when i either finish the debuglib or just use a pdb parser or maybe another method ;)
  • as a passion project i am really only implementing methods which i find enjoyable to either research or build which is why you see a lack of hooks and other such. Maybe in the future c:

how 2 use

  1. use the osr loader to load the driver at "system" load.
  2. inject dll into program you want to protect, i used notepad for testing
  3. logs will be printed to dbgview and the usermode dll via stdout

driver must be named "driver.sys" (sorry..)