SCARP.CC 2.2.1m: how it works

Documentation for the current version, 2.2.1m

SCARP.CC

A Windows application for Telegram accounts, restriction checks, profiles and proxies, audience search and collection, messages, invitations, folders, session conversion and other tools. All work takes place in the application's own window.

Accounts and settings are stored locally. Telegram modules use the selected sessions and their proxies. An account cannot run several tasks at once: an active multi-chat or auto-responder also holds its session.

1. Add accounts and proxies, then check the connection.
2. Open the required module, specify the source and select accounts.
3. Review the settings, start the task and monitor the log.
4. Open the results, save the report and wait for completion before closing the application.

Navigation is grouped in the sidebar; Miscellaneous shows the version and application information. Window size and position, sidebar width and workspace layout are saved. The Documentation button is in Settings next to Save.

Before you start

Do not move only the EXE: interface resources and supporting files are part of the package. Only one application instance can use a data directory.

Quick start

1. Extract the release and run SCARPCC.exe. If updating an existing installation, first follow the update instructions.
2. Activate your key. Enter the issued key on the license screen. Choose Russian, Ukrainian or English for the interface.
3. Add proxies. In Proxies, paste proxy lines or load a list and run a check.
4. Add accounts. Use a .session + .json pair, phone login, QR or a suitable import method.
5. Select accounts. Click Check to connect and contact @SpamBot. Check without SpamBot tests availability without sending the bot a message.
6. Open the account details with the gear icon. Review the information, its update time and the assigned proxy.
7. Start the required module. First test the source and limits on a small selection; group cleanup leaves groups immediately after starting.

License and HWID

The key is activated in the application and bound to the device. Copy the HWID from the activation screen. To transfer a license to another computer, contact official support instead of editing license files.

If activation fails

1. Check that the entire key is entered without extra characters.
2. Make sure the Windows date, time and time zone are correct.
3. For connection errors, check internet access and service availability, then try again.
4. Key revoked, Key expired and Different device messages require resolving the license issue.

The license is checked at startup and periodically during use. Background checks run every 30 seconds with a response timeout of up to 20 seconds. Brief interruptions trigger retries while the existing confirmation remains valid; permanent offline access is not supported. License revocation stops protected tasks and connections. Do not publish your key, session files or passwords.

Installation and automatic updates

1. For your first installation, download the official ready-to-use release ZIP. Extract the full package to a writable folder and run SCARPCC.exe. The source code archive is not suitable for this.
2. The application checks for a current version at startup. When an update is available, a separate window shows download, verification and installation progress.
3. After verifying the signature and integrity, the installer replaces the application files and starts the new version. Accounts, sessions, the database and settings are preserved.
4. What's New opens after the update. Reopen the changelog in Settings; the installed version is shown in Miscellaneous.

Updates are downloaded from the SCARP.CC update server. A ready-to-use GitHub Release archive is available for the first installation. Do not close the installer while it is replacing files.

Temporary files are removed after a successful launch. If installation fails, the application attempts to restore the previous version; the backup and log help diagnose the error. If rollback keeps happening, preserve the application folder and contact support with the error text. Older installers may require manually installing the complete package while the application is closed.

Internet access is required to start the application and check for updates. Signature verification remains mandatory. Changelog: all published versions.

Account manager

The table shows locally stored account details, connection and restriction status, assigned proxy and Premium. Search and filters help select rows; bulk actions apply to checked accounts.

Understanding statuses

The Premium star distinguishes a known subscription, no subscription and unchecked information. The expiry date appears only when confirmed information is available; an active subscription may be shown without a date.

Refresh data retrieves current profile and account details. Filenames may be changed to the actual phone number; an existing pair with that name is not overwritten. The Telegram Web button starts a separate login through the account's assigned proxy and may require manual authorization.

Account details and individual proxy

1. Click the gear icon in the account row.
2. View the profile, photo and update time. If cached data exists, the details open immediately using it.
3. Click refresh for current information. If no cache exists, data is requested when the details open.
4. For an individual proxy, select a pool entry or enter your own proxy line and save. Returning to automatic allocation is a separate action.

