---

🎥 Video Tutorial

---

🚀 Features

• Android Remote Administration Lab
• Real-time Device Monitoring
• Reverse Engineering Utilities
• Socket Communication System
• Cybersecurity Testing Environment
• Builder Interface
• File Management
• Notification Monitoring
• Calls / SMS / Contacts Modules
• Camera Interaction
• Research-focused Dashboard
• Windows Control Panel UI

---

🧠 Technologies Used

---

⚙️ Installation

git clone https://github.com/OnlineUnknowns/Unknown-Hacking-Tool.git

cd Unknown-Hacking-Tool

Open:

Unknown.sln

Then build using Visual Studio.

---

📂 Project Structure

Unknown-Hacking-Tool/
│
├── builderform.cs
├── mainform.cs
├── socket.cs
├── cameraform.cs
├── callsform.cs
├── contactsform.cs
├── smsform.cs
├── Program.cs
│
├── assets/
├── screenshots/
└── README.md

---

🎥 Cyberpunk Animation Banner

---

⚠️ Disclaimer

This repository is intended strictly for:

• Ethical Hacking
• Educational Research
• Reverse Engineering Practice
• Malware Analysis Labs
• Authorized Security Testing

Any misuse, unauthorized access, or illegal activity is strictly discouraged.

---

🌌 Developer

Unknowns

Cybersecurity Researcher • Reverse Engineer • Software Developer

```

APK Build Guide for OnlineUnknows

Overview

This document explains how to use the built-in APK Builder in the OnlineUnknows admin panel to generate a mobile payload APK.

The builder uses a template stub APK stored in res/stub/stubapk and repackages it after applying the user-provided server settings, app metadata, notification text, and optional icon.

Note: This project is intended for educational and research use only. Do not use it on devices you do not own or on networks without explicit authorization.

---

Requirements

• Windows with the compiled Unknown.exe admin panel
• Java Runtime Environment installed and available on PATH
• The res/tools folder must contain the required Android build tools:
  • apktool.jar
  • apksigner.jar
  • zipalign.exe (optional but recommended)
  • keystore.jks or apktool.pem + apktool.pk8 for signing

Where the APK builder lives

• Open Unknown.exe
• Select the Builder menu or tab
• Choose the APK tab inside the builder UI

The builder is implemented in builderform.cs and performs the following steps:

1. Copy the APK stub from res/stub/stubapk into a temporary working folder.
2. Update AndroidManifest.xml with the selected package name and version.
3. Update res/values/strings.xml with your app display name and notification text.
4. Patch the payload socket settings inside Socket.smali with the chosen server IP and port.
5. Replace the APK icon files if you provide a new PNG icon.
6. Rebuild the package using apktool.
7. Sign the APK using apksigner and the available keystore or certificate.
8. Output the final APK to res/out and open that folder.

---

Required fields in the APK builder UI

• App Name: This becomes the app display name inside Android.
• Server IP: The control server IP that the payload will connect to.
• Server Port: The control server port used by the payload socket.

Optional fields:

• Package Name: The Android package identifier. If empty, the builder keeps the stub package.
• Version: The Android versionName value.
• Notification Text: The service notification text shown by the Android background service.
• APK Icon: Click the icon placeholder to select a PNG file. The builder will replace launcher icons in res/mipmap-* directories.

---

How to build an APK step-by-step

1. Launch Unknown.exe.
2. Open the Builder section.
3. Switch to the APK builder tab.
4. Fill in the required fields:
   • App Name
   • Server IP
   • Server Port
5. Optionally set:
   • Package Name
   • Version
   • Notification Text
   • custom APK icon via the icon selector
6. Press Build.
7. Wait while the builder shows log progress in the built-in console.
8. After completion, the final APK will be written to res/out and the folder will open automatically.

---

Output locations

• Temporary working directory: res/temp/stubapk
• Final signed APK output: res/out/<AppName>.apk

If the builder fails, review the log panel for details. Common issues are missing Java, missing apktool.jar, or missing signing files.

---

Troubleshooting

Java not found

If java is not installed or not on PATH, the builder cannot run apktool.jar or apksigner.jar.

• Install Java from https://www.java.com/
• Restart the app after installation

Stub folder missing

The APK builder expects the stub source files at:

• res/stub/stubapk

If this folder is absent, the builder cannot modify or rebuild the APK.

Signing tools missing

The builder can use either of these signing options:

• res/tools/keystore.jks
• res/tools/apktool.pem and res/tools/apktool.pk8

If neither is present, the APK will be copied unsigned and marked as such.

Icon replacement not working

The builder replaces launcher icons only when PNG icon files already exist in the stub APK directories:

• res/mipmap-mdpi
• res/mipmap-hdpi
• res/mipmap-xhdpi
• res/mipmap-xxhdpi
• res/mipmap-xxxhdpi

Use a square PNG icon file and click the icon area in the UI to load it.

---

Notes

• The builder modifies Socket.smali in the stub payload to hardcode the server IP and port.
• If the payload fails to connect, verify the IP/port values and confirm the listener is reachable.
• This builder is designed to make an existing stub APK payload configurable, not to build an Android app from source.

---

📡 Connect & Support

💡 If this project saved you time — drop a ⭐ on the repo. It costs nothing and means everything.

Legal warning

This software is for educational and defensive research only. Do not use it for unauthorized access, privacy violations, or malicious activity.

Always comply with local laws and only test on systems you own or have written permission to evaluate.