2026 Binance App Authenticity Guide: Ten-Point Checklist for Package, Signature, Bundle ID, and UI

Ten-point checklist for verifying the official Binance app: Android package com.binance.dev, iOS Bundle ID com.binance.ios, SHA-256 signature, developer field, splash screen, UI details, and update log side by side.

Published on 2026-07-12 · About 26 min · Anti-Phishing

One-sentence answer: The three golden fields for judging whether a Binance app is genuine are the Android package com.binance.dev, the iOS Bundle ID com.binance.ios, and the Android APK signature SHA-256. If any of those three does not match the official published values, the package is a phishing package, no matter how closely its UI mimics the official app. To pull the fully verified package, head straight to the Download Page for the Official Binance App, or start on the Binance Official Site to register first and then follow the in-account download link.

BianIO writes for technically savvy users who take installation security seriously. This piece breaks down "real app vs. phishing package" across ten layers into a copyable verification checklist that you can go through in order.

Three Core Fields: Package Name / Bundle ID / Signature

These three fields are invariants; the official team never changes them. Version numbers change, the UI is redesigned, and icons are refreshed, but the package name, Bundle ID, and signature never move.

Field Official Value Extraction Command Common Phishing Variants
Android package com.binance.dev aapt dump badging Binance.apk com.binance.cn / com.binancecn.dev / com.binance.pro
iOS Bundle ID com.binance.ios Tail of App Store URL, or ideviceinstaller com.binance.us / com.binance.hk
Android signature SHA-256 Published 64-char hex on official site apksigner verify --print-certs Binance.apk Any mismatched value
Signature algorithm SHA256withRSA Same as above MD5withRSA (legacy)
Android Min SDK API 24 (Android 7) aapt dump badging Binance.apk API 21/22 (too low)

A: The signature SHA-256 is unforgeable — forgery would require Binance's official signing key. Any tutorial claiming to "solve the signature mismatch" is guiding you to install a phishing package. Ignore it.

Why the Package Name Can Be Faked While the UI Looks Identical

Android lets developers pick any package name freely; a phishing package only has to set the package to com.binance.cn and users who skip verification never notice. The UI, icon, and splash screen can be reproduced pixel-perfect — the only real defense is package name plus signature.

Verification Points on iOS

On iOS, the Bundle ID cannot be viewed inside the app; you have to check the App Store detail page URL or run ideviceinstaller -l on macOS to inspect installed apps. The iOS App Store also carries knock-off packages — for instance, com.binance.us is Binance's US-specific app, not suitable for non-US users. When choosing, confirm the developer field reads "Binance Ltd".

Developer Field and Store Metadata Checks

Whether Play Store or App Store, the developer field is an important line of defense.

  • Play Store developer: Should read Binance
  • App Store developer: Should read Binance Ltd
  • App Store price: Should be free
  • App Store in-app purchases: Should be none (Binance has no in-app purchases)
  • Age rating: Play 17+, App Store 17+
  • Release history: Binance Android first launched November 2017; iOS launched January 2018

A: Any store app labeled "Binance Pro", "Binance Exchange", "Binance China", or "Binance International" is almost certainly a phishing package. The real app is called simply "Binance" in the store — Chinese users see the English name.

Play Store Is Unreachable in Mainland China

Mainland China cannot access Play Store, so mainland Android users must always sideload APKs. This objective reality is heavily exploited by phishing operators: they distribute phishing packages under the guise of "Play Store APK on your behalf", accounting for over 60% of phishing cases in mainland China.

App Store Region-Switch Notes

iOS requires an overseas Apple ID (US and Japan regions are the most common) to download Binance. After switching region, search Binance in the App Store and confirm the developer field reads Binance Ltd. If multiple "Binance" results appear, pick the one with the highest download count, the most reviews, and the correct developer field.

Splash / Icon / Watermark Details

Visual details of the latest official release as of July 2026:

  1. Icon: Gold rhombus B on a black background; four smaller rhombuses form the large B. Common phishing tells include fuzzy rhombus edges and gold that leans too yellow or too red.
  2. Splash screen: Single Binance wordmark plus a loading ring; no promotional copy. Phishing packages often show "lucky draw" or "top-up bonus" banners.
  3. Login page watermark: None. Phishing packages often include QR code watermarks or Telegram support watermarks.
  4. Home screen top-left corner: Officially an asset/trading toggle icon. Phishing packages often replace it with a "Rewards" or "Events" entry.
  5. Bottom navigation bar: Five official items (Home / Markets / Trade / Futures / Wallet). Phishing packages often include six items or add a "Customer support" tab.
  6. Dark mode toggle: Official path is Profile, Settings, Display. Phishing packages have anomalous paths.
  7. Language switcher: Official app supports 40+ languages. Phishing packages usually have shorter language lists.

A: UI details are not decisive proof but serve as an early-warning signal — once you spot anomalies, immediately fall back to package name and signature verification.

Risk warning: Do not enter 2FA keys or private keys inside an app whose signature you have not verified. The most typical phishing attack is "induce input of 2FA backup code, sync to the attacker's server, attacker hijacks the account on the real site".

Identifying via Update History

