BabianNest / docs

How to Verify a Binance APK Signature: Two Tools, Step by Step

The two most practical tools for verifying a Binance APK signature are apksigner (command line) and a signature-viewer app on Android. This guide covers the full apksigner commands, how to cross-check the signature fingerprint, and what to do when the signature changes across Binance APK versions.

The two most practical tools for verifying a Binance APK signature are apksigner (command line) and a signature-viewer app on Android. Short answer up front: with apksigner, one line — apksigner verify --print-certs Binance.apk — prints the certificate fingerprint (SHA-256); on your phone, an app like ApkSignatureViewer shows the same thing directly. Both tools should return the same result, and as long as the fingerprint matches the known official Binance fingerprint, the package is genuine.

Signature verification is the strongest way to tell a genuine APK from a fake one — a package name can be faked, but a signature is practically impossible to forge. Anyone repackaging the app has to re-sign it with their own key, which produces a completely different certificate fingerprint. This guide walks through the full steps for both tools and how to cross-check the fingerprint once you have it. If you just downloaded the APK from the Binance official website, you can run through this entire process for the strictest possible check.

Why signature verification beats package-name verification

Dimension Package name Signature
How easy to fake Easy (just edit the manifest) Extremely hard (requires the original private key)
Uniqueness One per app One set per developer (can include several)
How often it changes Rarely Occasionally rotated
Tooling required Low (just check app info) Medium (requires a tool)
Verification strength Weak Strong

Signature verification is the last and strongest gate in telling real from fake.

Tool 1: apksigner (command line, the most authoritative)

apksigner is Google's own tool bundled with the Android SDK — the most authoritative APK signature verification tool in the industry.

Getting apksigner set up

Method 1: Install Android Studio

Android Studio ships with apksigner, located at:

C:\Users\<you>\AppData\Local\Android\Sdk\build-tools\<version>\apksigner.bat

Or on Mac/Linux:

~/Library/Android/sdk/build-tools/<version>/apksigner

Method 2: Install just the build-tools

If you don't want to install the whole of Android Studio, you can download the command-line tools on their own:

  1. Download the command-line tools from the Android developer site
  2. After unzipping, use sdkmanager to install the build-tools
  3. apksigner will be under build-tools/<version>/

Command 1: Print the certificate fingerprint

The most commonly used command:

apksigner verify --print-certs Binance.apk

Sample output:

Signer #1 certificate DN: CN=Binance, O=Binance Holdings Limited
Signer #1 certificate SHA-256 digest: a1b2c3d4... (64 hex characters)
Signer #1 certificate SHA-1 digest: f1e2d3... (40 characters)
Signer #1 certificate MD5 digest: 1a2b3c... (32 characters)

Write down the SHA-256 fingerprint and cross-check it against Binance's official announcements or developer signature disclosure page.

Command 2: Verify signature validity only

apksigner verify Binance.apk

An output of Verifies means the signature is valid (but not necessarily that it belongs to Binance). A failure will print the reason — for example, a corrupted or tampered signature.

Command 3: Check the signing scheme

apksigner verify --verbose Binance.apk

The output shows which signing schemes were used:

Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true

The official Binance APK typically uses dual v2 + v3 signing (APK Signature Scheme v2/v3). If you only see v1, it may be an old version or a package that has been tampered with.

Tool 2: An Android app (on your phone, the most convenient)

If you'd rather not install command-line tools, you can check the signature directly from an app on your Android phone.

Recommended tools

App Platform Root required What it shows
ApkSignatureViewer Android No Package name + signature fingerprint
App Inspector Android No Package name + permissions + signature
APK Analyzer Android No Full APK structure

ApkSignatureViewer steps

  1. Install ApkSignatureViewer (available on Google Play or F-Droid)
  2. Install the Binance APK
  3. Open ApkSignatureViewer → select Binance
  4. You'll see the package name, version, and SHA-256 signature

App Inspector steps

  1. Install App Inspector
  2. Open it and select Binance
  3. Scroll to the bottom → look for the SHA-256 signature

The advantage of an on-device tool: no computer, no ADB, no root required — done in seconds.

Both tools should give the same result

Whether you use apksigner or an on-device tool, the SHA-256 fingerprint output should be identical. If it isn't:

  • The on-device tool's algorithm implementation may be buggy — trust apksigner
  • The installed app is genuine but the APK file you're checking is a fake — be cautious
  • The tool version is too old — update the tool

Cross-checking the official Binance signature fingerprint

Once you have the SHA-256 fingerprint, how do you know if it's Binance's official one?

Source 1: Binance official announcements

The "App Security" or "Developer" page on the Binance website occasionally publishes the APK signature fingerprint. This isn't a fixed URL, though — you'll need to search for it.

Source 2: APKMirror and other well-known mirrors

APKMirror is a well-known APK mirror site in the Android community, and every listed APK has a signature fingerprint page. When downloading the Binance APK, check the "Cert sha-256" field on APKMirror.

Source 3: Cross-checking multiple versions

Download several versions of the Binance APK (v2.83.x, v2.84.x, v2.85.x) and print the fingerprint for each with apksigner:

  • All identical — most likely genuine packages signed by the same developer
  • Not identical — some may be fakes, or Binance may have rotated its keys

