A comprehensive, robust, and highly-optimized remote security and administration system designed for Windows PCs, controllable entirely via a Mobile App.
This project is a multi-layered security system that allows users to remotely control, monitor, and secure their Windows machines through a dedicated mobile application. It leverages a lightweight Rust service running in the background, minimizing CPU and RAM overhead, while providing instantaneous WebSocket-based communication through a cloud relay.
- ⚡ Remote PC Lock & Control: Lock your PC screen instantly from anywhere.
- 🛡️ USB Port Blocking: Prevent unauthorized physical data access by disabling USB mass storage devices.
- 📸 Stealth Camera Capture: Remotely trigger the webcam to take silent snapshots and securely send them to your mobile app.
- 🛑 Secure Service Hibernation (OTP): Suspend the background service to save resources via a secure 6-digit OTP verified between the PC and Mobile App.
- ☁️ Seamless OTA Updates: Hot-update the background services without ever needing to uninstall or manually disrupt the system operations.
- 📱 QR Code Pairing: Easy and secure zero-config pairing between the Mobile App and the PC using QR codes.
The system consists of 4 highly decoupled modules:
graph LR
subgraph Client [📱 Mobile App]
Mobile[Expo React Native]
end
subgraph Server [☁️ Cloud Relay]
Relay[Node.js + Socket.IO]
end
subgraph Desktop [💻 Windows PC]
UI[SecurityApp - Tauri/React]
Service[Background Service - Rust]
Watchdog[Watchdog Service - Rust]
end
Mobile <-->|Encrypted Commands| Relay
Service <-->|Socket.IO Events| Relay
UI <-->|Named Pipes IPC| Service
Watchdog -->|Process Monitoring| Service
UI -.->|QR Code Pairing| Mobile
Service(Rust): The core engine. Runs as aNT AUTHORITY\SYSTEMservice. It maintains a persistent Websocket connection to the Cloud Relay, executes hardware-level commands, and exposes a Named Pipe for the PC UI.SecurityApp(Tauri + React): The local management dashboard. Used strictly for initial setup, QR code pairing, generating OTPs, and triggering OTA updates.ControlApp(React Native / Expo): The remote control center. Allows the user to monitor activity logs and send security commands on the go.Cloud(Node.js + Express): A lightweight, stateless intermediary router that bridges the Mobile App and the Windows Service. It also hosts static binaries for OTA (Over-the-Air) updates.
Follow these steps to deploy the entire security suite from scratch.
- Navigate to the
Clouddirectory. - Deploy this folder to a Node.js hosting provider (e.g., Render, Heroku, or an AWS EC2 instance).
- Once deployed, note down your server URL (e.g.,
https://my-security-relay.onrender.com).
For maximum convenience, an automated build pipeline is provided. You need Rust, Node.js, and Tauri CLI installed on your machine.
- Double-click the
build.batfile located in the root of the project. - The script will automatically compile the Rust services (
--release), build the Tauri UI, and package everything into a singleSecurity_Installer.ziparchive. - Extract
Security_Installer.zipand runinstaller/install.batas Administrator. - The system will automatically register the services and launch the PC UI.
- Navigate to the
ControlAppdirectory. - Install dependencies:
npm install
- Start the Expo development server:
npx expo start
- Use the Expo Go app on your iOS or Android device to scan the QR code shown in your terminal. (Alternatively, use EAS Build to generate a standalone
.apkor.ipa).
- Open the Security App on your Windows PC.
- Ensure the "Server Relay URL" field matches your deployed Cloud Relay URL.
- Open the Mobile App, log in, and click Scan QR to Pair.
- Point your phone camera at the QR code displayed on the PC screen.
- Done! Your devices are securely paired. You can now remotely lock the PC, disable USB ports, or take stealth photos.
- OTA Updates: Compile new
.exefiles inService, place them inCloud/public/updates/, increment theversion.json, and push to your server. Users can update via a single click in the PC UI. - Service Logs: Debug logs for the Windows Service can be found at
C:\Windows\Temp\security_service.log.