How es3n1n/defendnot works
Project type and purpose
• defendnot is a low-level Windows system utility / CLI tool whose goal is to disable Windows Defender by directly interacting with the undocumented WSC (Windows Security Center) API.
• It’s not a web app or full-stack service, but a command-line launcher plus a DLL payload that hooks into Windows internals.
File structure
Top-level modules:
• cxx-shared/…
– A Git submodule containing headers (ctx.hpp, defer.hpp, ipc.hpp, names.hpp, util.hpp) used by multiple components for shared utilities (context handling, IPC abstractions, common names, defer macros, etc.).
• defendnot-loader/…
– A console app (“defendnot-loader”) whose main responsibility is:
• parsing CLI args
• optionally registering itself in autorun on Windows (to persist after reboot)
• injecting or invoking the defendnot DLL to talk to WSC
• defendnot/…
– The actual DLL payload (dllmain.cpp) plus “bootstrap” and “core” code:
• bootstrap/bootstrap.cpp/.hpp: entry point that sets up the payload environment
• core/com.hpp: wrappers for interacting with undocumented COM interfaces of WSC
• core/log.hpp: logging support
• wsc-binary-check/…
– A small CLI tool to verify whether a binary is correctly registered in WSC.
Supporting files:
• .gitmodules, cxx-shared.vcxitems → manage the shared submodule
• Multiple Visual Studio project files (.vcxproj, .sln) → build, link, and dependency graph
README for additional insights
• Confirmed the high-level workflow: loader registers in WSC via direct API calls, persists via autorun, and can disable itself.
• No network or DB; pure Windows API interactions.
Final advice
• Be exhaustive: break the payload into “bootstrap” vs. “core/com” blocks.
• Sequential data flow for the disable operation.
• Build artifacts (VS projects) only if the engineer needs to understand build dependencies—otherwise focus on runtime components.