How dharani-sanjaiy/malware-development works
Core Components
• Injection Modules: Each C++ file (e.g., APCInjector.cpp, DLLInjector.cpp, ClassicThreadHijacking.cpp, etc.) acts as a stand-alone module demonstrating a specific injection technique.
• NTAPI Support: The NTAPI folder (Headers.h and NtRemoteThreadInjection.cpp) provides support for low-level operations, likely used by one or more of the injection techniques.
• Payload: The shellcode (calc.exe) is the actual payload employed across these modules.
• Shared Infrastructure: Although not explicitly delineated as libraries or other services, the repository’s structure indicates that each injector relies on common techniques and possibly shared helper functions.
Highlighting Architectural Patterns and Design Principles
• Modularity: Each file represents a distinct module based on the injection technique. This encourages a modular architectural view.
• Separation of Concerns: The separation between payload generation (using msfvenom’s shellcode) and injection methods is a key design element.
• Reuse of Low-Level Components: The NTAPI directory encapsulates the low-level Windows API calls that can be reused across multiple injection techniques.
Relevant Technologies and Frameworks
• Windows API: A core part of these techniques relies on Windows-specific APIs and NT internals.
• C++: The source files indicate that the project is implemented in C++.
• Shellcode (calc.exe generated using msfvenom): Highlight this as the payload used across injection techniques.
Essential Elements
• Each injection technique (e.g., APCInjector, DLLInjector, etc.) should be represented as its own node.
• The “NTAPI” component (from the NTAPI folder) should be connected to those modules that depend on it.
• Notes or callouts if necessary to denote how each component interacts with system internals.