Source 4: Cross-checking across multiple devices

Install the same APK on 3 phones: A from the official website, B from another source, C from a friend. Check the SHA-256 signature on all 3 with an on-device tool:

  • All identical — all the same package
  • A and B match but C doesn't — C may have a fake package installed

The full verification workflow

Here's a recommended end-to-end workflow:

Step 1: Download the APK (from the official website)

Download the roughly 85MB APK from the Official Binance App entry point.

Step 2: Check the file size

The file should be 80-95MB. If it deviates noticeably, delete it immediately.

Step 3: Check the signature with apksigner

Run apksigner verify --print-certs Binance.apk on your computer and note the SHA-256 fingerprint.

Step 4: Check the package name

apksigner also reads the manifest, but it's more direct to use:

aapt dump badging Binance.apk | grep package

The output should read package: name='com.binance.dev'.

Step 5: Check again after installing

Once installed, check the signature again with ApkSignatureViewer. If both results match — it's genuine.

Step 6: Confirm it redirects to binance.com after login

Launch the app; the login page should redirect to accounts.binance.com. If it redirects to an unfamiliar site, uninstall immediately — this could be a man-in-the-middle hijack or a fake package.

Common signature anomalies

Anomaly Likely cause Action
Verifies but SHA-256 doesn't match the known fingerprint A re-signed fake package Delete
Verification failed Corrupted or tampered signature Delete
Multiple signers An APK with more than one signer may have been injected Be cautious
v1 signature only A very old version or a repackaged file Be cautious
Certificate has expired Expired certificate Check whether this is a rotation period
DN field shows garbled Chinese text Fake package using a non-standard certificate Delete

A few advanced apksigner commands

Verify signature block integrity

apksigner verify --print-certs --verbose Binance.apk

Prints details for every signing scheme, so you can see whether v1/v2/v3 are all valid.

Check the signature block size

apksigner verify --max-sdk-version=33 Binance.apk

Verifies signature compatibility against a specific Android version.

Check whether the file was modified after signing

apksigner verify --check-signed Binance.apk

Verifies that the APK wasn't modified after it was signed (including the ZIP comment and alignment).

A note on the aapt tool

Alongside apksigner, aapt is also commonly used — it's built specifically for viewing APK metadata:

aapt dump badging Binance.apk

The output includes the package name, version number, minimum Android version, app name, requested permissions, activity list, and more.

Beyond signature verification, it's worth taking a look at the requested permission list with aapt — fake packages often request unusual permissions (SMS, contacts, auto-start), while the official app only asks for notifications, camera, storage, and network access.

How this fits with package-name and file-size checks

A complete authenticity check should really be three layers:

Layer Tool Time needed Strength
File size File manager 5 seconds Weak
Package name App info / aapt 30 seconds Medium
Signature apksigner / app 1-2 minutes Strong

See Binance APK package name check for a matching walkthrough, or browse the Android APK category for more hands-on Android guides.

Handling signature rotation

In rare cases, Binance rotates its signing key (for example, using key rotation under APK Signature Scheme v3 on Android 11+). When that happens, you'll see something like:

Signer #1: <old signature SHA-256>
Signer #2: <new signature SHA-256>

Seeing two signatures at once means you're in a rotation period, and that's normal. Judging a package as fake based on only one of the two is a mistake. Rotation periods typically last several months.

FAQ

Q: Do I need Android Studio to use apksigner? A: No. You can install just the command-line tools (about 200MB) and use sdkmanager to install the build-tools — that gets you apksigner. It saves you 6GB+ compared with installing all of Android Studio.

Q: Does the signature change when an APK is transferred — say, emailed or uploaded to cloud storage? A: No. An APK is a ZIP file, and transferring it doesn't change its internal contents. If the signature changes after a transfer, the file was swapped somewhere along the way — it's not a transfer artifact.

Q: Is a signature-viewer app on your phone as accurate as running apksigner on a computer? A: They're equally accurate in terms of the algorithm. But an app's implementation can have bugs or restricted read permissions. For strict verification, trust apksigner.

Q: What's the difference between v2 and v3 signatures? A: v1 is JAR signing (the older scheme), v2 is a whole-APK hash-based signature (more secure), and v3 supports key rotation. Android 9+ requires v2, and the Binance APK typically uses both v2 and v3 together.

Q: Why does apksigner output "DOES NOT VERIFY"? A: Possible reasons: (1) the APK is corrupted; (2) the signature has been tampered with; (3) your tool version is too old to recognize a newer signing scheme. Try updating build-tools to the latest version first.

Q: Can I judge the signature just by looking inside the extracted APK's META-INF folder? A: You can look, but META-INF only contains the binary signature block — you can't read a SHA-256 fingerprint by eye. You still need a tool like apksigner to compute it.

Q: Does iOS have anything similar to signature verification? A: iOS code signing is enforced by Apple, and every app installed through the App Store has already passed signature verification. So iOS users don't need to verify signatures manually. Android's openness is what makes user-side verification necessary.

Q: Can I still verify the signature after installing the app? A: Yes. An installed app's signature info is stored in /data/system/packages.xml (requires root), or you can read it via the PackageManager API using an app like ApkSignatureViewer — no root needed.