Audit name:
[PT] WhiteBIT | Android | Jul2026
Date:
Sep 2, 2026
Table of Content
Introduction
We express our gratitude to the WhiteBIT team for the collaborative engagement that enabled the execution of this Pentest.
Document | |
|---|---|
| Name | Pentest and Security Analysis Report for WhiteBIT |
| Approved By | Faizan Nehal |
| Website | https://whitebit.com, https://whitebit.com/ua |
| Changelog | 05/08/2026 - Preliminary Report |
| 09/09/2026 - Final Report | |
| Platform | Android |
| Tags | Pentest (Black-box) |
| Methodology | https://docs.hacken.io/methodologies/pentesting→ |
Document
- Name
- Pentest and Security Analysis Report for WhiteBIT
- Approved By
- Faizan Nehal
- Website
- https://whitebit.com, https://whitebit.com/ua
- Changelog
- 05/08/2026 - Preliminary Report
- 09/09/2026 - Final Report
- Platform
- Android
- Tags
- Pentest (Black-box)
Review Scope | |
|---|---|
| URL | https://play.google.com/store/apps/details?id=com.whitebit.android&hl=en→ |
| Version | 3.79.0 |
Review Scope
- Version
- 3.79.0
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
{FindingsVulnSeverityStatusTable}
System Overview
WhiteBIT Mobile Android application is a cryptocurrency exchange, providing users with the ability to buy, sell, store, and exchange cryptocurrencies, view balances, transaction history, and receive market notifications.
Core Features:
User registration, login, and identity verification (KYC/AML)
Viewing account balance and transaction history
Conducting trading operations (buy, sell, exchange)
Account transfers, deposits, and withdrawals
Security settings (2FA, PIN code, biometrics)
Push notifications for events (trading, security, balance updates)
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2026-1884 | App Lock Passcode Bypass | fixed | Medium | |
| F-2026-1884 | WebSocket Authorization Bypass via Unenforced API Key Permissions | fixed | Medium | |
| F-2026-1883 | App Updates Are Not Code-Signed Allowing Arbitrary Code Execution | fixed | Medium | |
| F-2026-1885 | Unhandled Exceptions Disclose Internal Database Error Information | fixed | Low | |
| F-2026-1884 | Lack of Input Validation in Branded QR Code Generation | fixed | Low | |
| F-2026-1884 | Overly Permissive CORS Policy on cc.whitebit.com | fixed | Low | |
| F-2026-1883 | Missing JWT Access Token Expiration | accepted | Observation | |
| F-2026-1883 | Missing Emulator and Root Detection | accepted | Observation | |
| F-2026-1883 | Missing SSL Pinning | accepted | Observation |
Appendix 1. Severity Definitions
Findings are categorized based on their potential impact and assigned a severity level using the Common Vulnerability Scoring System (CVSS) version 4.0: →
Severity | Description |
|---|---|
Critical | These issues present a major security vulnerability that poses a severe risk to the system. They require immediate attention and must be resolved to prevent a potential security breach or other significant harm. |
High | These issues present a significant risk to the system, but may not require immediate attention. They should be addressed in a timely manner to reduce the risk of the potential security breach. |
Medium | These issues present a moderate risk to the system and cannot have a great impact on its function. They should be addressed in a reasonable time frame, but may not require immediate attention. |
Low | These issues present no risk to the system and typically relate to the code quality problems or general recommendations. They do not require immediate attention and should be viewed as a minor recommendation. |
Severity
- Critical
Description
- These issues present a major security vulnerability that poses a severe risk to the system. They require immediate attention and must be resolved to prevent a potential security breach or other significant harm.
Severity
- High
Description
- These issues present a significant risk to the system, but may not require immediate attention. They should be addressed in a timely manner to reduce the risk of the potential security breach.
Severity
- Medium
Description
- These issues present a moderate risk to the system and cannot have a great impact on its function. They should be addressed in a reasonable time frame, but may not require immediate attention.
Severity
- Low
Description
- These issues present no risk to the system and typically relate to the code quality problems or general recommendations. They do not require immediate attention and should be viewed as a minor recommendation.
Appendix 2. Scope
The scope of the project includes the following:
Scope Details | |
|---|---|
| URL | https://play.google.com/store/apps/details?id=com.whitebit.android&hl=en→ |
| Version | 3.79.0 |
Scope Details
- Version
- 3.79.0
Assets in Scope
Appendix 3. Additional Valuables
Frameworks and Methodologies
This security assessment was conducted in alignment with recognised penetration testing standards, methodologies and guidelines, including the NIST SP 800-115 – Technical Guide to Information Security Testing and Assessment →, the Penetration Testing Execution Standard (PTES) →, and the OWASP Testing Guide →. These assets provide a structured foundation for planning, executing, and documenting technical evaluations such as vulnerability assessments, exploitation activities, and security code reviews. Hacken’s internal penetration testing methodology extends these principles to Web2 and Web3 environments to ensure consistency, repeatability, and verifiable outcomes.