If you are searching for the X777 Game APK, you may encounter different version numbers, filenames, and APK sizes across different download pages. That makes it difficult to determine whether two X777 Game APK files are actually the same build.

For this fact check, we analyzed a specific X777 Game APK rather than relying only on the information displayed on a download page. The examination covered its package name, version information, Android SDK requirements, permissions, native libraries, file size, SHA-256 hash, and signing certificate.

The analyzed file identifies itself as X777 Game version 6.9.18, with version code 12 and package name com.ltcg.kup2039.utej.

The findings below apply specifically to the APK that was analyzed. They should not automatically be applied to every file distributed under the X777 Game name.

Table of Contents

X777 Game APK Technical Details

Detail	Verified information
App	X777 Game
Package name	com.ltcg.kup2039.utej
Version	6.9.18
Version code	12
Minimum SDK	API 23
Minimum Android	Android 6.0
Target SDK	API 34
Target Android	Android 14
APK size	76.63 MB
Exact file size	80,349,548 bytes
Architectures	arm64-v8a, armeabi-v7a
SHA-256	88cda7828aa9647ea00373e720d57a3a55841bc806206aca36c6982b6f341fb6
Signature schemes	V1, V2, V3
Signers	1
Signing key	RSA 2048-bit

Android’s documentation identifies Android 6.0 as API level 23 and Android 14 as API level 34.

Which X777 Game APK Version Was Actually Analyzed?

The APK examined during this investigation internally reports:

• Version name: 6.9.18
• Version code: 12
• Package: com.ltcg.kup2039.utej

This is more useful than relying on the filename alone.

The analyzed file was named:

a48564_nn_v3.apk

That filename does not contain the application’s actual version number. APK metadata therefore provides a more reliable way to identify the build.

Android’s own documentation explains that application versioning and API requirements are represented through application metadata and manifest/build configuration.

Why the APK Filename Is Not Enough

An APK filename can be changed without changing the application inside it.

For example, a file could be renamed from:

a48564_nn_v3.apk

to:

X777.apk

without changing its contents.

The filename alone would therefore tell us very little about whether the file is version 6.9.18.

For this investigation, the stronger identifiers are:

• Package name
• Version name
• Version code
• File size
• SHA-256
• Signing certificate

These allow a particular APK build to be identified much more precisely.

X777 Game APK Version 6.9.18 Compatibility

The analyzed APK declares a minimum SDK of API 23.

API 23 corresponds to Android 6.0.

This means Android 6.0 is the minimum Android platform declared by this particular APK.

It does not guarantee that every Android 6.0 device will provide identical performance. Device hardware, manufacturer software, available memory, and other dependencies can affect the actual experience.

Minimum Android Requirement

Android 6.0 / API 23

This is the verified minimum SDK extracted from the APK.

X777 Game Targets Android 14

The APK declares target SDK API 34.

API 34 corresponds to Android 14.

Target SDK should not be confused with minimum SDK.

The APK does not require Android 14 simply because it targets API 34. Its minimum SDK remains API 23.

Android explains that target API levels affect platform behavior and compatibility rules, while minimum API requirements determine which Android versions an application can run on.

For the analyzed X777 Game build:

Minimum: Android 6.0 / API 23
Target: Android 14 / API 34

X777 Game APK File Size

The exact APK file measured:

80,349,548 bytes

That is approximately:

76.63 MB

This is the size of the exact file analyzed for this article.

It should not be treated as the universal size of every X777 Game APK. A different version or build may have a different file size.

For comparing two APK files, the SHA-256 hash is a stronger identifier than the displayed file size.

X777 Game Supports ARM64 and ARMv7

The APK contains native libraries under:

/lib/arm64-v8a/

and:

/lib/armeabi-v7a/

Therefore, the analyzed package contains native ARM libraries for both 64-bit ARM and 32-bit ARM devices.

During the inspection, no x86 or x86_64 native library directories were found.

