Skip to content
Projects

mocikadev/mocika-shield has 125 GitHub stars and 26 forks. GitHot measured +2 stars in 24 hours, +8 in 7 days, and +19 in 15 days. Last checked 2026-11-17 02:24 UTC. Last push 2026-11-15.

How these counts are measured

Measured star growth

in 24h
+2
in 7 days
+8
in 15 days
+19
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Android APK 加固工具(DEX 加密 + 壳保护 + 反调试) · Android APK hardening — DEX encryption, stub loader & anti-debug

Web & Apps

README.en.md

Original

Mocika Shield — Android APK Hardening Tool

简体中文 | English

Latest Release CI License

Protect and sign Android APKs and manage certificates locally. DEX encryption, certificate binding, and baseline runtime protection raise the cost of static analysis, tampering, and unauthorized re-signing—not a guarantee against unpacking or reverse engineering.

The recommended desktop GUI supports Windows, macOS, Linux, and Chinese/English interfaces. A source-built CLI is available for automation and development.

Use only with applications you own or are authorized to protect. Do not bypass third-party protections or use this tool for unauthorized purposes.

Core Capabilities

  • DEX and runtime protection: encrypt application DEX files, bind them to the original certificate, and apply baseline anti-debugging or optional strict environment checks.
  • Preflight checks: inspect signatures, existing protection, system requirements, and ABIs, with compatibility warnings and supported actions.
  • Integrated signing: import, create, and manage certificates; automatically sign protected output or sign an APK independently.
  • Reusable settings: remember protection options and the protection page's certificate choice, customize output directory and filename, and freeze each running task's configuration.
  • Installation compatibility: handle APK ZIP alignment and common native-library cases, with separate standard and Android 4.4 industrial modes.
  • Diagnostics: copy sanitized summaries and optionally preview and submit an error report. APKs and signing materials are processed locally.

Download and Quick Start

Download a stable desktop installer from GitHub Releases.

Platform Package
Windows 10 or later (64-bit) MocikaShield_x.y.z_windows_x64_setup.exe
macOS MocikaShield_x.y.z_macos_universal.dmg
Linux MocikaShield_x.y.z_linux_amd64.AppImage or .deb

The Windows desktop app does not support Windows 7, 8, or 8.1; upgrade to Windows 10 or later. This desktop requirement is separate from the Android versions supported by protected APKs.

Install a full JDK 8 or later, with java and keytool available. Desktop release users do not need to install the Android SDK. Installers are not commercially code-signed or notarized; download only from a trusted source.

  1. In Certificates, import the original APK's signing certificate. For a new project, you may create one, but the input APK must also be signed with it first.
  2. In Protect, select an already signed APK and review the preflight results.
  3. Choose the target system and protection policy. Normally use Android 5.0+ and the recommended standard protection; use industrial mode only when Android 4.4 is required.
  4. Review the output directory, filename, automatic signing certificate, and per-app sharing choice, then start protection.
  5. Test the signed output on target devices: installation, launch, core functionality, and upgrade installation.

Output defaults to the input APK's directory with a suggested filename; both can be changed before execution. Without automatic signing, sign the output with the original certificate. Re-signing protected output with another certificate prevents startup.

macOS reports that the developer cannot be verified

After verifying the download source and moving the application to /Applications, you can run:

xattr -rd com.apple.quarantine /Applications/MocikaShield.app

This removes quarantine; it does not mean the application is notarized by Apple. Open it again. See the usage guide for more help.

Preview

Mocika Shield protection page illustration

The screenshot illustrates the layout; available options depend on the current version. More screens and instructions are in the usage guide.

Compatibility and Limitations

Mode Scope
Android 5.0 and later API 21+; armeabi-v7a, arm64-v8a, x86, and x86_64. An APK does not need all four ABIs
Android 4.4 industrial Android 4.4 uses armeabi-v7a/NEON; the same APK may retain other supported ABIs for Android 5.0+. Removing legacy armeabi requires confirmation. Mixed-ABI device regression is pending
  • Compatibility mode does not lower the application's minSdkVersion; vendor systems and hardware still need testing.
  • APK only: no direct AAB or APKS protection, no re-protecting protected APKs, and inputs must be signed.
  • The GUI processes one APK at a time; no batch queue is provided.
  • Unneeded legacy ABIs can be excluded with per-task confirmation. Prefer filtering them in the original project; missing business libraries are not generated.
  • 16 KB ZIP alignment does not establish ELF page-size compatibility for every third-party library or guarantee Google Play acceptance.
  • A blank AppImage window on some Fedora environments remains under investigation: #121.

See the usage guide for detailed boundaries. Include the version, environment, and sanitized diagnostics when reporting problems.

How It Works and Security Scope

Protection reads the original certificate, compresses and encrypts DEX files, injects the stub, then rebuilds, aligns, and optionally signs the APK. At runtime, the stub checks the environment, validates or decrypts the DEX cache, loads code, and starts the original application.

Production uses a decrypted DEX cache in the application's private directory. It is not a fully in-memory DEX loader or method-code extraction scheme. Root access, process control, or other elevated privileges may allow runtime code extraction. Standard protection does not block startup solely because of root signals; strict protection blocks some risky environments but cannot guarantee detection of hidden root or prevent bypasses.

Hardening does not replace server-side authorization, key management, or application security design. See runtime security and technical internals.

Privacy

APKs, certificates, keystores, and signing passwords are processed locally and not uploaded. The desktop tool has three independent data channels:

Channel Data and controls
Anonymous usage statistics Enabled by default; random installation identifier, tool version, launch/task counts, and fixed failure categories. Can be disabled in Settings; no package names or raw logs
Safe error reports Preview and confirm each report; no raw logs, APKs, paths, package names, certificates, or passwords. Independent of the statistics switch
Per-app usage sharing Controlled on protection/signing pages, selected by default for new package names. Opt-outs persist across pages and restarts. Successful operations send app name, package name, version code, tool version, operation, flow, success date, and protocol/deduplication metadata; no device identifier

App sharing is independent of anonymous statistics. Reports are maintainer-only and retained for 180 days. Opting out stops future sharing for that package but does not delete received records. These reporting features are not injected into protected APKs. See data and privacy documentation for scope, retention, and deletion details.

Documentation and Development

Topic Documentation
GUI, certificates, configuration locations, and CLI Usage guide
Installation and runtime problems Troubleshooting
Source builds Build guide, environment requirements
Architecture and internals Documentation index
Future work Roadmap

Detailed guides are currently primarily in Chinese. The CLI is source-built; Releases contain desktop GUI packages only. Build make build-stub first, then make build-cli or make build-gui. Refer to the build guide for dependencies and platform-specific steps.

Feedback and Community

  • Read the support guide, then open a GitHub issue. Copy diagnostics from About.
  • Use the feature request form, or upvote an existing matching request.
  • Report vulnerabilities privately following SECURITY.md. Do not publish exploits, business APKs, certificates, or passwords.
  • Chinese-language QQ community: 1090352773. Keep actionable bug reports in GitHub issues for tracking.
QQ group QR codeMocika Shield QQ community: 1090352773

Support the Project

If Mocika Shield has helped you, feel free to buy me a coffee via WeChat ☕

WeChat donation QR code

You're also welcome to share the types of apps you protect and the devices they run on through a donation message, GitHub issue, or our QQ group. Real-world use cases help us prioritize future compatibility work.

Thank you to everyone who uses, provides feedback on, and supports Mocika Shield.

License

Dual-licensed under MIT OR Apache-2.0, at your choice: MIT · Apache-2.0.