ANDROID · TERMUX · OFFLINE RESEARCH

SN512A GhostStrike

A security research and offline firmware inspection workbench with cloud development and private diagnostics.

Open cloud IDE · Private source repository

Deployment scope

This portal contains documentation. Device enrollment, VPN provisioning, exploit functionality, and release validation remain incomplete. No validated firmware or rooting package is offered.

Private diagnostics setup

  1. Launch the Codespace and authorize Tailscale to join your own tailnet. Review its access policy to permit only the intended Codespace identity to reach this Android device on TCP 8022.
  2. Install the official Tailscale Android app, join the same tailnet, and note the device's Tailscale IPv4 address.
  3. In native Termux, install OpenSSH and Python using pkg install openssh python. Add the approved Codespace SSH public key to ~/.ssh/authorized_keys. Keep private keys off this website.
  4. From the checked-out repository in Termux: bash scripts/setup-mode.sh enable. This stops the recorded SSH listener; run locally since remote access may disconnect.
  5. When setup finishes: bash scripts/setup-mode.sh restore, then bash scripts/setup-mode.sh private-ssh YOUR_TAILSCALE_IP. From the Codespace, connect using ssh -p 8022 TERMUX_USERNAME@TAILSCALE_IP. Compare the host-key fingerprint through the device before accepting it.

The script refuses a non-tailnet address and binds SSH only to the supplied local address with password login disabled. Android VPN routing can vary: if binding or connection fails, stop and inspect device behavior before changing the network configuration.

Temporary setup protection

Setup mode creates a reversible project marker and stops the recorded SSH listener. There is currently no project updater. Future project update jobs must check the marker. Existing SSH sessions and independently managed listeners require separate inspection. Outbound HTTPS, VPN, Android updates, and system protections are not changed.

Unprivileged Termux cannot enforce an Android-wide firewall or suspend Android system updates.

Security and releases

No public command shell or device-management API is enabled. Future APIs require scoped authentication, audit logs, rate limits, and replay protection. Firmware work is offline until backups, exact device identity, and validation are established.

Approved releases — private repository access required; no validated release is currently advertised.