The package contains a large collection of native components, including libraries associated with React Native, Hermes, image processing, Vision Camera, Bugsnag, Cocos, and other components.

The presence of a native library confirms that it is packaged inside the APK. It does not, by itself, prove how frequently or under what circumstances that component is used at runtime.

X777 Game APK Permissions

The analyzed manifest contains a relatively broad permission set.

Among the declared permissions are capabilities related to:

• Internet access
• Network and Wi-Fi
• Camera
• Microphone
• Media files
• Notifications
• Background operation
• Device state
• Biometrics
• Storage
• Advertising and attribution

Android maintains a reference list of permissions available to applications and defines what individual manifest permissions represent.

Camera and Microphone

The APK declares:

• android.permission.CAMERA
• android.permission.RECORD_AUDIO
• android.permission.MODIFY_AUDIO_SETTINGS

This confirms that camera and microphone-related permissions are declared in the APK.

It does not independently prove that X777 Game continuously records audio, takes photographs, or actively uses those capabilities.

Runtime behavior would require separate testing.

Network Permissions

The APK declares:

• android.permission.INTERNET
• android.permission.ACCESS_NETWORK_STATE
• android.permission.ACCESS_WIFI_STATE
• android.permission.CHANGE_WIFI_STATE
• android.permission.CHANGE_NETWORK_STATE

These permissions are consistent with an application that communicates with online services and interacts with network connectivity.

Media Permissions

The manifest includes:

• android.permission.READ_MEDIA_IMAGES
• android.permission.READ_MEDIA_VIDEO
• android.permission.READ_MEDIA_AUDIO

It also contains older storage permissions restricted to API 32 and below:

• READ_EXTERNAL_STORAGE
• WRITE_EXTERNAL_STORAGE
• MANAGE_EXTERNAL_STORAGE

The presence of an android:maxSdkVersion='32' restriction means those particular declarations are limited to the specified API range in the manifest.

Notifications and Background Operation

The APK declares:

• POST_NOTIFICATIONS
• FOREGROUND_SERVICE
• RECEIVE_BOOT_COMPLETED
• RECEIVE_USER_PRESENT
• WAKE_LOCK
• VIBRATE

These declarations indicate that the application includes capabilities associated with notifications, background services, wake locks, boot events, and vibration.

Again, manifest declarations should not be interpreted as proof of continuous runtime activity.

Biometric Permissions

The manifest includes:

• USE_FINGERPRINT
• USE_BIOMETRIC

These are associated with biometric authentication capabilities.

Advertising and Attribution Permissions

The APK also declares:

• com.google.android.gms.permission.AD_ID
• ACCESS_ADSERVICES_ATTRIBUTION
• ACCESS_ADSERVICES_CUSTOM_AUDIENCE
• ACCESS_ADSERVICES_AD_ID

Their presence indicates that advertising/attribution-related capabilities are included in the application manifest.

The permission list alone cannot tell us exactly what information is collected or how that information is processed.

X777 Game APK SHA-256 Hash

The SHA-256 hash of the analyzed file is:

88cda7828aa9647ea00373e720d57a3a55841bc806206aca36c6982b6f341fb6

This is one of the strongest identifiers for the exact APK analyzed in this article.

If another file produces a different SHA-256 value, it is not byte-for-byte identical to the analyzed APK.

A different hash does not automatically mean the other APK is malicious. It may simply represent another version or build.

X777 Game APK Signature Verification

The APK was successfully verified under:

• V1: Yes
• V2: Yes
• V3: Yes
• V3.1: No
• V4: No
• SourceStamp: No

There was one signer.

The signing certificate reported:

Certificate DN

CN=Franky Hu, OU=personal, O=Franky Hu, L=Mala, ST=Mala

Certificate SHA-256

e6035023a050207141d4cb7baf867dd1b2a1e2191f746eb3104c1c363556047d

Key algorithm: RSA

