BabianNest / docs

Fake Binance App vs. the Real One: Icon, Developer, and Permission Differences

A real Binance app and a clone can be told apart on five hard criteria: icon detail, developer attribution, requested permissions, package size, and signature fingerprint. This article lays out a side-by-side checklist for each criterion, plus a two-round verification process to run before and after installing.

You've downloaded a "Binance app" and you're not sure if it's real — how do you actually check? To answer the headline up front: a real Binance app can be verified against a clone on five hard criteria — icon detail, developer attribution, requested permissions, package size, and signature fingerprint — and if any single one fails the check, don't use it. The safest download path is through the Official Binance App entry point on the Binance official website. Below is the comparison checklist for each criterion, along with a two-round verification process to run before and after installing.

The Short Version: 5 Comparison Criteria

Criterion What the real app looks like
Icon Black Binance geometric logo on a yellow background, no text, no decoration
Developer Binance Holdings Limited
Permissions 5 core permissions: network/camera/storage/notifications/biometrics
Package size Android 180-220 MB
Signature Matches the SHA-256 fingerprint officially published by Binance

If even one of these fails, it's not the genuine app.

Criterion 1: Icon

A lot of people assume that if the icon "looks about right," it must be real — but a clone's icon can also "look about right." The differences show up in the details.

What a Genuine Binance Android Icon Looks Like

  • Shape: rounded square (Android) or circle (iOS adaptive icon style)
  • Primary color: yellow background, #F0B90B (Binance's brand color)
  • Logo: a black, four-piece angled geometric shape (four diamonds arranged together)
  • No app name text — the icon itself contains only the logo
  • High resolution, with sharp, crisp edges

Common Flaws in Clone Icons

Clone icon feature
Off-color (orange or yellow-green)
Mismatched logo proportions (diamonds of uneven size)
Added text like "Binance" / "币安" / "BNB"
Added decorative elements (crown / flag / flame)
Low resolution (blurry or jagged edges)
Added badge like "Pro" / "Plus" / "VIP"

On iOS

The icon shape on iOS is determined by the system (rounded square), but the primary color and logo should still match. On iOS, clones commonly add a "Pro" badge or show an off-color rendering.

Criterion 2: Developer Attribution

This is one of the hardest, most reliable ways to tell real from fake.

Android (App Store Listing)

The "Developer" or "Offered by" field on the store listing page must read exactly:

Binance Holdings Limited

Or the shortened form Binance (this varies slightly by channel, but it must always include the core word "Binance" and carry no other suffix).

iOS (App Store)

At the bottom of the App Store listing page, the "Information" card's "Seller" field must read exactly:

Binance Holdings Limited

Complete, with no prefix or suffix attached.

Common Fake Developer Names

Fake name The trick
Binance Asia Adds a region
Binance China Adds a region
Binance Pro Adds a product suffix
Binance Plus Adds a product suffix
Binance Tech Adds "Tech"
BNC Inc Disguised abbreviation
Crypto Trade Unrelated to Binance

Only accept the exact, complete field "Binance Holdings Limited" — even a single-character difference means it's fake.

Criterion 3: Requested Permissions

Real and fake apps differ sharply here — clones almost always request excessive permissions.

Permissions the Real Binance App Requests

Permission Purpose
Network access API communication
Camera Taking KYC document photos, scanning QR codes
Storage read/write Saving screenshots, reports
Notifications Market alerts, login alerts
Biometrics (fingerprint/face) Unlocking the app
Location (optional) Certain compliance requirements

That's the complete list — any other permission is a red flag.

Excessive Permissions Common to Clones

Suspicious permission Clones request it, the real app doesn't
Read contacts ✗ Real app doesn't need it
Read SMS ✗ Real app doesn't need it (2FA uses an Authenticator app)
Read call log ✗ Real app doesn't need it
Make phone calls ✗ Real app doesn't need it
Device administrator access ✗ Real app doesn't need it (this is the most dangerous one)
Accessibility service ✗ Real app doesn't need it (one of the most dangerous)
Auto-start + background persistence ✗ Real app doesn't need it
Install other apps ✗ Real app doesn't need it
Screen recording ✗ Real app doesn't need it