The details show basic groups, supergroups, channels and private chats separately. Unavailable information is marked as unknown rather than zero. Failure of an individual request does not invalidate a successful main account check.

Current session date comes from the current Telegram authorization, not the file modification time. Its age is not the age of the Telegram account. The separate bulk Creation date command estimates the earliest available activity and does not guarantee the registration date either.

The details show 2FA status and whether a password is saved locally. The password stays hidden until you explicitly reveal it. No saved password does not mean 2FA is disabled. Checks and data refreshes update the details through the already connected session.

The checks section shows the last attempt time, result and reason. Information about a previously confirmed restriction may remain after a network failure during a new attempt. Replacing the authorization prevents reuse of another session's cache and metadata.

Adding an account

Existing files

Telethon uses a pair with matching names: account.session and account.json in the session folder. JSON stores profile and client details; it does not replace authorization in .session. Do not copy a SQLite session that another process has open with a pending write.

Phone login

1. Enter your phone number in international format, then choose client settings and a proxy.
2. Click Get code and enter the code using the method Telegram offers.
3. If 2FA is requested, enter the current password.
4. Wait for confirmation that the file pair was saved, then refresh the table.

QR login

Select a proxy, obtain a QR code and confirm it in Telegram on an already authorized device. Request a new QR code if it expires. If an explicitly selected proxy is deleted or invalid, login stops without silently switching to another connection method.

Other methods

For tdata, HEX and file discovery, use the import and conversion tools. To register a new account with your own number, use manual registration. Existing accounts are not overwritten automatically.

Manual SIM registration

You use your own phone number: the module does not buy numbers automatically. Registration is based on phone login but can also create a new account.

1. Enter the phone number, first name and optional last name, then select a proxy and client settings.
2. Request and enter the code; if 2FA is requested, provide the current password.
3. For a new account, read Telegram's terms and explicitly confirm acceptance and the required age.
4. Set a bio, photo and new 2FA password if needed. Wait for the save result.

Email, payment or an unusual device verification requirement may require completing login in the official client. A profile setup error after confirmed registration produces a partial result: the working session is saved. Do not register again before checking the saved account.

Proxies: pool and assignments

Account details, phone login, QR login and manual registration share one searchable proxy list. The address is shown with a flag from the check results in Proxies. An unknown country uses a neutral icon and Country unknown label. Search accepts an address, country code or country name in Russian, Ukrainian or English; opening the list does not run country detection again.

Open Proxies, add proxy lines, check selected entries and remove confirmed failed proxies if needed. Removing a pool entry does not delete an account.

Line format

socks5://proxy.example:1080:login:password
http://proxy.example:8080:login:password
login:password@proxy.example:1080
proxy.example:1080

The addresses above are illustrative. SOCKS5 is used when no scheme is specified; a port is required and must be 1-65535. The shared pool does not support IPv6. Specify the provider's actual supported type; changing the label does not convert one protocol into another.

Priority

1. An individual proxy from JSON or account details takes precedence over the shared pool.
2. An automatic pool assignment remains valid while the entry is in the pool.
3. When needed, the pool is allocated according to Accounts per proxy.

Resetting automatic assignments and managing the pool must not silently replace a manually assigned proxy. If an individual proxy stops working, fix it in the account details or explicitly return the account to automatic allocation.

The country is detected through a geolocation database or available services and may be unknown. A country detection error does not necessarily mean a connection error. A proxy check does not guarantee Telegram will accept a particular authorization.

Account checks and @SpamBot

Connection and initial authorization checks share a deadline of up to 10 seconds. The checker's allowed timeout in Settings is 5-10 seconds. Selecting another automatic proxy uses the remaining time within the same deadline. Subsequent account details and bot responses have their own timeouts.

SpamBot response wait is set from 0 to 120 seconds; reading the response uses a minimum of 3 seconds, so 0 does not disable querying the bot. No response, unfamiliar text, network failures and FloodWait are reported separately. They do not become an Unrestricted result.