Key size: 2048-bit

Android’s official apksigner documentation explains that the tool can verify APK signatures and display signing certificate information with --print-certs.

What Does the Signing Certificate Tell Us?

The certificate gives us another useful way to compare APK builds.

If another APK claiming to be the same X777 Game build has a different signing identity, it should not automatically be treated as the same package.

Android uses signing keys to establish application update identity, and Google’s documentation recommends comparing certificate fingerprints against a trusted developer-provided identity when verifying that an app comes from the expected developer.

However, the certificate itself does not prove that the distributor is trustworthy.

It identifies the signing identity associated with the analyzed file.

Signature Warnings Found During Verification

The signature verification process also produced warnings for several META-INF/services/ entries:

• kotlinx.coroutines.c0
• com.fasterxml.jackson.core.l
• com.fasterxml.jackson.core.d
• md.r

These entries were reported as not protected by the signature.

This is a technical observation, not evidence that the APK is malware.

The APK nevertheless successfully verified under the V1, V2, and V3 schemes.

It would therefore be inappropriate to interpret these warnings alone as proof of APK tampering or malicious behavior.

What We Can Verify About This X777 Game APK

The technical analysis gives us a reproducible identity for the exact file examined.

We can verify that it contains:

• Package com.ltcg.kup2039.utej
• Version 6.9.18
• Version code 12
• Minimum SDK 23
• Target SDK 34
• 76.63 MB file size
• ARM64 and ARMv7 native libraries
• The recorded SHA-256 hash
• One RSA-2048 signing identity
• V1, V2, and V3 signature verification
• The permissions declared in its manifest

These are APK-level observations obtained from the file itself.

What This Analysis Cannot Prove

The technical inspection cannot independently establish:

• That this is the official X777 Game distribution
• That every X777 Game APK online is the same build
• That every declared permission is actively used
• What information the app sends during runtime
• Whether the app is completely malware-free
• Whether an X777 Game service is financially trustworthy
• Whether deposits or withdrawals will work
• Whether the APK will behave identically on every Android device

Those questions require different evidence.

This is why the version and technical findings in this article are presented as facts about the analyzed APK, rather than assumptions about every X777 Game file found online.

Is X777 Game Version 6.9.18 Official?

The APK analysis alone does not provide enough evidence to make that claim.

What we can establish is that the supplied APK internally identifies itself as:

X777 Game — version 6.9.18 — version code 12

It also has a consistent package identity, signing certificate, architecture set, and cryptographic hash.

To establish whether this is an officially distributed X777 Game release, those identifiers would need to be compared against a trusted reference distribution.

Therefore, this article does not label the analyzed file as “official” solely because its internal metadata contains the X777 Game name.

How to Identify This Exact X777 Game APK

If you have another X777 Game APK and want to determine whether it is the same file analyzed here, compare:

Package name

com.ltcg.kup2039.utej

Version

6.9.18

Version code

12

File size

80,349,548 bytes

SHA-256

88cda7828aa9647ea00373e720d57a3a55841bc806206aca36c6982b6f341fb6

Certificate SHA-256

e6035023a050207141d4cb7baf867dd1b2a1e2191f746eb3104c1c363556047d

The filename alone is not enough to establish that two APK files are identical.

X777 Game APK Safety Considerations

The analyzed APK declares permissions involving the camera, microphone, media, network connectivity, notifications, device state, storage, biometrics, and advertising-related services.

That does not automatically make the APK unsafe.

Applications can request multiple permissions for different features, and a manifest declaration does not by itself establish exactly how a permission is used at runtime.

For users downloading APKs outside a trusted distribution channel, however, verifying the identity of the exact file is useful.

A SHA-256 hash can establish whether two files are identical, while a signing certificate can help establish whether they share the same signing identity.

Neither is a complete security audit, but both are stronger evidence than relying on an APK filename or download-page title.

Related APK Guides

