Security audit

Conclusion for client information

1. Authentication security

Login is only possible with simultaneous verification of your username, password, and two-factor authentication (2FA). Passwords and 2FA data are not stored in cleartext (recoverable). If multiple unsuccessful login attempts occur, access is temporarily restricted and additional confirmation is requested. All login attempts are recorded with sensitive data masked. The session remains valid until the browser is closed. Registration is protected by user authentication.

2. Cryptocurrency wallet security

Wallet private keys are not stored in the app. When creating a wallet, the user receives and stores a secure backup copy; to withdraw funds, they must present this copy and confirm the action via 2FA. Before a withdrawal, the key is verified to match the wallet address. Withdrawal frequency limits and temporary blocking are in place in the event of suspicious activity. A minimum withdrawal amount can be set, as well as general or personal withdrawal limits, if needed.

3. Supported networks

USDT is supported on the TRC20, BEP20, and TON networks. Requests for other networks are not accepted.

4. General protection

Critical actions are protected against request forgery. Standard headers and settings are used to mitigate the risks of unauthorized access, interface embedding on third-party sites, and content type spoofing. Incoming data is validated and restricted before use.

5. Comparison with similar solutions

Based on a comparison with a number of well-known platforms in the same class (exchange and non-exchange services, wallets, and digital asset platforms): the level of login protection (multifactor support, limited attempts, storage of account and 2FA data without the possibility of restoring original values) meets or exceeds the typical level for the industry; the elimination of private key storage in the application is consistent with the approach of non-custodial solutions and increases user control over funds; mandatory 2FA for withdrawals corresponds to the practice of the most strict services; restrictions on the frequency of transactions and blocking in case of verification failures are typical for financial and crypto services; support for a limited set of networks reduces the attack surface compared to platforms with a larger number of networks; the use of standard web application security mechanisms meets expectations for similar products. Overall, the measures applied meet or exceed the typical level of maturity of similar well-known solutions in terms of login, key management, and withdrawal operations.

6. Infrastructure and runtime environment

In October 2026, an unscheduled runtime update was performed on production servers due to published critical vulnerabilities in the PHP interpreter (PHP2Shell family), affecting the runtime and not just the application code. The latest official distribution security packages were installed, web stack workflows were restarted after the update, and compliance with the patched builds was verified. Thus, at the time of the review, the known class of risks of remote code execution and memory disclosure at the runtime level was closed. A practice of promptly responding to critical advisories without waiting for the scheduled quarterly cycle is in place.

Conclusion

The audit (revised on November 5, 2026) confirmed that the application implements multi-factor authentication, eliminates the storage of private wallet keys, requires mandatory two-factor authentication and withdrawal restrictions, supports only specific networks (TRC20, BEP20, TON), and adheres to generally accepted web application security measures. Since the previous audit (August 28, 2026), two-factor authentication data storage has been strengthened: like passwords, they are not stored in cleartext (recoverable), mitigating the consequences of a credential storage compromise. Additionally, in October 2026, a critical PHP runtime update was promptly applied to the servers according to the published PHP2Shell advisory, followed by a review and restart of workflows, mitigating the corresponding risk at the infrastructure level. Compared to current industry benchmarks as of 2026 (non-custodial practices, multi-factor control, attack surface limitation, and timely runtime patching), the measures applied meet or exceed the typical maturity level of similar solutions. This document is prepared for client information purposes only and does not constitute a formal certification (CCSS, ISO 27001, etc.) and does not disclose information that constitutes a trade secret or could facilitate unauthorized access.

The conclusion is subject to mandatory revision quarterly and in the event of significant changes in the application or infrastructure.

This conclusion is based on an analysis of the application code, verification of measures on the server infrastructure, comparison with industry practices, and artificial intelligence methods.

Signature: Internal Security Audit Team (using advanced AI models)
Date: 05.11.2026
Review frequency: quarterly