English   简体中文

DuckDetector is an Android security detection application focusing on local, on-device evidence collection. It is designed to identify Root-related tampering, runtime Hooks, Mount operations, KeyStore integrity (Attestation Trust), and virtualized execution environments. This application combines a Jetpack Compose UI interface, modular Kotlin detection packages, and low-level C++ / assembly probes to present detailed detection results, method coverage, and scanning status summaries through structured cards.

Please read the DuckDetector coding standards before submitting changes to the codebase, workflows, or git history.

• Modular Architecture: Features independent modules with specific functions; each module includes its own exclusive Repository, Mapper, ViewModel, and card UI.
• Native Preload: Implements low-level early preloading via a transparent NativeActivity launcher to capture extremely early mount points and virtualization traces.
• Native Probes: Utilizes system-call (Syscall) level, time-sensitive, mount, and runtime visibility checks implemented in C++ and Assembly.
• Cross-Process & Isolated Process Validation: Co-validates across multiple processes and isolated processes (Isolated Process) to minimize reliance on a single signal.
• Local & Privacy-First: By default, TEE revocation checks use a built-in static snapshot. It only accesses the network when the user manually enables "Online Refresh" in settings.

The app currently supports heuristic detection in the following security domains:

Bootloader · Custom ROM · Dangerous Apps · Kernel Check · LSPosed · Memory · Mount · Native Root · Play Integrity Fix · SELinux · SU · System Properties · TEE · Virtualization · Zygisk

In addition, the project contains helper modules such as dashboard, settings, and deviceinfo to provide data aggregation, user controls, and device context visualization.

• Compose Dashboard: Includes detection cards, scan status summaries, top findings, and detailed expandable rows.
• Consistent Card Design: A unified shared card style ensures excellent readability for long labels, detection statuses, and evidence strings across different modules.
• Independent Settings & Info Streams: Separates advanced controls and environmental context from the main detection logic to keep the interface clean.

Duck-Detector-Refactoring/
├─ app/
│  ├─ src/main/java/com/eltavine/duckdetector/
│  │  ├─ core/            # Core common components and foundations
│  │  ├─ features/        # Individual detection feature modules
│  │  └─ ui/              # Global common UI and themes
│  └─ src/main/cpp/       # Low-level C++ / Assembly probe source code
├─ build-logic/           # Gradle composite build logic
├─ gradle/                # Gradle wrapper configuration
├─ scripts/               # Automation or helper scripts
├─ build.gradle.kts
└─ settings.gradle.kts

Most detection feature modules (features) strictly follow this clear package structure:

• domain: Data models for reports and results (Models).
• data: Repositories, probes, native bridges, and system service helpers.
• presentation: Data mappers and UI-state reducers.
• ui: Detection card components and module-specific UI models.

💡 All native probes are located under app/src/main/cpp and are ultimately compiled into a single shared dynamic link library (.so). This is used for preload capture, mount checks, virtualization snapshots, renderer validation, and low-level trap path interceptions.

• Android Studio (Latest stable version recommended)
• Android SDK 37.0 & Android Build Tools 37.0.0
• JDK 17
• Android NDK 30.0.14904198
• CMake 4.1.2

Compile Debug Version:

# Windows environment
gradlew.bat :app:assembleDebug
# Linux / macOS environment
./gradlew :app:assembleDebug

Daily Development Validation Command (Recommended):

# Validate Kotlin compilation, run unit tests, and package the app
./gradlew :app:compileDebugKotlin :app:testDebugUnitTest :app:assembleDebug

🔐 Signing Note: Automatic signing for the Release version is controlled by the environment variables ANDROID_KEYSTORE_PATH, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, and ANDROID_KEY_PASSWORD. When these four variables are fully present, the build system will automatically enable the ciRelease signing configuration.

• Localized Security: Detection logic runs primarily locally on the device; it does not collect or upload your sensitive private data.
• Non-Intrusive: The app itself does not require root privileges to function properly.
• Heuristic Detection: All security detections are based on heuristic algorithms. No single signal should be relied upon in isolation as absolute proof of trustworthiness.
• Hardware & Vendor Restrictions: Due to OEM policies or sandbox rules, some probes may report downgraded statuses on specific models. Certain low-level checks rely strictly on the arm64-v8a ABI architecture.

This software is provided "as is", without warranty of any kind. It is designed for educational, diagnostic, and security research purposes only. The developers assume no liability for direct or indirect damage, data loss, or system instability resulting from use of this application. Relying on heuristic security detection is at your own risk.

This project is open-sourced under the Apache License 2.0.