Run summary

After completion, categories reflect this run only. Click a category to select its accounts. Checks that never started are counted separately; collapsing the log does not stop the task or release busy sessions.

Restriction dates

A SpamBot restriction expiry date is extracted only from recognized text with an unambiguous date and UTC/GMT time zone. The original text remains available. For a frozen account, available information includes the start date, appeal link and deletion deadline without a successful appeal. The latter does not mean the account will be restored automatically.

Bulk operations and profiles

Select accounts and click an action on the manager toolbar. Wait for the current task to finish: a busy session cannot be opened for another operation.

Account labels

Click the label button in an account row or beside an account in Multi-chat. Set its name, color and one of 20 icons. You can edit or remove a label.

The manager offers Add label in bulk and Remove label in bulk for selected rows. Labels appear next to the status, in search and in the account selector.

Labels are stored in the account's JSON. Move the session together with its JSON to preserve them. Changing a label in Multi-chat preserves the open dialog and draft; no reconnection is needed.

Task manager

Open Task manager in the left menu to see active and recently completed tasks, their progress and links to module logs.

Stop applies to the selected task. New operations stop starting, current connections close and accumulated results are saved. Actions already completed in Telegram are not undone. Unfinished work is not marked 100% complete.

Bulk checks and account manager actions can also be stopped. Scheduled and other tasks work while the application is open.

Creating chats

Choose accounts, a title, description, chats per account and visibility. Public chats are created as supergroups with a random username; private chats offer the relevant group-type settings.

In What to return after creation, choose ID, link or ID + link. ID is selected by default. A private chat link is an invite link; its availability depends on Telegram.

Set pauses and the FloodWait budget. Confirmed creations, errors and unavailable links are included in the CSV/TXT report. An uncertain result is not counted as a successful creation.

Creating channels

Create public or private channels with selected accounts. Set the title, description, quantity and random username settings for public channels.

Choose the output: ID, link or both. A private channel is created without a public username. The report includes retrieved values and reasons for incomplete results. Telegram sets creation and invitation limits.

Channel cloner

1. Select one account and a destination channel you can manage.
2. Specify the source channel and copy settings: title, description, avatar, messages, visibility and post range.
3. Start the transfer and monitor confirmed progress. Stop is available in the module and task manager.

Supported messages are transferred in their original order with formatting and albums. On an account without Premium, custom emoji and Premium stickers use a standard representation. Simplifications and skipped items are recorded in the report.

Protected content is not copied. Views, reactions, original publication dates and poll results are not transferred. Confirmed progress is saved for resuming; if a send result is unknown, the post is not duplicated automatically.

Account cleanup

A separate module replaces the dialog and contact cleanup buttons in the manager. Seven actions are available: leave channels; leave groups and supergroups; delete private dialogs; block bots and delete their dialogs; clear Saved Messages; delete contacts; remove all profile photos.

1. Select the actions you need. None are selected initially.
2. Select accounts, simultaneous connections, pauses and the FloodWait budget. Deleting private history for the other participant is enabled separately.
3. Click Start. Selected actions run immediately, including archived dialogs. Groups and channels remain in Telegram; the accounts leave them.
4. Review the log and CSV/TXT report. Stop the task in the module or task manager.

Completed means a confirmed action; Nothing to clean means there were no objects. Result unconfirmed requires checking Telegram: the action may have partially completed. For example, after reaching the deletion limit for a long history, further cleanup of the affected account stops.

For partial results, the full report helps identify the cause: only the first 500 rows appear on screen. Problematic actions and account processing errors have separate counters.

Tasks, threads and reports

1. Select accounts using the module button. Check availability errors before starting.
2. Fill in the current form fields. A range minimum must not exceed its maximum; zero is meaningful only where explicitly allowed.
3. Start the task, open the log and then the results. Stop cancels further work and preserves already collected results.
4. Choose a format and save the report. Open beside a result opens the generated TXT/CSV in its Windows default application.

