Bulgaria  China  Taiwan  Czech  UK  France  Germany  Indonesia  Italy  Japan  Malaysia  Poland  Portugal  Romania  Russia  Spain  Turkey  Vietnam


Release the Kraken! Its monstrous tentacles come from netConnections and head straight towards the Core.
The more tentacles join together, the stronger the Kraken is.

The Kraken is a Brute Force Offensive Program which attacks nodes using the shortest possible path towards the network's Core. When there are multiple available paths of the same distance to the core, the Kraken will choose either a Turret or Black ICE with the highest firewall if available, or the node with the highest firewall if not. Wraithed nodes, as well as nodes with a Sentry antivirus do not affect target selection. If two nodes are identical, the Kraken will choose the node which was connected first by the network admin.[1]

Only one Kraken program can be installed on each netConnection in a network. They cannot be installed by the user on any other type of node, including those that the player has Portaled into.

Each Kraken program automatically installs one copy of itself on each node it captures. If the next node along its path already has a Kraken installed, their tentacles merge together and they combine their strength while still occupying only one program slot. The strength of a Kraken program on each installed node is equal to its program strength multiplied by the number of Kraken programs that have converged up to that point. As of v1.030, Kraken overwrites worms on a full node. Kraken will not overwrite any other offensive or defensive programs and will simply stop where they are.

They will continue this pattern until they capture the Core, then they will simultaneously attack all hostile nodes connected to the Core, similar to the Shuriken. As of Patch v1.011, the damage to nodes connected to the Core is equal to the Kraken's base program strength with no multipliers. Attacks from the Core do not install the Kraken onto connected nodes.

If a node with Kraken installed is recaptured, all tentacles which pass through the node will be severed and forcibly removed from all nodes after the break point. This does not directly cause any other captured nodes to be lost, even if all program slots become empty.

In this video you can see an example of a network attacked by a Kraken program.

Statistics Edit

Program Stats
(DPS 1-5x)
Research Stats
Evolver Level
1B8,00047512 Hours5
2B16,00050018 Hours5
3B32,00060024 Hours6
4B48,00070030 Hours6
5B60,00080036 Hours7
6B80,00083042 Hours7
7B100,00086048 Hours8
8B120,00090054 Hours8
9B140,00093060 Hours9
10B160,00096066 Hours9
11B180,0001,00072 Hours9
12B200,0001,08080 Hours10
13B220,0001,16088 Hours10
14B260,0001,25096 Hours10
15B300,0001,330104 Hours11
16B340,0001,410112 Hours11
17B380,0001,500120 Hours11
18B420,0001,625132 Hours11
19B440,0001,750144 Hours12
20B460,0001,875168 Hours12
21B480,0002,000180 Hours12
TotalB4,444,00023,5351,686 Hours12

Tips Edit

  • Krakens have limited use against networks that have their Core placed near their netConnections.
  • Similar to Worms, Krakens can attack multiple consecutive nodes using a single program.
  • Krakens only occupy one Program slot on any given node regardless of the number of merged tentacles.
  • Only one Kraken can be installed on each netConnection.
  • Nodes with a Portal installed do not count as a netConnection and cannot have the Kraken installed on them.
  • Kraken can save space in libraries with its duplication and on nodes with its convergence, all while consolidating power, which is particularly useful against Code Gates and other tough nodes en route to the Core.
  • On chokepoints, the Kraken will only attack one of the connected nodes, leaving the chokepoint vulnerable to any other securities. Consider bringing Shockers, ICE Walls or Shurikens along if that poses a problem.
  • It is not always best to use as many Krakens as possible - consider the placement of the core, the nodes and security in between, the level of your Kraken program and what else you could use extra disk space for when deciding how many to compile.
  • [Visual Bug] Rarely, the Kraken will appear to not be severed when one of the nodes along its path is recaptured by the network's defenses.

Trivia Edit

References Edit

  1. - Kraken Testing
Hackers Wikia - Programs List
Programs Nodes Gameplay
Offensive Programs

Battering ram Battering Ram  Ion cannon Beam Cannon  Blaster Blaster  Kraken Kraken 
Maniac Maniac  Shock Shocker  Shuriken Shuriken  Worms Worms 

Defensive Programs

Icewall ICE Wall  Protector Protector 

Stealth Programs

Access Access  Dataleach Data Leech  Portal Portal  Wraith Wraith 

A.I. Programs

Beetle A.I. Beetle  Hawk A.I. Hawk  Squid A.I. Squid 

Community content is available under CC-BY-SA unless otherwise noted.