If you regularly compare APK builds, you may also find our other technical APK guides useful:

• Y71 Game APK — version conflict and APK verification analysis.
• Truecaller Premium APK — a separate application-focused APK guide.
• PowerDirector APK — another application analysis and feature guide.
• TeraBox Mod APK — related APK information and compatibility content.

These links are intentionally placed where they are relevant rather than adding a large block of unrelated internal links.

X777 Game APK — Final Verdict

The X777 GameAPK analyzed for this fact check is a 76.63 MB Android application identified as version 6.9.18 with version code 12 and package name com.ltcg.kup2039.utej.

It declares API 23 / Android 6.0 as its minimum SDK and API 34 / Android 14 as its target SDK. Android’s current platform documentation confirms those API-level mappings.

The package contains native libraries for arm64-v8a and armeabi-v7a, while no x86 or x86_64 native library directories were found during the inspection.

Its SHA-256 is:

88cda7828aa9647ea00373e720d57a3a55841bc806206aca36c6982b6f341fb6

The APK successfully verifies under V1, V2, and V3 signing schemes and contains one RSA-2048 signing identity. Android’s apksigner tool is specifically intended for verifying APK signatures and inspecting signing certificates.

The manifest also declares a broad set of permissions covering network access, camera, microphone, media, notifications, storage, biometrics, background operation, and advertising-related services.

The key conclusion

The supplied APK can be technically identified as X777 version 6.9.18, version code 12, but the technical inspection alone cannot prove that every X777 APK online is the same build or that this particular file is an officially distributed release.

That distinction is important when comparing APK download listings.

Quick Reference

App: X777 Game
Version: 6.9.18
Version code: 12
Package: com.ltcg.kup2039.utej
APK size: 76.63 MB
Minimum Android: 6.0 / API 23
Target Android: 14 / API 34
Architectures: ARM64 + ARMv7
SHA-256: 88cda7828aa9647ea00373e720d57a3a55841bc806206aca36c6982b6f341fb6
Signing: V1 + V2 + V3
Signer count: 1
Key: RSA 2048-bit

Frequently Asked Questions

What version of X777 Game was analyzed?

The analyzed APK reports version 6.9.18 with version code 12.

What is the X777 package name?

The package name is:

com.ltcg.kup2039.utej

Does X777 6.9.18 require Android 14?

No. The APK declares API 23 / Android 6.0 as its minimum SDK and API 34 / Android 14 as its target SDK.

How large is X777 version 6.9.18?

The analyzed APK is 80,349,548 bytes, approximately 76.63 MB.

What is the SHA-256 of the analyzed X777 APK?

88cda7828aa9647ea00373e720d57a3a55841bc806206aca36c6982b6f341fb6

Which Android architectures are included?

The APK contains native libraries for arm64-v8a and armeabi-v7a.

Is the X777 APK signed?

Yes. The analyzed APK successfully verifies under V1, V2, and V3 signature schemes.

Does the permission list prove that X777 records audio or uses the camera?

No. It proves that the APK declares those permissions. Runtime testing would be required to determine exactly how those capabilities are used.

Can the SHA-256 prove that an APK is safe?

No. A SHA-256 hash identifies a particular file; it does not certify that the file is safe.

Is this definitely the official X777 APK?

The technical analysis confirms the identity and properties of the supplied APK, but it does not independently prove that it is an official distribution.

Technical Verification Note

The APK-specific information in this article was obtained by directly analyzing the supplied APK rather than copying version information from an APK listing.

The verification covered:

• Package name
• Version name
• Version code
• Minimum SDK
• Target SDK
• Manifest permissions
• APK size
• SHA-256 hash
• Native library architectures
• APK signature schemes
• Certificate fingerprint
• Signing key information

The results therefore apply specifically to the APK analyzed for this article.

For additional technical reference, Google’s official Android documentation covers APK signature verification with apksigner, Android API levels, and application SDK/version requirements.