How lvn11lvn/durakonline-autoreg-and-cheating works
Project Type and Purpose
• This is a multi‐tool automation suite (CLI application) designed to register accounts and “boost” in-game currency for Durak Online. It also includes reverse-engineered Apple JS authentication, a Gmail API client, and an SMS verification helper. The README confirms it’s a “регер и накрутчик валюты дурак онлайн,” with Apple JS reverse, Gmail API, and SMSHubOrg integrations.
File Structure Analysis
• Top-level orchestrators:
• main.py – entry point
• durak_bot.py – core booster logic
• durak_token_checker/ – pipeline for validating tokens
• Modules for external services:
• Apple/ – Python wrappers and “reverse-engineered” JS under utils/apple_auth.js
• GmailWebApi/ – gmail_client.py, models.py, main.py
• SMSHubOrg/ – api.py, properties.py
• DurakOnline/ – socket_api.py, websocket_api.py, utils.py
• Config and local data:
• config.py, proxies.txt, reged_tokens.txt, invalid/valid_tokens.txt
• Utilities:
• utils.py, module-specific tests (apple_auth_test.py)
Key Architectural Components
a. CLI Orchestrator
• main.py invokes durak_bot and/or token_checker.
b. Durak Currency Booster
• durak_bot.py uses DurakOnline/socket_api and Apple/Gmail/SMS modules to register or log in, solve captchas via SMSHub, then perform boosting actions via the game API.
c. Token Checking Pipeline
• durak_token_checker/token_checker.py reads tokens, validates them against the DurakOnline API, and writes results to valid_tokens.txt or invalid_tokens.txt.
d. External Service Integrations
• Apple: apple_auth.js + auth_durak_webapi.py/web_api.py
• Gmail: GmailWebApi/gmail_client.py + main.py
• SMSHubOrg: SMSHubOrg/api.py
e. Data Stores
• Flat files for tokens, proxies, configuration
Relationships and Data Flows
• The CLI (main.py) is the central orchestrator.
• It delegates:
• To durak_bot.py → calls DurakOnline module, AppleAuth, GmailWebApi, SMSHubOrg
• To token_checker → reads flat files, calls DurakOnline API
• Each external‐service module communicates via HTTP or sockets to its respective endpoint (e.g., Gmail REST, Apple reverse JS endpoints, DurakOnline sockets, SMSHub HTTP).
• Results (new tokens, boosted currency) are written back to the local data store (reged_tokens.txt, proxies.txt).
Architectural Patterns and Principles
• Modular separation by external service (single-responsibility modules)
• CLI orchestration layer
• Flat-file persistence (no database)
• Thin adapters for 3rd-party APIs (Gmail, SMSHub, DurakOnline, Apple)
Final Checklist
• Clear, descriptive labels on every component
• A title: “Durak Online Booster & Token Manager Architecture”