How lamachin3/droppy works
Project type and purpose
• This is a full-stack, web-based “dropper builder” tool. The user interacts with a browser UI (frontend) served by a Flask backend. The backend interprets user selections (injection, payload loading, encryption, etc.), invokes build logic, and compiles a customized C dropper (dropper_core) for download.
File structure
• Top level:
• backend/ – Python Flask API, build scripts, static assets, Jinja2 templates
• dropper_core/ – C source tree, modules folder, Makefile & Visual Studio project
• setup.ps1, setup.sh – environment/bootstrap scripts
• backend/ sub-structure:
• app.py, routes.py – entrypoint, HTTP route definitions
• dropper_builder/ – builder.py orchestrates module selection → C code generation; module_info_parser.py reads module metadata; shellcode_generator.py embeds payloads
• static/ + templates/ – CSS/JS assets + HTML views
• config.py, utils.py – global configs, helper functions
• dropper_core/ sub-structure:
• modules/ – plugin-style folders (anti_analysis, encryption, injection, etc.) each providing .c/.h
• common headers, syscalls/, utils/, Makefile, VS projects
README for additional insights
• Confirms features (injection, payload loading, encryption, stealth).
• Describes simple setup and run instructions.
• Highlights separation: “backend/” = API & build scripts; “dropper_core/” = C source.
a. Main components
1. Client Browser (UI)
2. Flask Web Server (app.py, routes.py)
3. Builder Service (dropper_builder package)
4. Dropper Core Codebase (dropper_core/)
5. Compiler Toolchain (Make/gcc or MSVC)
6. Download/Storage (artifact endpoint)
b. Relationships & interactions
• Browser → HTTP request (module selections) → Flask routes
• Flask routes → invokes Builder Service
• Builder Service → reads module metadata, writes temp C files/configs
• Builder Service → calls Compiler Toolchain on dropper_core + generated code
• Compiler → outputs binary (.exe)
• Flask → serves compiled binary back to Browser
c. Architectural patterns
• MVC-ish: templates (views), routes (controllers), builder & utils (model/services)
• Plugin architecture in dropper_core: each module is a self-contained plugin directory
• Separation of concerns: web API vs build logic vs C code
d. Key technologies & frameworks
• Python 3, Flask, Jinja2, JavaScript/CSS (frontend)
• dropper_builder (custom Python package)
• C, Makefile / Visual Studio projects for compilation
Detailed elements
• The dropper_builder package internals (module parser, shellcode generator)
• The dropper_core/modules collection as an expandable module set
• The Makefile / VS project as part of the compiler block
• External link to HWSyscalls under stealth techniques as an optional external dependency