Skip to content

Co-op (MeshLink)

MeshLink is the crew relay system for cooperative operations. Form a crew of 2-4 operators and take on Crew Operations, coordinated domain breaches that no solo operator could pull off.

Open MeshLink from the desktop or start menu. From the LOBBY tab:

Action What it does
Create Crew Name your crew, choose visibility (Friends Only or Public), and start hosting
Invite While hosting, COPY INVITE CODE shares your crew code, or STEAM INVITE opens the Steam overlay
Browse When offline, scroll to BROWSE PUBLIC CREWS to discover open lobbies, then hit REFRESH to scan
Join Crew Enter a lobby ID, accept a Steam invite, click JOIN on a browsed crew, or enter a host’s LAN IP (e.g. 192.168.1.5) to connect directly
Leave Disconnect from the crew. Personal progress (wallet, hardware, properties) is preserved

Lobby visibility is set when you create a crew. FRIENDS ONLY lets only Steam friends see and join (the default for private sessions); PUBLIC lists your crew in the Browse list for everyone, so you can find random operators.

Tab Purpose
LOBBY Create or join a crew, browse public lobbies, invite via code, Steam, or LAN
CHAT Real-time IRC-style crew chat with timestamps and voice push-to-talk controls
MISSIONS Host generates crew operations; all members review the briefing; host accepts or rerolls. COPY TO NOTEPAD drops the whole briefing into Notepad for every operator
OPERATION Live objective tracker during an active breach: progress, detection %, cancel button (host only)
CREW Member cards: handle, role (HOST/PEER), heat, connected server, exploit count, BTC balance, and copyable BTC address

The host’s world becomes the shared world. When you exploit a server, crack a password, or discover a node, it syncs to all crew members automatically.

Shared (syncs to crew) Local (stays per-player)
Exploited servers, cracked passwords, privesc vectors BTC wallet and balance
Web sessions, discovered servers, crew trust Hardware rig (thermals, wattage, noise)
Downloaded files, purchased software, BTC price Properties/safehouses, proxy and bounce chains

Your routing is your own. A crewmate running proxychains --clear cannot touch your chain, and theirs is invisible to you. Your chain still travels with any command the host runs on your behalf, so the target logs your exit node rather than your address. Each operator gets a unique in-game IP address (128.32.18.22 through 128.32.18.25), shown in the CREW tab and in server logs when you connect.

Crew operations are multiplayer-exclusive domain breach missions, available with 2 or more operators online.

  1. The host opens the MISSIONS tab and clicks GENERATE OP.
  2. An operation briefing appears: target entity, domain, gateway, tier, objectives, reward.
  3. All crew members review the briefing in the MISSIONS tab.
  4. The host clicks ACCEPT to start, or REROLL for a different target.
  5. MeshLink switches to the OPERATION tab with live tracking.
  6. The target gateway’s LAN is revealed and the crew moves in.
  7. Complete all objectives before the detection meter hits 100%.

Objectives are all-or-nothing: root every LAN device, exfiltrate target data, and clean ALL logs across ALL servers. An email briefing also lands in your inbox: [CREW OP] Breach <entity>.

Crew Targets LAN devices Payout
2 operators Tier 1-3 4-6 2.5x
3 operators Tier 2-4 6-8 4x
4 operators Tier 3-5 8-10 6x

The host can pin a Hardcore operation to Tier 5-6 and forbid an easier substitute. (In Wargames it pins Tier 6 exactly.) Expect IDS on everything.

There is no hard timer. A detection meter tracks how visible the crew is to the target’s security operations center, filling from 0% to 100%. At 100% the operation fails and an investigation starts against the crew. Every 30 seconds the meter adjusts:

Change Cause
+0.5% per check Ambient SOC monitoring (unavoidable baseline)
+1.5% per server per check A dirty server (uncleaned logs)
+4.0% per investigation per check An investigation triggered
-1.0% per check The trail goes cold, whenever NO target is dirty and no new investigation opened

A dirty server is any target IP (gateway or LAN) still carrying log entries the crew added. Entries that were already there when the operation was accepted are not charged: they predate the job, so an old breach of yours does not tax a new contract.

The decay line is the only thing that turns the meter around, and it is all or nothing. One server you never clean means the meter can only ever climb, and a standard operation has no timer, so detection becomes the only way it can end. Clean every box and the meter walks back down on its own. Investigations cost four times what a dirty server does and are charged the moment they open, regardless of which operator triggered one: a peer’s scan counts exactly as much as the host’s.

