How Do You Check the Binance APK Package Name? Is com.binance.dev Real?
The official Binance APK package name is com.binance.dev, and the file is roughly 85MB. This guide covers 4 ways to verify the package name, how to check the signature, and what to do if the package name doesn't match.
The official Binance Android APK's package name is com.binance.dev — this is the single most reliable fingerprint for telling a real APK from a fake one. To answer the headline directly: the package name com.binance.dev is genuine, the file is around 85MB, and it ships as a single APK (not a split APK). Any APK with a different package name should never be installed. This guide walks through 4 ways to verify the package name, how to check the signature, and what to do if something doesn't match.
If you've just downloaded the APK from the Binance Official Site, verify the package name before you install it.
Key fingerprints of the official Binance APK
| Field | Value |
|---|---|
| Package name | com.binance.dev |
| App name | Binance |
| Developer | Binance Holdings Limited |
| File size | About 85MB (varies by 5-10MB between versions) |
| Package format | Single APK (not a split APK / xapk) |
| Minimum Android version | Android 8.0 (API 26) |
| Signing certificate fingerprint (SHA-256) | See below |
Delete immediately any APK where even one of these fields doesn't match.
4 ways to verify the package name
Method 1: Check after installing (easiest)
If you've already installed the APK on your phone:
| Android version | Path |
|---|---|
| Android 12+ | Settings → Apps → find Binance → App info → small text at the top reads "com.binance.dev" |
| Android 10-11 | Settings → Apps & notifications → App info → small text at the top |
| Older versions (< 10) | Settings → Apps → App details |
If what's shown isn't com.binance.dev, uninstall it right away.
Method 2: Inspect the APK file before installing (recommended)
After downloading the APK, verify it before you install:
Using a tool like APK Editor
Open the APK file with an APK inspection tool (APK Editor, APK Analyzer) on another phone or a computer. It will show you:
- AndroidManifest.xml → the package name
- The META-INF folder → the signing certificate
- The size of the resource files
Using the command line (on a computer)
If you have the Android SDK installed:
aapt dump badging Binance.apk | grep package
It should output:
package: name='com.binance.dev' versionCode='2840500' versionName='2.84.5'
Method 3: The phone's built-in "package details" screen
Some Android systems show package details before you actually install an APK. Tapping the APK file usually brings up an "Install app" dialog that shows:
- The app name
- The package name (shown on some brands, not on others)
- The source
- The size
- The permissions requested
If your phone's brand doesn't show the package name, fall back to Method 1 (check after installing).
Method 4: Use a security-scanning app
Some security apps (like 360 Security Guard or Tencent Mobile Manager) can scan an APK and display its package name along with a known-threat rating. But treat these apps' verdicts as a reference only — you still need to verify the package name yourself in the end.
Signing certificate verification
Package names are easy to fake, but a signing certificate is nearly impossible to forge. The official Binance APK's signing certificate has a unique SHA-256 fingerprint, and re-signing a counterfeit package changes that value.
How to check an APK's signature
After installing (needs root or developer tools)
keytool -list -printcert -jarfile Binance.apk
Or use an Android app like ApkSignatureViewer to view it directly.
Binance's official signing fingerprint
Because Binance rotates its certificates from time to time, the most accurate fingerprint is whatever Binance's official announcements state.
The safest approach is simply to download the APK straight from the official website, which saves you the trouble of verifying the signature yourself.
What a mismatched package name usually means
Case 1: The package name is com.binance.app or com.binance.client
This is 100% a counterfeit. Binance has never used either of these package names.
Case 2: The package name is com.binance.dev but the size is off
Possibilities:
- Too large (> 100MB): may be bundled with ad SDKs or malicious code
- Too small (< 50MB): may be a stub app that downloads the real code after launch (even more dangerous)
- Normal 80-95MB: most likely fine
Case 3: The package name is com.binance.us
This is Binance.US, a legitimate official build, but with limited functionality — it serves US users only, and accounts in mainland China get flagged by risk controls when they log in. Users outside the US should use com.binance.dev.
Case 4: The package name is something like app.binance.com.binance.dev
A common "double prefix" trick used by counterfeit packages. A legitimate package name never contains spaces, double prefixes, or special characters. Delete it immediately if you see this.
How to download and verify from the official site
Step 1: Visit the genuine official site
The only correct download entry point is the Binance Official Site, via "Download" in the top-right corner → Android.
Step 2: Download the APK
The file name is usually something like Binance_v2.84.5.apk. It downloads to your Download folder.
Step 3: Check the file size
Look at the downloaded APK's size in your file manager:
- It should be between 80-95MB
- If it's 5-10MB, it's fake (likely a broken download link)
- If it's 200MB+, it's fake (likely stuffed with malicious code)
Step 4: Verify the package name after installing
Check "App info" as described in Method 1, and confirm the package name is com.binance.dev.
If anything looks off at any step, uninstall immediately and re-download from the official site.
Common traits of counterfeit APKs
Here are the shared traits we've collected from counterfeit packages.
Trait 1: Odd suffixes on the package name
| Fake package name | The trick |
|---|---|
| com.binance.appcn | Adds "cn" to look like a China edition |
| com.binance.crypto | Adds "crypto" |
| com.binance.helper | Disguised as a "helper" tool |
| com.binance.china | Adds "china" |
| com.binance | Missing the ".dev" suffix |
Trait 2: Requests unusual permissions
Counterfeit packages often ask for:
- Contacts access (the official app never asks for this)
- SMS access (the official app never asks for this)
- Auto-start permission (the official app never asks for this)
- Background running (the official app never asks for this)
The official Binance app only needs notifications + camera + storage + network at launch.
Trait 3: Abnormal file size
- Too small (< 50MB): a stub package that downloads malicious code after launch
- Too large (> 120MB): may have embedded ad SDKs
- Normal: 80-95MB
Trait 4: Suspicious developer info
Check the "Developer" field on the app details screen:
- ✓ Real: Binance Holdings Limited
- ✗ Fake: "XX Studio", "XX Technology", "XX Financial Services"
Safety checklist before installing
Working through this checklist catches 95% of counterfeit packages:
| Check | Passing criteria |
|---|---|
| Download source | binance.com official site |
| File size | 80-95MB |
| Package name | com.binance.dev |
| App name | Binance (not "Binance Pro" or similar) |
| Developer | Binance Holdings Limited |
| Permissions requested | Notifications / camera / storage, no location / contacts |
| Can you log in after launch | Genuine only if it redirects to accounts.binance.com |
| "About" page in-app | Shows a version number that matches the official announcement |
Pass all 8 items and it's genuine; fail any one and it's fake.
Things you should never do
- ❌ Don't download the APK from a QQ group or Telegram group
- ❌ Don't download "Binance App" from Baidu Netdisk
- ❌ Don't use a third-party "lite version," "cracked version," or "VIP version"
- ❌ Don't skip a permission check just because it's "too much hassle"
- ❌ Don't enter your 2FA backup codes into a third-party site to "speed up verification"
FAQ
Q: After installing, the package name shows com.binance.dev, but it redirects to an unknown website after launch — is it genuine? A: This could be a DNS hijack. Close the app, restart your network connection, then relaunch. If it keeps redirecting to strange addresses, uninstall it immediately — it may be a counterfeit disguised with the real package name.
Q: Is the "Binance" package found in my phone brand's app store also com.binance.dev? A: A handful of official app stores (like the Hong Kong version of Samsung Galaxy Store) carry the genuine Binance app. But "Binance" on most third-party app stores is counterfeit. The safest route is always downloading from the official site.
Q: Can I trust version numbers other than v2.84.x? A: v2.84.x was the mainstream version as of April 2026, and it will keep updating. Any version number could be genuine — what matters is that it came from the official site. If the version number is something absurd like v9.9.9 or v100.0.0, it's 100% fake.
Q: What if a "risky app" warning pops up while installing the APK? A: Android shows this warning by default for any APK not sourced from the Play Store — it's standard system behavior, not a sign the APK itself is bad. Once you've verified the package name, you can safely dismiss the warning.
Q: Can I trust the Binance APK on APKMirror? A: APKMirror is a well-known APK mirror site, and the Binance APK there is usually genuine (mirrored directly from the official release). But you should always prefer the official site first, which saves you the verification hassle.
Q: Why is the package name .dev instead of .app?
A: com.binance.dev is the package name Binance's developers used early on, and it's stuck ever since. It functions as Binance's globally unique, trademark-level package name.
Q: Do I need to re-verify the package name after every update? A: In theory, checking every time is safest. But if you always download from the official site and always install as an in-place update (rather than uninstalling the old version first), the package name never changes, so you can skip this step.
Q: Can I check the package name with an ADB command?
A: Yes. Connect your phone to a computer via USB, enable USB debugging in Developer Options, then run: adb shell pm list packages | grep binance. If the output is package:com.binance.dev, it's genuine.