The global thread setting is 1-32. Global search, audience collection, author collection, the inviter and converter use it in their current forms. Modules with a separate Simultaneous accounts field have their own limit, usually 10; the duplicator and reauthorization allow up to 5. More threads do not increase Telegram's allowed quotas.

Module tables preview up to 500 rows. Export saves the full accumulated result. The general technical report limit is 100000 rows; reaching it is reported explicitly. Stopping or encountering an error does not undo completed actions.

Global search, audience collection, author collection and folder creation reports are saved in the system Downloads folder. Other tasks may also return a path in data/module_reports: use the path and open button in the result. Saving again must not destroy the previous file.

With one source chat, audience/author collection does not create a second identical combined TXT. With several chats, separate lists and a combined deduplicated list are available. CSV stores all columns; List, Premium and link outputs are available where the module supports them.

Saved tasks have been removed from the interface. Text templates remain available where supported by the module. Scheduling works only while the application is open and does not replace the system scheduler.

Direct-message campaigns

1. Enter recipient usernames or select one source file.
2. Select the type of message: text, media, forwarding or inline bot. Fill in the fields for the selected mode.
3. Select accounts, quotas, pauses, if necessary, schedule and number of cycles.
4. Check the preview and start the campaign. Save the report of confirmed sends, skipped recipients and errors.

Each recipient may receive a set of several files or forwarded messages. The set counts as successful only after delivery is confirmed. Repeated cycles reuse the original list and may send messages to the same people again.

The campaign's built-in autoresponder replies to the first incoming message from a recipient successfully processed during the current task. It is separate from the standalone AI autoresponder. An unconfirmed send blocks another attempt for that user.

Parameters

Inviter

1. Specify one target group or a template with group variants.
2. Paste a shared list of usernames and phone numbers. To import phone numbers, enable the corresponding contacts option.
3. Select accounts, successful invitations per account and the pause before an attempt.
4. If needed, enable an additional request limit, protection against repeated errors and leaving after the task.
5. Start and save the report; a request does not count as a successful invitation without Telegram's confirmation.

The current form uses a shared queue and success quota, defaulting to 40 per account and a 2-4 second pause. Unavailable users, privacy restrictions, insufficient permissions and existing membership are counted separately. A broadcast channel is not a valid target group for this mode. Uncertain invitations are not resent automatically.

Parameters

Mass subscriptions

1. Enter chat links or usernames. Public and private invitations and addlist folder links are supported.
2. Select accounts and distribution: a shared queue or the entire list for each account.
3. Set joins per account, pauses and additional checks, then start the task.
4. Review the report: joining, requesting approval, existing membership and unconfirmed results are counted separately.

You can check permission to write, leave newly joined groups without that permission and mark recent messages as read. FloodWait stops the affected account. After an uncertain result, the join command is not repeated automatically.

There is no captcha-solving system or 2Captcha integration. Chats with manual verification may require action in Telegram. Stop is available in the module and task manager; the accumulated report is saved in Downloads.

For your own folders, use Creating folders.

Global search

1. Enter keywords, one per line.
2. Choose normal or deep mode, words per account and the minimum member threshold.
3. In Chats to find, set an upper limit or 0 for no user-defined limit.
4. Select accounts and start. After completion, choose the export contents: All data, Links, Links + Member count, Usernames or Usernames + Member count.

Search finds public supergroups with an available member count strictly above the threshold. With 100, a group with 100 members fails and one with 101 passes. Channels and personal profiles are not added to this result.

Normal mode runs up to 27 search variants per word; deep mode up to 729. Deeper search expands queries, but Telegram may return incomplete results. Words beyond the selected accounts' combined quota remain unprocessed.

Link and username lists are saved as TXT; member counts are separated by tabs. All data can be exported as CSV or TXT. Files are saved in Downloads with a new name on each export.

Parameters

Audience collection

1. Paste source groups, one per line.
2. Choose the result format and name search alphabet.
3. Set activity recency, desired statuses, gender estimation and the member or administrator category.
4. Select accounts, start and open the automatically saved TXT or export full data.

