antidetect-phone-kit
Cloud antidetect phone linter — ARM Android device fingerprint, GPS, IMEI coherence before TikTok/Instagram login.
pip install antidetect-phone-kit
ad-phone audit -i device.yaml
CLI: ad-phone · Python 3.10+ · offline lint only
Coupon hubs:
SAAS50(primary) /MIN50cloud phone — anti-detect.github.io · SaaSVerdict. Get latest codes before checkout. Affiliate disclosure.
Lint ARM cloud Android profiles before app-native login. Catches emulator-style configs that GeeLark and MoreLogin Remote Phone avoid with real hardware fingerprints.
Problem
Cloud phone bans often trace to x86 emulators, mismatched GPS/timezone, or shared datacenter proxies — not “bad content.” Teams need a fast YAML audit before scaling phone farms.
Install
pip install antidetect-phone-kit
Quick start
ad-phone template -o device.yaml
ad-phone audit -i device.yaml
When profiles still fail (playbook)
| Symptom | Likely cause | Fix |
|---|---|---|
| Instant app ban | PC emulator / static device ID | arm_cloud: true + unique IMEI |
| Wrong store region | GPS ≠ proxy country | Align gps_lat/lng, country, proxy |
| GeeLark/MoreLogin migration gaps | Missing proxy mapping | Pair with mobile-vendor-bridge |
Coupon hubs: anti-detect.github.io · SaaSVerdict — verify SAAS50 at checkout.
CLI
| Command | Description |
|---|---|
ad-phone audit |
Score device YAML |
ad-phone validate |
Lint YAML schema |
ad-phone template |
Starter ARM cloud profile |
ad-phone --show-deal |
Opt-in MLX Cloud Phone coupons |
Limitations
- Offline linter — does not call GeeLark, MoreLogin, or MLX APIs.
- Does not install APKs or run ADB.
Production
Production app-native stacks need Multilogin Cloud Phone ARM environments — code SAAS50 on eligible purchases. Disclosure: docs/AFFILIATE.md. Coupons: ad-phone --show-deal.
FAQ: docs/FAQ.md
Related tools (on PyPI)
| Package | CLI | Role |
|---|---|---|
| cloud-phone-kit | cloud-phone |
Launch readiness |
| mobile-vendor-bridge | mobile-bridge |
GeeLark/MoreLogin import |
| app-warmup-phone | app-warmup |
App warmup cadence |
| virtual-android-farm | phone-farm |
N-phone job queue |
License
MIT
Cloud antidetect (partner): Multilogin · SAAS50 · anti-detect.github.io · SaaSVerdict
Open-source SDK: github.com/multilogin-automation
Metadata
Release files for antidetect-phone-kit 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| antidetect_phone_kit-0.1.5.tar.gz | 7.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| antidetect_phone_kit-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.6 kB
Release files / antidetect_phone_kit-0.1.5.tar.gz
| Download URL | antidetect_phone_kit-0.1.5.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25ae90c5484a2767d760f573c10af422f17132d8c37c2a5fb176686e34859c7a
|
|
BLAKE2b-256 checksum How to use checksums |
4aaf1b2452818a9fe7dfb562552719e06f1019324a9bb3510ff88ac6dfc86eb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / antidetect_phone_kit-0.1.5-py3-none-any.whl
| Download URL | antidetect_phone_kit-0.1.5-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
965a64431535af6012acf85f36f83e24abb470f98197a2e47203c064937c0f7b
|
|
BLAKE2b-256 checksum How to use checksums |
0e416d0a71301be7d982081ab5e7a762eded9589dce8b25d9e8a253c73bf5029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for antidetect-phone-kit 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.