How catblackcrack/rabbit_modmailtm works
Project Type and Purpose
• This is a desktop automation tool (Windows, .NET WinForms) that automatically registers Facebook accounts on an LDPlayer Android emulator.
• Core use-case: batch-create Facebook profiles via emulator control (ADB), captcha solving, device fingerprinting, and remote web requests.
File Structure Analysis
• Top-level:
• ToolRegFB.sln / ToolRegFB.csproj: .NET solution and project.
• README.md: succinct description.
• Properties/, Resources/: .NET resource and assembly info.
• ToolRegFB/: C# source files (WinForms UI, logic classes).
• bin/Debug/net48/: compiled output, supporting files (APK, ADB, extension, data, logs, outputs).
• Source packages:
• UI forms (frmMain, frmViewLD, ns*/frm*.cs) for different features.
• Logic classes: AutoControl.cs (emulator & UI automation), CaptchaService.cs, Device.cs, RequestFacebook.cs, Common.cs.
• Namespaces ns0…ns10: modular features (Napxu, Shopee, phone verification, contact sync, etc.).
• Resources & Data:
• bin/Debug/net48/app/*.apk: emulator apps (Facebook, ADBKeyboard, device-ID changer).
• data/…: name lists for account generation.
• setting*.ini: configuration.
• output/ and log/: results and logs for each run.
Main Components
a. User Interface (WinForms)
b. Core Automation Module
• AutoControl
• Device (device fingerprinting)
• ADB wrapper (adb.exe)
c. Registration Engine
• RequestFacebook (HTTP interactions)
• CaptchaService (third-party captcha solving API)
d. Emulator Layer
• LDPlayer instance controlled via ADB
• APKs installed (facebook.apk, facebooklite.apk)
e. Data & Configuration
• Local data store (data/… text files)
• Settings (INI files)
• Output folder (account results)
f. External Services
• Captcha solving API
• Facebook servers (registration endpoints)
Component Interactions
• WinForms UI invokes the Registration Engine based on user input.
• Registration Engine calls AutoControl to push APKs and simulate touches via ADB.
• Device module changes emulator device ID between registrations.
• CaptchaService fetches and solves captchas via external API.
• RequestFacebook posts registration data to Facebook and handles HTTP responses.
• Results and logs are saved to file system (output/, log/).
Architectural Patterns and Technologies
• Modular namespaces (ns0…ns10) for feature isolation.
• Layered pattern: UI → Automation → Registration logic → External services.
• .NET Framework WinForms, ADB command-line integration, REST calls, file-based config.
Numbered Workflow for Full Process
1. User launches the WinForms application (frmMain).
2. Application loads settings (.ini) and data lists (data/US, VN, THAI).
3. User clicks “Start Registration,” specifying batch size.
4. For each account:
4.1. Device module issues ADB commands to change emulator device ID.
4.2. AutoControl pushes or launches facebook.apk via ADB.
4.3. RequestFacebook initiates registration HTTP session with Facebook servers.
4.4. CaptchaService downloads captcha image, sends to solving API, receives solution.
4.5. AutoControl inputs solved captcha and other registration fields via simulated touches/keyboard.
4.6. RequestFacebook confirms registration and checks for 2FA or checkpoint.
4.7. Results (success, errors) are logged to output/facebook/*.txt and to log/log.txt.
5. End loop. UI shows summary of registered accounts and any failures.