To keep detection low:

  1. Clean every server as you finish with it, using logcleaner --ip <your_ip>. The surgical form takes no trace penalty, works at user level, and also sweeps the gateway you pivoted through and your proxy chain, so one command covers the whole trail you left on that box.
  2. Never use hydra: it opens an investigation every time, no roll involved. Crack a shadow file with john and use ssh instead, which rolls no IDS check.
  3. Scan quietly. On Tier 6, nmap default is caught about 55% of the time, -sS about 22%, -sN about 5%. This applies to every operator, not just the host.
  4. Exploit from inside. Running metasploit while connected to the gateway cuts its IDS chance by a quarter.
  5. Keep heat below 5.0, or the game opens investigations for you.

The reward and the crew bonus are added together and split evenly between every operator. Nobody is paid more for doing more. The bonus is earned by the crew as a whole, from what the operation achieved:

Bonus Earned for
+0.025 BTC Per server rooted
+0.010 BTC Per file exfiltrated
+0.015 BTC A wallet.dat recovered from any target
+0.050 BTC Clean sweep (the clean-logs objective completed)
+0.030 BTC First blood (the first root of the operation)

On success a debrief email lands in your inbox: the crew’s score itemised, the payout and its split, and what each operator personally did (roots, first blood, log cleans) with the points those were worth.

Commands fall into three groups, and which group a command is in decides where it runs:

Group Behavior Commands
Local only Reads nothing shared, changes nothing help, ls, cd, cat, searchsploit, analyze, balance, all Unix commands, mc/meshchat, and your own routing commands (proxychains, bounce, tunnel)
Local, then synced Runs on your machine, pushes the result to the crew nmap, scan, connect, disconnect, download, upload, the IoT tools, miner, infect
Routed to the host Writes the crew’s shared record metasploit, hydra, john, linpeas, winpeas, sudo, runas, kexploit, sqlmap, phish, mitm, logcleaner

Log cleaning runs on the host because that is where the authoritative logs live. Your proxy chain and pivot path travel with the request, so the host attributes the work to you and not to itself.

Command What it does
mc <message> Send a chat message to the crew (alias: meshchat)
crew --list List all crew members with role, IP, and heat
crew --status Show crew status and active operation progress
crew --kick <handle> Kick a member (host only)
crew --leave Leave the crew

The CHAT tab is an IRC-style channel with timestamps. System events auto-post:

[MESH] n3ur0 breached 45.12.88.1 (root)
[MESH] WARNING: Detection meter at 34%
[MESH] zer0day cracked 3 passwords on 192.168.1.50
[MESH] !! FEDERAL RAID DETECTED !!

Each operator’s handle is drawn in its own colour so a four-way conversation stays readable; yours is green, matching the CREW tab, and colours hold for the whole session. Voice defaults to open mic, which latches: press TALK or F4 to go live, press again to close. It stays open while you type (F4 is used because a letter key would be swallowed by the command line), and your mic is never opened until you press something. Push-to-talk is available in Options under Audio if you prefer to hold. The MIC button mutes your input without affecting what you hear; the Microphone and Crew Voice sliders control the two directions separately.

If the host disconnects, the crew automatically migrates to a new host within seconds. The operator with the lowest player index takes over, and you see:

[MESH] MESH RELAY INTERRUPTED: REROUTING...
[MESH] MESH RELAY RESTORED

All shared state (exploited servers, operation progress) is preserved through migration, because the host takes periodic state snapshots.

Ready to compete instead of cooperate? See Wargames (CTF).

Mesh Mail is your in-world encrypted email client, with INBOX, SENT, COMPOSE, and CAMPAIGNS tabs. Mission offers and updates, fed raid warnings, trust milestones, and ambient news and market bulletins all land in your inbox. The terminal shortcut mail checks the inbox without opening the app.

COMPOSE takes file attachments, and this is how you deliver stolen goods. Many exfil contracts are closed by emailing the file to the client as an attachment, not by any terminal command:

  • Data theft, surveillance tap, phone exfil
  • Credential harvest, comms intercept, market manipulation

Attachments come from your local files: something you downloaded off a target, a SIGINT dossier, or a Cobalt exfil. Attach it, send it to the client, and the contract closes.

The COMPOSE tab lets you set the FROM line yourself, so you can write to a target’s corporate address under any name. The message lands unread in that person’s real mailbox, where you will see it when you RDP into their workstation (Outlook, Thunderbird, Outlook Express).

About one send in three draws a reaction: most often an out-of-office auto-reply that leaks their job title, direct line and a covering colleague to chase next; sometimes a short human reply. A spoofed FROM makes a wary reply likelier, but answers still reach you (Reply-To). A handful of probes is free; spray a whole company and a DLP alert fires to their security team, with heat. This is pure recon: the intel feeds OSINT and social engineering, with no terminal command of its own.

The CAMPAIGNS tab runs phishing email campaigns against a target’s people (tiers 1 to 2). See OSINT, Phishing & Rivals for the full campaign workflow.