Skip to content

Mobile Devices

Phones are targets in their own right, and they rarely live where you expect. This page covers the on-network route: discovering and exploiting a handset on a LAN you already own. For off-network signal interception (catching IMSIs, SMS and MFA from the air), see the Signal Decoupler. The handset is rarely the prize. What its owner saved on it can open doors a long way from the phone.

Mobile phones are hidden devices on corporate LANs. They are not visible by default, so you have to discover them before you can touch them.

Mobile devices are only found by cracking the wireless access point they are connected to:

  1. Hack into the network and find a wireless ACCESS_POINT on the LAN.
  2. Connect to the access point and run wifi_crack --scan to find networks.
  3. Capture the handshake with wifi_crack --capture <essid>.
  4. Crack it with wifi_crack --crack <essid>.

Once the network is cracked, the mobile devices on it become visible.

The NSO Pegasus Toolkit covers both handset families: Pegasus chains for iOS, Chrysaor for Android. Buy it from node://darkmarket.onion under the PEGASUS tab (2.5 BTC).

The licence also opens the operator console at node://dash.pegasus.onion. The console implants a handset from its phone number alone, with no network access and no LAN adjacency, provided you own an implant pack whose coverage reaches that handset’s OS version. Packs are sold on the same tab.

An implant is collection, not a shell. It reports messages, call logs, contacts, browsing history, file listings, installed apps, media, keychain and MFA codes, and it takes remote screenshots and location fixes. For a root shell on the handset you still need the terminal, and the terminal still needs the phone on your LAN.

With a phone discovered on your current LAN:

Command Platform What it does
pegasus <phone_ip> iOS Deploy the Pegasus zero-click exploit. Grants root.
adb_exploit <phone_ip> Android Exploit via the ADB debug bridge. Grants root.

Pegasus delivers an iMessage exploit chain, escapes the WebKit sandbox, escalates to kernel root, and installs a persistent backdoor. The Android path needs no toolkit and no purchase: it exploits the device straight through its ADB debug bridge for root access to the filesystem.

Once a phone is exploited, use connect <phone_ip> to access its filesystem. Phones may contain:

  • Crypto wallets
  • Authentication tokens
  • Contacts and messages
  • Sensitive files relevant to missions

Use phish to run social engineering against phone users on the same LAN. Phishing sends a crafted SMS to the target and tries to harvest their credentials.

Command What it does
phish --list List available phishing templates
phish <phone_ip> --template <name> Send a phishing SMS to the target

The templates trade success against detection:

Template Base success Per tier Heat Notes
password_reset 60% -8% +0.15 Fake IT password reset. High success vs low-tier targets.
package_delivery 50% -6% +0.10 Fake shipping notice. Moderate success, lowest detection.
calendar_invite 55% -7% +0.12 Fake meeting invite with a harvesting form.
ceo_urgent 45% -10% +0.25 Impersonate an executive. High risk, high reward vs lower staff.
mfa_expired 65% -9% +0.20 Fake 2FA re-enrollment. Best base rate, highest detection.

Requirements:

  • You must be connected to the target’s network.
  • The target must be a discovered phone on the same LAN.
  • One attempt per phone per session, so choose your template carefully.

Running mitm on the target phone first grants a +15% success bonus.

Outcomes: on success, the captured username and password are saved for cross-server reuse. On failure, the target reports the message to IT and an investigation is created against you.