Into the Breach Codexery

Vek Stinger (Venom)

Small, fast, and never alone—the Vek's favorite way to make you move.

The Vek Stinger—often nicknamed "Venom" by Golem pilots in the field—is the most numerous and most frequently encountered of the Vek's ground forces. A small, angular insectoid creature with a low-slung profile and a pair of forward-reaching mandibles, the Stinger is the Vek hive's basic skirmisher: fast, expendable, and always arriving in clusters. It is the first enemy most pilots face and the last they stop seeing, threading through the grid with a speed no other Vek ground unit matches.

In the broader Vek war machine, Stingers serve as the pressure layer. They do not break fortifications or deliver heavy blows; they swarm, flank, and force Golems to spend turns repositioning. Their role is less about killing than about controlling tempo, making them a constant, low-grade threat that defines the rhythm of every engagement.

Quick Facts

Role
Basic melee skirmisher; fast flanker
Affiliation
Vek (alien hive species)
Movement
2 tiles per turn
Attack range
1 tile (adjacent)
First encountered
Early campaign missions
Typical grouping
Appears in packs of 2–4 or more

Lore & Background

The Vek are an alien species that arrived in the Breach, a fractured zone where the world's geometry has been torn into a rigid grid. Their biology is insectoid and hive-structured: individual Vek do not think in the way Golem pilots do. Stingers, at the low end of the caste hierarchy, operate on reactive impulses—sensing heat, vibration, and the electromagnetic signature of a Golem's core. They do not plan. They pour.

Pilots who have lost a Golem to a Stinger swarm describe the experience not as a battle but as a drowning. The creatures do not charge heroically; they simply arrive from two or three directions at once, their two-tile stride letting them close the distance before a pilot can react. The mandibles are not designed to crush armor so much as to latch, to pin, to keep a Golem from reaching its next tile. It is a small, ugly, efficient violence that has no grandeur.

In the Vek's own hierarchy, Stingers are the most disposable caste. They are produced in volume, deployed in waves, and expected to be destroyed. The Vek do not mourn them. This is, in its own alien way, a kind of respect: the hive values the function, not the individual, and the Stinger's function is to be everywhere at once.

Reader's Guide

The Vek Stinger moves 2 tiles per turn, making it the fastest ground enemy in the campaign. It attacks only in the adjacent tile (range 1), so it must close to a Golem before dealing damage. There are no special abilities, charge attacks, or conditional modifiers—its entire design is speed plus numbers.

In early missions you will face one or two Stingers alongside a Masher or Spitter. Their speed lets them swing wide around a Golem's facing, threatening the tile behind you while the heavier unit pins you in front. By mid-campaign, Stingers appear in groups of three or four, sometimes split across two flanks, forcing you to choose which threat to address first. In late-game and Boss missions, Stinger packs can number six or more and are layered with other Vek types, creating multi-directional pressure that punishes any Golem that stays stationary.

Because Stingers have low hit points, a single well-placed Golem attack can eliminate one, but their two-tile stride means they can often reposition out of your reach on the same turn they appear. The core counter-play is to use terrain, Masher bodies, or Spitter range to create a corridor, then intercept the Stinger on its second tile of movement before it reaches your Golem. Never let two Stingers converge on the same tile from opposite sides—that is the pattern that kills Golems.

Did You Know?

What players say: Player verdict on Into the Breach — Rotten Tweets

More in Enemies & The Vek

Elsewhere in Into the Breach

Spotted an error? Know more?

Reader corrections go straight into our review queue. Suggest an edit · How this site is sourced

Comments

Loading…
Open in the interactive codex →