The new module works with members accessible to the selected accounts. Public groups are read without unnecessary joining; private invitations may require joining. The alphabet defines name search queries, not the profile language. Phone numbers are saved only if Telegram already shows them to this account.

Gender is estimated with a name dictionary and is not a confirmed personal attribute. Premium creates an additional list of users who passed the filters. The time filter applies to exact last-seen time, not message dates. All statuses bypasses time filtering but not the output format or name filtering.

ID lines may include source chat context; keep it if the next operation uses that format. Separate TXT files and the combined deduplicated list follow the report rules.

Parameters

Collecting chat authors

1. Add source chats or channels.
2. Choose the username/ID format and author filters.
3. Set history depth, select accounts and start.
4. Open the TXT list or export full rows with the discovery source.

Collects unique authors from the history accessible to a particular session. Depth is defined by a message ID range, not by days or the exact number of messages read. IDs may have gaps, and ranges may overlap; duplicate authors are removed.

Last seen more/less than fields filter author activity, not the message publication time. Hidden history, anonymous senders and unavailable information limit completeness. A public source does not require automatic joining; a private invitation may require it.

Parameters

Group cleanup

1. Select leaving conditions and accounts.
2. Review protection for chats where the account is an administrator or owner, the dialog limit and pauses.
3. Click Start: matching chats are left immediately.
4. Monitor the log and save the report after completion or stopping.

The task leaves chats matching at least one selected condition. It does not delete private conversations. Checking for write restrictions, paid messages and administrator protection are enabled by default; leaving all channels is not enabled separately.

Activity is counted over the 24 hours preceding each group check. Service events are not regular messages. Unknown permissions, size and incomplete history are not treated as zero. The separate unavailable-data switch is off by default; even when enabled, it does not turn a network error or FloodWait into a reason to leave.

The dialog limit includes inspected private dialogs even though they are not processed. Reaching the limit means the account was only partially checked. An unconfirmed leave response is recorded as an uncertain result.

Parameters

Creating folders and addlist links

1. Select accounts and enter your own base name. A new form starts empty; you cannot start without a name.
2. Set the size to 100 or choose the account maximum mode.
3. Review the free-space switch, enabled by default. Disable it if existing personal folders must be fully preserved.
4. Separately decide whether to allow converting basic groups to supergroups for the link.
5. Start, compare Groups in folder with Groups in link, then save the table or a TXT of links.

Only existing groups and supergroups of the selected account are used. Channels and private conversations are excluded. With 300 groups and size 100, the name Work produces Work-1, Work-2 and Work-3, provided Telegram's limits allow it.

Before changes, actual account limits are requested, including Premium. A missing individual key in an otherwise successful response is replaced with a documented value, with its source noted in the report; failure to retrieve configuration stops account changes.

When space is insufficient, only the necessary number of old personal user folders is deleted. Shared and imported folders are not deleted automatically. Only folder structure is removed; the account does not leave chats or clear history. Links to deleted folders may become unavailable.

A matching existing folder is reused. A name match with different contents stops work for that account. The full name including its number must fit Telegram's limit; a short base leaves room for the suffix.

The report distinguishes created or reused links, folders without links, deletion, skips, errors and uncertain outcomes. The links TXT contains only confirmed retrieved links; errors and folders without links remain in the full report.

Parameters

Account booster

1. Select at least two of your own accessible accounts with public usernames.
2. Enter message variants, one per line, or select a TXT file.
3. Choose sending, replies or mixed mode; set attempts, cycles and delays.
4. Start and monitor the per-account report.

Messages and conversation partners are selected from the specified set. In reply mode, no suitable incoming message results in a skip, which also consumes an attempt. The booster creates real conversations but does not guarantee changes to Telegram's trust or removal of restrictions. PeerFlood stops the task.

Parameters

Adding contacts

1. Enter phone numbers/usernames or load one TXT, CSV or SQLite file.
2. Choose unique distribution or a shared list for every account.
3. Set the contact count range, delays and accounts.
4. Check the contact cleanup and phone privacy exception switches separately, then start.

