Cassian reprograms an Imperial KX droid into K-2SO

During the events around the Ghorman Massacre and the growing rebel effort, a damaged KX-series Imperial security droid came into rebel hands. Cassian transported its components to Yavin 4, where technicians rebuilt it for the Alliance.

Official image of K-2SO, the former Imperial security droid who joined Cassian Andor.
Illustration note: Official image of K-2SO, the former Imperial security droid who joined Cassian Andor.
Date
2 BBY
Continuity
Canon
Setting
Rebel base, Yavin 4

Chronology note: The year is well established, but separate plotlines in the same year may not have an exact relative order. Every page distinguishes published narrative facts from anthropological interpretation.

An Imperial machine captured

During the events around the Ghorman Massacre and the growing rebel effort, a damaged KX-series Imperial security droid came into rebel hands. Cassian transported its components to Yavin 4, where technicians rebuilt it for the Alliance.

A second social identity

Reprogramming freed the droid from the violent security instructions under which its Imperial counterparts operated. The resulting K-2SO developed a blunt, sometimes unwelcome manner of speech and formed a durable partnership with Cassian.

Practical help for the rebellion

K-2SO offered strength, mobility, access to Imperial security routines and a capacity to improvise during infiltration. Later missions brought the pair to Coruscant, the Ring of Kafrene and finally Scarif.

Anthropological assessment

The story treats software and institutional ownership as central to a droid's lived identity. A machine constructed for surveillance and physical coercion can become a valued participant in a community organized around resisting those functions.

Interactive history lab

Was K-2SO created as a rebel droid from the beginning?

No. He was an Imperial KX security droid who was captured, rebuilt and reprogrammed.

Compare the historical event, institutional decision-making, and cultural consequences.

During the events around the Ghorman Massacre and the growing rebel effort, a damaged KX-series Imperial security droid came into rebel hands. Cassian transported its components to Yavin 4, where technicians rebuilt it for the Alliance.

Sources and evidence

Andor Season 2 Episode 9; StarWars.com K-2SO Databank. Read related source material →.

Canon · 2 BBY · Public opposition

K-2SO joins the Rebellion

Historical sequence and evidence

During events linked to the Ghorman crisis, an Imperial KX-series security droid fell into rebel hands. Cassian later brought it into the Alliance's orbit, where it was reprogrammed and came to be known as K-2SO. Its subsequent cooperation with Cassian should be understood as a change of relationships and operational duties, not a retroactive claim that the droid always worked for the Rebellion.

Political authority and collective identities

The conversion of an Imperial security machine into an independent companion asks how systems built for control can be repurposed. Its memory, physical body and programmed functions had military origins, but its later actions depended on new experiences and an altered place in a social group.

IDS original historical diagram about K-2SO joins the Rebellion
Original IDS conceptual infographic. Character portraits on the page are contextual illustrations.
Original narrative and source qualification

Andor season two and Rebels depict these events within 2 BBY. Their chronology is fictional and differs from the episodes' publication dates. The linked original source provides context and does not imply that promotional art depicts the complete event.

Original Lucasfilm episode or character source →

Test the historical evidence

Both questions give a score, corrections and explanations of the source record.

1. What sort of droid was K-2SO originally?
2. Had it always served Cassian?