Skip to content

Residential Networks

Beside the 250 corporate gateways, every person in the world is a home-broadband subscriber. A home is a real target: pivot from a company to an employee’s house, loot it, and pivot back into the company through their work laptop. Residential networks are single-player only.

Step How
Find the home IP ISP customer DB, a reverse lookup, or a SIGINT lead
Get in the home modem (a real CVE per vendor skin), or the occupant’s weak password
Loot the NAS: disk-image backups, a password export, sometimes a wallet
Pivot back the work laptop’s cached corporate account, then the company VPN

A home always exists as data, but its modem and LAN are only built the moment you reach for the IP. Three ways to get that IP:

  • The ISP customer DB. sqlmap --dump the ISP’s customer_db box, or use its OSS console.
  • A reverse lookup. host <name> or a PTR lookup.
  • SIGINT. The Signal Decoupler names the ISP and city; the ISP paths then give the IP.

With one home address in hand, sweep its block (nmap <prefix>.0/24) to list the other exposed modems on that block by model and firmware, without touching the ISP. Homes are off the world map on purpose and can only be reached by an IP you obtained; once reached, they show in NETMAP with their local network.

Most providers hand out a public address, but the fixed-wireless and satellite ISPs keep their customers behind carrier-grade NAT. Those homes do not answer from the open internet, and a /24 sweep of their range comes back empty. To reach one you have to be inside the provider first: on one of its boxes, or on a line of your own on its network. Reverse lookups for a carrier-NAT home only resolve through the provider’s own DNS box; from outside they read as NXDOMAIN.

Device What it is
HOME_MODEM The home gateway. Real-vendor skins, each with a real CVE; its admin panel is reached with hydra --url
NAS The jackpot: backup shares with a disk image, a password export, sometimes a wallet
Home PC The occupant’s desktop
Cameras RTSP streams
Smart-home hub A dashboard for the house

A soft home is a flat LAN. A hardened home, with an IT or security person living there, adds a pfSense firewall, VLANs and an EDR-protected work laptop.

The PC and the NAS share one weak occupant password: get it with hydra or john, then ssh or RDP in. The router and the hub keep their own weak factory default: try the obvious login, or hydra --url.

A hardened home’s work laptop caches the employee’s real corporate account:

  1. Root the laptop.
  2. Run invoke-mimikatz (or john) to recover the credentials and the VPN profile.
  3. vpn --add vpn.<corp> <user> <pass>, then vpn --connect, and the corporate LAN appears.

The connect writes a corp-side log you can clean: scrub it with logcleaner --ip.

The ISP’s customer_db box also serves an operator console in the browser (nmap and the dump point you at it). Open it from any foothold on the ISP, or sign in at the web gate with a weak NOC default or hydra --url.

It gives you a searchable subscriber directory (each row shows the home IP), a per-subscriber lawful-intercept connection fingerprint, and two actions with teeth:

  • Suspend line: a blackout of about 6 game hours. The home is unreachable until it restores or you lift it: a denial or diversion play.
  • Provision rogue line: stands up an ssh foothold inside the ISP that survives a reload, a persistent way back in.

Both raise heat and land in the Audit tab, which is the box’s real log: clean it with logcleaner --ip before you disconnect.