Cleanup deletes existing contacts before import and is a separate change. The privacy exception allows the added contact to see the phone number as supported by Telegram. An entry in the source list does not guarantee that Telegram will find or allow adding the user.

Parameters

Publishing stories

1. Select local images or MP4 files and, optionally, a caption with text variants.
2. Specify stories per account, visibility and file distribution.
3. If needed, add usernames for mentions and set their count.
4. Select accounts, check delays and start.

JPG/JPEG, PNG, WEBP and MP4 are supported; up to 100 files. For videos, actual parameters and a duration of up to 60 seconds are checked. Telegram determines publishing availability and limits for each account. Success is recorded from a confirmed story ID; an uncertain publication is not retried automatically.

Parameters

Link checker

1. Enter links/usernames or select one source file.
2. Enable only the extra checks you need: members, private invitation, profile bio, link normalization.
3. Set the link quota and total request/result budget, then select accounts.
4. Save the report, comparing the source link, normalized value and status.

The module does not join groups. Checking a private invitation only provides the available preview. One source address may require several Telegram requests; errors and skips also count toward result quotas.

Parameters

Multi-chat

1. Select accounts and the number of messages to load from history. Media loads on click without a separate switch.
2. Click Connect, then select an account, folder and conversation. The All chats tab shows the account's full list.
3. Open the history, load earlier messages if needed, select a reply and send text.
4. For translation, select incoming and outgoing message languages. Wait for the send result before disconnecting.
5. Stop connections to release sessions for other tasks.

Private conversations, groups and channels are separated by account. Saved Messages, SpamBot and Telegram service notifications are pinned at the top for each account, even without history. They remain available when searching or selecting a folder. Starred chats is a separate local filter for conversations you marked with a star.

Folders load from Telegram on connection. Click Refresh folders to retrieve the current list. Contents account for explicitly included and excluded chats, conversation type and folder rules. If refresh fails, the last retrieved list is shown with an error message.

To delete a folder, select it and click Delete folder. Confirmation applies to the selected account's folder. The folder is deleted, but all chats, history and group memberships remain, including for folders added by link. The current folder version is checked before the request, and the result is checked again afterward. If the folder changed in another client, fresh confirmation is required. If the result is unknown, refresh the list first.

History loading is set to 1-200 messages per request. Search, starred chats and drafts are available. Viewing history alone does not mark messages as read; a separate button marks them as read.

Outgoing text is limited to 4096 UTF-16 units. You can reply to messages, copy usernames and delete a private conversation for your own account. Conversation deletion is unavailable for groups, channels and Saved Messages. Sending to groups and channels depends on account permissions.

Preview of supported images and audio is limited to 8 MB. Media loads on click. A hidden forward requires a link to a public post such as https://t.me/channel/123. Translating a draft does not send it automatically.

If the send result is unknown, resending is blocked until history is checked and the connection is restarted. Stopping clears accounts, folders, conversations and loaded media from the workspace. Account selection, starred chats and drafts are saved locally; Telegram history is not deleted.

Text randomizer

A local tool that does not need accounts, Telegram or an AI key. Enter a template, check the combination count, generate a random variant and copy or save the result to TXT.

{Hello|Good afternoon}, {colleagues|friends}!
{New {text|variant}|Another wording}

Variant groups use braces and the | separator. For literal special characters, use \{, \}, \| and \\. Nested groups are supported, but every opening brace must be closed.

Template limit: 100000 characters; depth: 32; alternatives per group: 128. Replacement masks: up to 10000 characters and 64 rules. Built-in Russian/English masks replace similar-looking characters; a custom mask lets you define your own groups. Replacement applies to the template and does not reprocess characters already inserted.

The combination count is not a guarantee of that many distinct texts: identical branches may produce duplicates. Repeated generation may also return the same result.

Telegram Premium

1. Select one account. If an active subscription is confirmed, another purchase does not start.
2. Click Get price. The application retrieves a new invoice from PremiumBot.
3. Check the account, purchase title, amount, currency, provider and terms. Select a saved card and enter CVV.
4. Confirm the payment terms. If required, complete additional confirmation in the bank/provider payment window.
5. Wait for confirmation of the original receipt. Separately check the result of the request to disable renewal.