The official Binance app updates roughly every two weeks with a standard changelog format: bug fixes, performance improvements, new features. Phishing packages exhibit anomalies in their update history: gaps followed by a sudden update after six months of silence, changelogs full of marketing copy, or version numbers that skip (say 2.60 straight to 2.99).

Permission List Comparison

The official Android app requests around 20 permissions: network, camera (for QR scan), biometrics, storage, and vibration. Bloated permissions common in phishing packages: accessibility service, screen recording, notification read, contacts, SMS read, always-on location. Any one of these appearing means it is a phishing package, without exception.

Recommended Full Verification Flow

Complete the following eight steps in order:

  1. Download source: Only from binance.com/download or the verified Download Page
  2. File hash: After download, compute SHA-256 and align it with the officially published file hash
  3. Signature verification: Use apksigner verify --print-certs to inspect the certificate SHA-256
  4. Package name check: Use aapt dump badging to extract the package and align it with com.binance.dev
  5. Post-install inspection: Immediately after install, check the permission list; deny any anomalies without question
  6. First launch: Do not log in or register — switch language, toggle dark mode, and observe the UI
  7. Network capture (optional): Use mitmproxy to observe API domains; official domains are fixed to api.binance.com and its subdomains
  8. Login: After verification passes, log in and enable TOTP 2FA (Aegis recommended); refuse SMS 2FA

A: The full check takes about 5-10 minutes, and this is the minimum cost any user holding crypto assets should be willing to pay.

For a step-by-step end-to-end walk-through, consult the Binance Official Site entry tutorial to identify the correct entry, then return to the Binance Official Site for registration and download.

Network Request Identification

Primary domains for the official app's network traffic:

  • api.binance.com (main API)
  • www.binance.com (web version)
  • fapi.binance.com (USDT-M futures API)
  • dapi.binance.com (coin-margined futures API)
  • data-api.binance.vision (market data)

Anomalous domains common in phishing packages: any request outside the binance.com or binance.vision top-level domain is a danger signal. Subdomains may vary but the top-level domain is invariant.

Common Phishing Distribution Channels

  • Telegram groups labeled "Binance China Edition": nearly 100% phishing
  • WeChat groups labeled "Binance iOS region-switch-free": no such iOS technology exists — always phishing
  • Short-video platforms labeled "Binance Accelerated": no official "accelerated" edition exists
  • Forums labeled "Binance Pro cracked": the concept of a cracked version does not exist for a compliant exchange app
  • SMS links like "Your Binance account has irregularities, verify immediately": 99% phishing SMS

FAQ

Q1: The signature does not match but the version number does — is it real?

A: It is fake. Signature is the sole anti-forgery credential; version numbers can be forged freely. Uninstall any APK whose signature does not match and redownload.

Q2: Can iOS be verified via SHA-256?

A: iOS IPAs also carry signatures, but App Store-distributed apps are signed by Apple and users do not have to manually verify. Just confirm the Bundle ID and that the developer field reads Binance Ltd. The iOS defense line is App Store review, which is why iOS phishing cases are more than 90% rarer than Android.

Q3: Are the Play Store and official-site APK signatures the same?

A: Yes. The official Play Store version and the official-site APK use the same signing key; the SHA-256 is identical. Any mismatch signals a suspect source.

Q4: Is an accessibility permission request always a phishing package?

A: Yes. The official Binance app never requests accessibility, screen recording, call recording, or SMS read permissions. Any one of these appearing means it is a phishing package.

Q5: Are older APK versions still safe to use?

A: Not recommended. Older versions may contain known security vulnerabilities. Even if they were the official version at the time, upgrading to the latest release is advised. The signature is still official, but functionality and security are outdated.

Q6: Can I use an APK someone else copied from their phone?

A: Technically yes, but you must perform full signature verification. There is no fundamental security difference between devices — as long as the signature SHA-256 matches the official value, it is the official APK.

Q7: What if my phone was tricked into installing a phishing package?

A: Execute three steps immediately. First, uninstall the phishing app. Second, log into Binance from another device and revoke all API keys and device authorizations. Third, change the password and reset 2FA. Fourth, if the 2FA backup codes may already be exposed, contact official support to freeze the account.

Q8: Will Binance officially notify me to download the app via SMS or email?

A: The official team never proactively notifies you to download the app via SMS or email. Any SMS or email claiming that "Binance is warning you to download the latest version to avoid account suspension" is phishing. Official notifications happen inside the app only.

Final Anti-Phishing Principles

Three cast-iron rules: only pull packages from the official site or the verified Download Page, always verify the signature SHA-256, and uninstall immediately at any abnormal permission request. Hold these three lines and phishing packages essentially cannot land.

Comprehensive checklist:

  1. Download source limited to the official site or Download Page
  2. Package name fixed at com.binance.dev
  3. iOS Bundle ID fixed at com.binance.ios
  4. Developer field fixed at Binance / Binance Ltd
  5. Signature SHA-256 matches the official published value character-for-character
  6. Permission list free of accessibility / screen recording / SMS / contacts
  7. UI free of ad banners and promotional watermarks
  8. Network requests limited to binance.com / binance.vision
  9. Update notes follow a standard changelog format
  10. 2FA prefers TOTP (Aegis/Authy); refuse SMS 2FA

Published on 2026-07-12, next review scheduled for 2026-10-12.