Hacknet: Complete Guide

A beginner-to-completion guide to Hacknet, the terminal-based hacking sim: the core hacking workflow, port crackers, proxies, firewalls and traces, the story's factions, achievements, the Labyrinths DLC, and Extensions.

Researched September 2026 — current as of the latest official Steam posts (10th anniversary, August 2025) and community activity (the unofficial UnHacknet Jam, February 2026). The base game and Labyrinths DLC (March 31, 2017) are complete; there are no pending patches. Live games change; check the linked sources if something differs.

Quick Start

1. Type help. The in-game help lists every command you currently have, with syntax. It's the most reliable reference when you forget something.
2. The basic loop: scan to find linked machines → connect [ip] → probe to see open ports and defenses → run port crackers → porthack → you're admin.
3. Watch your RAM. Every running program takes memory from a limited pool. If you can't launch a cracker, close something (ps then kill [PID]).
4. Watch the trace timer. On protected machines, a countdown starts when you begin hacking. Disconnect (dc) before it hits zero.
5. Clean the logs. After a job, go to the target's log folder and delete the entries that show your activity. Sloppy hackers get consequences.
6. Read every email and file. The story and many "puzzles" (passwords, addresses, clues) are hidden in text files on machines you break into.
7. Don't delete system files on your own computer. A popular community guide exists purely for restoring x-server.sys after players delete it.
8. Use the Netmap and keep notes. The netmap shows known nodes; keep a record of passwords and IPs you'll need again (the game's own notes tool or a text file outside the game).

The Hacking Workflow

Port crackers

The crackers are programs you acquire over the course of the game. Each one targets a specific service:

Later in the game (and in Labyrinths) you meet more port types — the game's port table also includes 104 (medical), 6881 (torrent), 443 (SSL), 192 (Pacific), 554 (RTSP), 211 (transfer), 9418 (version control), 3724 and 3659 — each needing its own tool; the probe output always tells you which ports a machine has, and help lists what you own. You find new programs as downloadable .exe files on machines you hack — always check /bin folders and anything that looks like a tool.

Proxies

A proxy blocks hacking until it's taken down. Use shell on machines you already own to open remote shells, then have those shells overload the proxy. More shells take it down faster, but every shell costs RAM.

Firewalls

A firewall hides a password. Run analyze repeatedly to reveal it, then solve [password] to disable the firewall. Harder firewalls take more analyze passes.

Traces

• A trace starts when you hack a protected system; the speed varies per machine.
• Plan your crackers before you start, launch them back-to-back, and disconnect the moment you're done.
• Letting a trace complete has serious consequences for your own machine — reload a save or follow the in-game instructions if it happens.
• Disconnecting from a traced system with under half a second left unlocks "To the Wire".

Encrypted files

Some files are encrypted and need dedicated tools (the game introduces Decypher for decrypting and DECHead for reading encryption headers, which can reveal the originating IP). Keep an eye on emails that mention these tools.

Useful extras

Exact syntax can differ slightly from memory — help in-game is authoritative.

Story and Factions (spoiler-light)

A hacker called Bit is dead, and when he fails to reconnect for 14 days his failsafe starts emailing you instructions. The main path:

Missions come from mission boards and emails. You can often take jobs in a flexible order, but the story beats follow each other.

Achievements

There are 11 achievements, all single-player.

Tips:

• "To the Wire": pick a system with a slow trace, start hacking, and watch the timer closely. Saving just before helps.
• "PointClicker": leave it running in the background while you do other things.
• "Quickdraw": the description only says to finish the tutorial "earlier than normal" — on a new save, try completing the tutorial's objectives before the instructions prompt you, and check the community 100% achievements guide if it doesn't pop.

Labyrinths DLC

• Released March 31, 2017; a 3–4 hour additional chapter.
• You're recruited by Kaguya into a small team of elite hackers pulling data heists.
• Adds new programs, network environments and UI themes, plus the Memory Analyzer for memory forensics on RAM dumps.
• Teamwork happens through an in-game IRC channel.
• Accessed through missions from Entropy or CSEC within the main story.
• Has multiple endings based on your choices.

Hacknet Extensions and Mods

• Since May 2017, Hacknet Extensions let players build custom campaigns, networks, themes, music and missions, shared on Steam Workshop. An official Extensions guide is on the Steam community.
• Pathfinder is a community modding framework used by many extensions; the community has run jams for it (the Pathfinder Jam in 2024).
• In February 2026 a community member ran the unofficial UnHacknet Jam, focused on extensions built within vanilla Hacknet's constraints.
• Extensions are a great way to keep playing after the story — some are longer than the base game.

Common Mistakes to Avoid

• Launching crackers without checking RAM. A failed launch mid-trace wastes precious seconds.
• Forgetting to delete logs. Leaving evidence can cause trouble later.
• Deleting your own system files. Particularly x-server.sys — keep your hands off your own /sys folder.
• Not saving before risky hacks. The game saves, but make sure you have a recent save before traced jobs.
• Skimming emails. Clues, addresses and credentials are in the text.
• Getting stuck without checking help. You may already have the tool you need.

Advanced Tips

• Pre-plan the crack order. probe, then type crackers in quick succession — many players keep the terminal focused and use the up arrow to repeat commands.
• Use shells as a resource. Keep shells on several owned machines so you can overload proxies instantly.
• Kill finished programs. Crackers that have done their job still eat RAM until they close.
• Take notes on IPs. Missions often send you back to machines you hacked hours ago.
• Explore beyond the missions. Hidden servers, side content and extra tools exist for players who dig.
• Try Extensions with Pathfinder once you've finished Labyrinths.

FAQ

Do I need real hacking knowledge? No. It's based on UNIX-style commands and teaches everything, but it's a game, not a real hacking tool.

How long is Hacknet? The main story is a medium-length game; Labyrinths adds 3–4 hours.

Where do I find new programs? On machines you hack — look for .exe files, often in /bin, and in mission rewards.

How do I get past a proxy? Open shells on machines you control and use them to overload the proxy.

How do I beat a firewall? analyze until the password is revealed, then solve [password].

Is Labyrinths worth it? Yes if you liked the base game — it has harder hacks, new tools and multiple endings.

Sources

• Hacknet — Wikipedia
• Hacknet global achievements — Steam Community
• Hacknet — Steam store page
• Hacknet – Labyrinths — Steam store page
• Hacknet news (10th anniversary, UnHacknet Jam, Pathfinder Jam) — Steam
• Hacknet community guides index — Steam Community
• Hacknet Pathfinder mod framework (vanilla port table) — GitHub