The price comes from the current invoice; the application has no fixed price. Changing accounts resets the prepared invoice and CVV. Saved cards are displayed masked and protected by local Windows encryption; CVV is not saved. Access to local protected storage may differ after moving to another system.

Payment confirmed and Renewal disabled are different results. A failure to disable renewal does not cancel an already completed payment. After restart, an unfinished operation is restored for verification; explicitly stopping it preserves a paused state.

Reauthorization

1. Select source accounts and a separate folder for new sessions.
2. Set delays and threads. This form allows 1-5 threads and delays of 0-3600 seconds.
3. Separately choose whether to terminate other sessions, sign out of the source session and set a new 2FA password. Do not assume these actions are mandatory by default.
4. Start and review the outcome of each stage, the new files folder and errors.

New authorization is created through the active source session. If 2FA is enabled, the correct current password is required. Telegram may prevent a recently created session from terminating other sessions; this does not justify treating all stages as completed.

The source session is preserved unless the corresponding sign-out is selected and confirmed. For a partial result, check that a new working file pair exists before deleting the originals. Cancellation waits for clients to disconnect and sessions to be released.

Session duplicator

1. Select source accounts and a separate destination folder.
2. Choose code retrieval from the source session or QR confirmation by the source account.
3. Select a preset device profile or fill in all custom profile fields; enter a custom API pair only as a complete pair.
4. Start and check the new authorization result.

The duplicator creates an additional authorization while preserving the source. SMS in the form means retrieving a code from the source account's Telegram service chat 777000: receiving carrier SMS is not implemented. QR does not require manual scanning if the source account can confirm sign-in.

Parameters

Shadow sessions

This feature does not make an active authorization invisible to Telegram. Activation signs out of the current session and saves a recovery token in encrypted Windows storage. Deactivation attempts to restore sign-in using that token.

1. Select accounts and a mode.
2. If 2FA is enabled, make sure the current password is saved in JSON.
3. Read the sign-out confirmation and start.
4. To restore access, use the reverse mode and check each account's outcome.

Parameters

Converters, HEX and account discovery

tdata to session + JSON

1. Place the source tdata directories in the input folder using the supported structure.
2. Select/check the detected sources and start conversion.
3. Check the report and the file pairs created in session. Duplicate keys and existing files must not be counted as a new import.

The local tdata encryption password and the Telegram cloud 2FA password are different values. Damaged tdata or tdata protected in an unsupported way requires a valid source, not manual key changes.

session + JSON to tdata

1. Select current accounts using the selection button; no separate list scan is needed.
2. Select the destination folder. An empty field uses the standard tdata folder.
3. Choose whether to use the current authorization or create a new one.
4. Enter the required device/API settings and start; check the actual files created.

Exporting the current authorization with a valid Telegram ID can run without a network or proxy. If the ID is missing, account data must be retrieved. Creating a new authorization requires a connection, access and, if needed, the current 2FA password. The general thread setting is used up to 32; the destination directory must not overlap with source sessions or application resources.

HEX import

Use the record format offered by the form, with auth_key_hex, dc_id and phone number. The key must contain 512 hexadecimal characters, and dc_id must be 1-5. This is an authorization secret: do not send it to a group chat or support. Invalid rows and duplicate keys are counted separately.

tdata/session discovery

Select a source folder for recursive scanning. Do not use the application's own data directory as a source for reimporting. Preview the results, then copy/convert. Inaccessible folders and duplicates appear in the results; finding nothing in an inaccessible folder does not mean it contains no files.

Exporting accounts

1. Select the required accounts in the export module.
2. Set the batch size and available packaging options.
3. Create archives, then check the number of exported accounts and errors.
4. Open the specified output folder and check the contents before sharing.

Export copies account data into prepared archives and does not confirm their current Telegram status. The session and JSON pair provides access to the account, and JSON may contain the 2FA password and proxy. Share an archive only with its intended recipient; deleting a local archive does not revoke the session.