If you see any one of "read SMS + accessibility service + device administrator," uninstall immediately — that combination lets a trojan read your 2FA text messages, auto-confirm withdrawals, and resist being uninstalled.

Criterion 4: Package Size

The genuine app's size falls within a stable, predictable range.

Genuine Binance APK Size

Form Size range (as of April 2026)
Full APK About 180-220 MB
Incremental update About 30-60 MB
Google Play split package Similar total size, split across multiple APKs

On iOS, package size is managed automatically by the App Store — check the "Size" field on the App Store listing page. It's roughly 300-400 MB (larger than Android due to bundled multilingual resources and iOS-specific assets).

Abnormal Clone Package Sizes

Clone type Size
"Lite version" / "Speed version" 5-30 MB (actually just a shell)
Repackaged bundle (with a backdoor) 250-400 MB (bundled with a malicious SDK)
Middleman shell package 50-80 MB (remotely loads the real interface)

"Binance Speed Edition," "Binance Lite Edition" — all of these are fake. There is no such official version.

Criterion 5: Signature Fingerprint

The hardest, most conclusive criterion — the APK's digital signature.

How to Verify the Signature

On Android

apksigner verify --print-certs binance.apk

Or use a tool like ApkTool or APK Analyzer to check the SHA-256 certificate fingerprint inside META-INF/CERT.RSA.

