PE‑OopsSec is a security utility designed to identify and flag common OPSEC mistakes hidden inside PE files
Like this: E:\Movies\Action\Not_Porn\I_Swear_Its_Not\Why_Would_I_Lie\You_Have_Trust_Issues\Told_You_So\Empty_Folder\NASA_hot_kitten.jpg.pdb
Github: TwoSevenOneT/PE-OopsSec
#redteam #antimalware #pentest
@kyREcon This is the demo file I normally use. The goal of the tool is to build a scanner that checks files after they are built but before deployment. Better to catch too much than to miss something critical
Been coding a lot with AI, so now I’m creating a toolkit (also AI‑assisted 😄) to check for OPSEC mistakes in PE files before they’re used in the real world.
Both the article and the toolkit will be released soon 🤗
New #redteam tool for blocking EDRs: EDRChoker
Instead of fully blocking the EDR agents' connections to their server, we can throttle their bandwidth so they consistently time out when sending data, which is effectively the same as blocking but avoids triggering "block" or "drop" packet events
#pentest #cybersecurity
Github: TwoSevenOneT/EDRChoker
@EAehorn I think you should determine which process handles the connection task to the MDE server first. I've already included it in the list, but I'm not sure it contains all the MDE processes
@IstaPee@RossMichaels328@Defte_ So, EDR with core rules will trigger some warnings. But the most important thing is that the client now can’t send logs to the server anymore, right?