Views through proxies

1. Add public channel or individual post links, or a TXT file.
2. Check the shared proxy pool; Telegram accounts are not selected here.
3. Set request cycles, the number of recent posts and pauses.
4. Start and review request statuses in the report.

The module accesses Telegram's public widget pages. A confirmed HTTP request does not guarantee a view counter increase. Private invitations are not supported. A rate-limit response ends the task without switching proxies to bypass the restriction.

Parameters

Proxy scraper and country filter

1. Choose a protocol: SOCKS5 or HTTP from those available in the form.
2. Select several countries if needed. Search accepts a name or code; selecting all matches and resetting are available.
3. Set the target number of working proxies, maximum latency and concurrency.
4. Decide whether to add results to the shared pool, then start.
5. Check the log and open the output folder.

When filtering, unknown countries are excluded. If the geolocation database is unavailable, the filter is not silently disabled: fix the error or explicitly change your selection. Locally cached DB-IP Country Lite is used; the source is shown in the interface.

Public source availability and the quality of found proxies vary. Results may fall short of the target; a check at collection time does not guarantee long-term operation or suitability for a particular account.

Temporary email

1. Create a mailbox in Temporary email.
2. Copy the address and check for the successful-copy message.
3. Refresh the inbox and open a message.
4. Delete the mailbox only after confirming that its messages are no longer needed.

The external mail.tm service is used. Its domains, limits and availability are outside the application's control. Creating a mailbox and saving locally are separate steps: if the service created a mailbox but the save failed, read the message before creating another.

Email content opens in an isolated view; an unknown error does not mean the mailbox is empty. Refreshing and deletion require a valid service state. A temporary mailbox does not replace reliable email for recovering important accounts.

AI: auto-replies, advertising and profiles

AI auto-responder

1. Enter your OpenRouter key in Settings and save.
2. Set reply instructions, select accounts and allowed dialog types.
3. Set the delay, simulated reading/typing, per-user cooldown and maximum replies per minute.
4. Start; to release a session, stop the corresponding account and wait for completion.

The per-user cooldown is 5-600 seconds; the reply limit is 1-60 per minute per account. Group replies are enabled separately. The session lock remains while the auto-responder runs; closing the application window stops it.

Incoming message text needed to generate a reply is sent to an external AI service. API errors, an exhausted balance or request limits may prevent a reply from being generated. PeerFlood stops the affected work and is not resolved by a brief pause.

Ad copy generator

Enter a description, select a style and language, and optionally a contact. Generate the text, check its facts and copy the result. The generator creates text but does not start a messaging campaign.

AI for profiles

Bulk operations offer name, username and bio generation, and gender estimation by name. A generated username may already be taken; selection mode retries within the configured limit. Manual modes do not require an AI key.

General settings

Click Save after making changes. If writing fails, do not consider the new settings saved. The button to open this documentation is beside it.

Files, data and backups

SCARP_DATA_DIR, if used, changes the user data directory. To back up, fully close the application and save this entire directory along with source files and results located in other folders.

Account JSON

The current API pair format is app_id/app_hash. A valid api_id/api_hash pair is also accepted and normalized; pairs are not mixed. A complete canonical pair takes precedence when present. Invalid JSON is not overwritten by an individual change, preserving the other fields.

Do not publish .session, auth_key, twoFA, proxy credentials or API keys. Locally encrypted payment details and Windows tokens may be bound to the current user/system and may not open after simply copying them to another computer.

Message and error reference

Enter text from a notification, log or report. The reference explains the cause and next step; an error missing from the list does not change the task's actual result.

Frequently asked questions

Support

Support and license questions: @scarrytraff. Community: @scarrysoft. Version changes: release history.

Provide the version from Miscellaneous, module name, sequence of actions and exact error text. License issues may require the HWID from the activation window. For a task, attach its result or a screenshot with personal information hidden.

Do not send your license key, 2FA password, full card details, proxy password, auth_key or authorization files. Use anonymized data to describe a reproducible problem.