What a Genuine Binance Signature Looks Like

  • Signed with the same developer certificate (the private key held by Binance Holdings Limited)
  • A fixed SHA-256 fingerprint value
  • Consistent signature across historical versions (overwrite installs don't throw an error)

The exact fingerprint value can change over time as Binance updates it (in the rare case Binance rotates certificates, they publish an announcement) — check the latest value in the Binance Official Site's Help Center, or in the APK package name verification article.

What a Clone Signature Looks Like

  • A self-signed certificate (anyone can generate one)
  • SHA-256 doesn't match the official value
  • Attempting to overwrite-install the real Binance app on top of it produces a "signature mismatch" error

On iOS

iOS uses Apple's code signing, and every app listed on the App Store passes through Apple's signature verification — in theory, an app downloaded from the App Store shouldn't have a signature-spoofing problem — but you still need to confirm the developer attribution reads Binance Holdings Limited.

Combined 5-Criteria Comparison Table

Criterion Genuine Common clone traits
Icon Plain black logo on yellow, no text Added text/badges/off-color
Developer Binance Holdings Limited Suffixed with Asia/China/Pro
Package name (Android) com.binance.dev Various altered variants
Permissions 5-6 core permissions Adds SMS/accessibility/device admin
Package size 180-220 MB Unusually small or large
Signature Official SHA-256 Arbitrary self-signed

All 5 criteria match → genuine app. Any 1 doesn't match → don't install it.

Verification Process Before Installing

Once you've downloaded a "Binance" installer, don't install it yet — run through this first:

Step 1: Verify the Source

Source Likelihood of being genuine
binance.com download page Genuine
Google Play (Binance Holdings Limited) Genuine
App Store (Binance Holdings Limited) Genuine
Domestic Android app stores (Huawei/Xiaomi/OPPO/vivo, etc.) Fake
Shared in a QQ group / Telegram group Fake
Third-party APK sites (other than well-known ones like APK Mirror) Needs verification

Step 2: Check the Package Size

Check the APK's size in your file manager. If it doesn't fall within the 180-220 MB range, delete it immediately.

Step 3: Check the Package Name With ApkTool / APK Analyzer

Package name = com.binance.dev → move on to the next step.

Step 4: Check the Signature With apksigner

apksigner verify --print-certs xxx.apk

If the SHA-256 fingerprint matches the officially published value → move on to the next step.

Step 5: Install

Only install once all 5 checks pass.

Verification Process After Installing

Once it's installed, run through this checklist again:

Step 1: Check the Icon

Look at the home screen icon's color, logo proportions, and whether any text or badge has been added.

Step 2: Check the App Info

Settings → App Management → find Binance → App Details:

  • Package name: com.binance.dev
  • Developer: Binance Holdings Limited
  • Permission list: confirm there's nothing abnormal

Step 3: Watch Closely on First Launch

If the first launch pops up a request to "enable accessibility service," "become device administrator," or "grant SMS permission" — close the app and uninstall it immediately. This is a clone.

Step 4: Confirm Once More Before Logging In

Before logging in, check the version number shown under "Settings → About" in the app, and the API endpoint if it's visible. The real app's API endpoint is api.binance.com.

Things Not to Do

  • Don't install "Binance" from a domestic Android app store (they're all fake)
  • Don't install a package shared through a QQ or Telegram group link
  • Don't install variant packages like "Binance Speed Edition" / "Binance Lite Edition" / "Binance Pro"
  • Don't assume it's safe just because "it lets me log in" (that's exactly how a clone tricks you)
  • Don't enter your password or 2FA code into a suspected clone app

What to Do If You've Already Installed a Clone

Step 1: Uninstall Immediately

Settings → Apps → long-press the icon → Uninstall. Force-remove it.

Step 2: Run a Security Scan and Reboot

Some clone packages bundle background SDKs that can leave residue even after the main app is removed. Reboot the device and run a full scan with a security app.

Step 3: Check Your Account on the Real Official Site

Open your browser and manually type in binance.com. Change your password, reset 2FA, and review your login history and withdrawal history. See telling the real site from a fake one for more.

Step 4: Reinstall the Genuine App

Download from binance.com → run the 5-criteria check → install. See app downloads for all five platforms for more.

Step 5: Check Periodically

Going forward, verify the signature every time you update — make it a habit.

FAQ

Q: I downloaded mine from the official Binance website — do I still need to verify it? A: It's worth doing once. Downloading from the official site is the safest channel, but in rare cases a browser or download manager can be hijacked. Running through the 5-criteria check as a habit doesn't hurt.

Q: Do I need to verify an app downloaded from the App Store on iOS? A: Risk is lower on iOS since the App Store enforces Apple's signature review. But you still need to confirm the developer listed on the App Store page is Binance Holdings Limited — a common trick for iOS clones is registering a developer name that closely resembles the real one.

Q: The "dev" suffix in the package name com.binance.dev looks strange — is that a development build? A: No. That's simply the package name format Binance chose — every official production version of the real Binance app uses this exact package name, regardless of version.

Q: How do I verify an APK a friend sent me? A: Run all 5 checks on it. The simplest, most foolproof approach is not to use the one your friend sent — just download it yourself from binance.com. An APK is just software; re-downloading costs nothing.

Q: A clone app lets me log in successfully — why? A: A clone's "login" actually just sends your password to the phishing operator's backend — so "successful login" is an illusion, and in reality, your password has already been intercepted. It appears to work, but you've already been compromised behind the scenes.

Q: What happens if I overwrite-install the real Binance app on top of a clone? A: You'll get a "signature mismatch" error and the install will fail. That's actually useful information — if installing the genuine official APK over your existing app throws a signature mismatch, it confirms the app you had installed was fake.

Q: What does the Android warning "This app may harm your device" mean? A: That's a Google Play Protect warning, shown for APKs that are unverified or from an unknown source. If an APK downloaded from binance.com triggers this warning, you can choose "Install anyway" — but run the 5-criteria check first to confirm it's genuine.

Q: The app crashes or the login page won't open after installing — is that a sign it's a clone? A: Not necessarily. It could be a network issue or a version compatibility issue. Run the 5-criteria check first; if it's confirmed genuine but still crashing, check the Install Issues category for solutions.