Master Qui-Gon, more to say, have you?

It is requested that this article, or a section of this article, be expanded.

See the request on the listing or on this article's talkpage. Once the improvements have been completed, you may remove this notice and the page's listing. No reason has been supplied; please provide a reason on the template or talkpage

"Still resisting? Unwise."
―A KX-series security droid[14]

KX-series security droids,[1] also known as KX-series enforcer droids,[3] KX enforcer droids,[15] or executor droids,[16] were a model of security droid manufactured by Arakyd Industries that was in service to the Galactic Empire during the Galactic Civil War.[1]


"KX droids have a long range of combat capabilities, excellent probability analysis algorithms, and direct access to the Imperial datanet."

KX executor droids had an intimidating stature.

Arakyd Industries KX-series enforcer droids came equipped with a built-in comm package, recharge port, and a computer interface arm that allowed them to connect with standard communication frequencies for areas they were assigned to. The Imperial crest was imprinted on the side of each shoulder,[18] one of which could be emblazoned in gold if the droid had received an enhanced status.[19] The droids were designed with exaggerated human proportions but with the mobility of a human athlete. They were able to operate a variety or tools or equipment and weapons and could carry gear without becoming exhausted, such as a blaster.[18]

While the Imperial Senate had prohibited the creation of battle droids, Arakyd used a loophole in the law by marketing the KX-series as "security droids." They were programmed without the standard restriction against harming organic sentient lifeforms.[18] The droids were programmed to recognize and defer to Imperial Military officers ranked lieutenant or higher.[18]

The KX-series droids were programmed to speak and interact with people, but were not as proficient at it as protocol droids were. They could handle a wide range of tasks, including escorting dignitaries, protecting important people and defending Imperial installations.[2] However, they could also fail to understand certain statements by processing them as orders meant to be taken literally.[20] Nevertheless, Baron Espis Zanchal owned a service droid that resembled[21] the KX.[5]

A variant of this model existed by 9 BBY,[22] known as the Security Droid Enforcer, sporting tan plating rather than black. Like some scout troopers, these counterparts were equipped with electro riot batons, combined with a reinforced chassis, making them far more dangerous than the standard model. They were primarily designed to train stormtroopers in the use of the electrobaton.[9]

One service droid model used the modified head of a KX-series unit.[23] That same modified head design was used in a monster droid model.[24]


Encounters with a Jedi[]

"Visitation is not permitted."
―A KX-series security droid, to Cal Kestis[14]

The droids were deployed as early as 14 BBY[25] to guard Imperial installations, such as the Imperial Refinery in Kashyyyk, the mining headquarters on Ilum and the Fortress Inquisitorius on Nur. During his mission to Ilum to find a kyber crystal and build a new lightsaber, the Jedi Cal Kestis confronted and destroyed a large group of these droids.[14]

In 9 BBY, K-4O5, a Security Droid Enforcer led Jedi Knight Cal Kestis to Imperial Senator Daho Sejan on Coruscant. Kestis faked a capture to get closer to the senator and his starship, on which Sejan had stored Imperial military information, which Kestis intended to deliver to Partisan Saw Gerrera. K-4O5 found Kestis again after his escape and confronted him. The droid was destroyed in the fight with Kestis and his ally, Bode Akuna.[9]

Rebels and other insurgents[]

A KX-series security droid was present on Corellia among a trio of stormtroopers during the heist on Corellia.[26]


A KX-series security droid accosts Cassian Andor near Arkie's, on Pier Nine on Niamos.

In 5 BBY,[27] several KX droids were stationed on the beaches of Niamos alongside coastal defender stormtroopers[20] during the Imperial occupation.[28]

During the Galactic Civil War, they were present on both Jedha and the Imperial facility on Scarif. K-2SO[5] and K-4D8 were examples of these droids.[19] They were also present during the Great Purge of Mandalore, where they shot any survivors from the bombing runs of Imperial TIE/sa bombers.[8]


KX-series secruity droids deployed to the surface of Mandalore with E-22 reciprocating double-barreled blaster rifles in the "Night of a Thousand Tears."

At least one KX-series security droid was stationed aboard an Imperial II-class Star Destroyer.[29] Around 1 ABY,[30] the astromech droid R2-D2 staged a rescue of his friend C-3PO from the vessel, creating utter chaos throughout the ship. Aware that the attacker was a droid that had incapacitated several squads of Imperial forces, a trio of stormtroopers searching for the culprit cornered the KX-series security droid and, despite its protests, opted to destroy it.[29]

Also around that time,[31] a KX-series security droid was among the forces that detained Doctor Chelli Aphra and her crew on Skako Minor. Caught in an explosion caused by a Flufto, one of Aphra's genetically-modified tookas,[32] the droid was destroyed but auto-transmitted footage of the events unfolding upon deactivation. The footage was captured by Imperial scanners and was sent to Inspector Magna Tolvan, having tripped several active search filters set by Tolvan. Tolvan and a corporal reviewed the posthumous transmission and associated location data, providing them a lead on Aphra's location.[33]

A machine with the head and torso of a KX-series security droid was constructed by the Tarkin Initiative but ultimately frozen and put into storage aboard Hivebase-1, where it was found by Aphra, her crew, and Hera Syndulla.[34]

In 3 ABY,[30] a KX-series security droid was present aboard the Imperial II-class Star Destroyer Executor. When bounty hunters Boba Fett and Beilert Valance infiltrated the destroyer in an attempt to rescue the carbon-frozen Han Solo, the droid approached the pair and lifted Fett off his feet. Valance damaged the enforcer's head with his a shot from his palm blaster, causing it to question whether Valance himself was a droid before the cyborg fired a second blast, incapacitating the Imperial machine for good.[35]

A Sinister Peace SWDConv

A pair of KX-series security droids

At least two KX droids who managed to think for themselves were part of the Second Revelation.[11] Two KX-series security droids were present in the city of Kantiema on Brentaal IV at the time of the bombing orchestrated by Jul Tambor and caught in the ensuing blast.[36] Another two KX droids were among those formerly wronged by Darth Vader and rebuilt in an effort to take revenge on the Sith Lord as part of the droid uprising.[12]

Sometime after the Battle at Amaxine Station, four of these droids were transported to the Amaxine Space Station aboard a Sentinel-class landing craft to aid in the cleanup effort ordered by the Emperor himself. One of the units became infected after picking up a disk containing the Scourge, a being born of the Spark Eternal[6] and a droid dropped by the Fermata Cage.[37] Upon returning to an Imperial I-class Star Destroyer, the Scourge used the KX to spread itself, overwriting all droid life aboard and leading them in a murderous uprising against the organic crew. The security droid, the disk that corrupted it perched on its shoulder, later stared out the viewport on the destroyer's bridge, the Scourge reflecting on its vast knowledge, insight into the galaxy, and plans for omnipresent dominion.[6] The Scourge used a number of KX units as bodies on the Star Destroyer[38] and began to carve into one to alter the droid's body.[39]

Imperial Refining Platform M36 hosted no organic life-forms, and was instead guarded solely by KX-series security droids armed with E-11 blaster rifles and T-21 light repeating blasters. The platform's security force was dispatched by Jedi Knight Luke Skywalker when the Rebellion launched a raid on the facility.[7]

Beyond the Empire[]

Following the defeat of the Empire, the New Republic elected to use the KX-series for its own security.[13] The B1-series battle droid-turned-author R0-GR recorded details about the KX-series security droid in his "droidography."[17]

Behind the scenes[]

KX-series droids were developed for the Star Wars anthology film Rogue One: A Star Wars Story. Their first canonical appearance was in Star Wars: Commander. They later appeared in the ambiguously canon Star Wars: Visions.

At some point between 1 ABY and 5 ABY, an KX droid accompanied an Imperial officer when he raided a club on the occupied world B-bel to intimidate Loi'e, but the rebels were able to escape.[40]


Non-canon appearances[]


Non-canon sources[]

Notes and references[]

  1. 1.0 1.1 1.2 1.3 1.4 Star Wars: Commander
  2. 2.0 2.1 Star Wars: Rogue One: Rebel Dossier
  3. 3.0 3.1 Dawn of Rebellion
  4. Star Wars: Absolutely Everything You Need to Know, Updated and Expanded
  5. 5.0 5.1 5.2 5.3 5.4 Rogue One: A Star Wars Story
  6. 6.0 6.1 6.2 6.3 Dark Droids 1
  7. 7.0 7.1 7.2 Age of Rebellion - Luke Skywalker 1
  8. 8.0 8.1 The Book of Boba Fett logo The Book of Boba Fett — "Chapter 5: Return of the Mandalorian"
  9. 9.0 9.1 9.2 9.3 Star Wars Jedi: Survivor
  10. Star Wars Jedi: Fallen Order
  11. 11.0 11.1 "The Book of Ajax" — Dark Droids: D-Squad 1
  12. 12.0 12.1 Darth Vader (2020) 36
  13. 13.0 13.1 13.2 Last Shot
  14. 14.0 14.1 14.2 Star Wars Jedi: Fallen Order
  15. Per the audio description for "Chapter 5: Return of the Mandalorian" available on Disney+
  16. Star Wars Bust Collection 35
  17. 17.0 17.1 Star Wars: Droidography
  18. 18.0 18.1 18.2 18.3 Star Wars: Rogue One: The Ultimate Visual Guide
  19. 19.0 19.1 Adventures in Wild Space: The Rescue
  20. 20.0 20.1 Andor logo new Andor — "Announcement"
  21. Darth Vader (2020) 20
  22. StarWars Star Wars Jedi: Survivor on StarWars.com (backup link) dates Star Wars Jedi: Survivor to five years after the events of Star Wars Jedi: Fallen Order, which in turn take place in 14 BBY per Star Wars: Timelines. As such, Jedi: Survivor must occur in 9 BBY.
  23. TwitterLogo Raffaele Ienco (@Raffaele_Ienco) on Twitter: "Looks that way. (In response to: "ah, turns out I have another question! In Vader 37, we see some service droids with the same head design. Are these units therefore also created with modified KX-series heads?")" (backup link)
  24. TwitterLogo Raffaele Ienco (@Raffaele_Ienco) on Twitter: "Correct. And their heads are modified K2SO. (In response to: "Haha, noted! And thank you for answering! Basically curious about how I should define the crush pirates. You seem to draw them as being built out of old battle droid parts, is that correct?")" (backup link)
  25. Star Wars Jedi: Fallen Order takes place five years after the Great Jedi Purge, which is dated to 19 BBY by Star Wars: Galactic Atlas. Therefore, Star Wars Jedi: Fallen Order, in which the droids appear, is set in 14 BBY.
  26. Han Solo & Chewbacca 1
  27. "Announcement" takes place days after "Kassa," which dates itself to 5 BBY.
  28. StarWars-DatabankII Niamos in the Databank (backup link)
  29. 29.0 29.1 Star Wars (2015) 36
  30. 30.0 30.1 Star Wars: Timelines
  31. Star Wars: Timelines dates the events of issues 9 to 31 of the Star Wars: Doctor Aphra comic-book series to around 1 ABY. Therefore Doctor Aphra 15 must take place around 1 ABY.
  32. Doctor Aphra (2016) 15
  33. Doctor Aphra (2016) 16
  34. Doctor Aphra (2016) 18
  35. War of the Bounty Hunters 5
  36. Darth Vader (2020) 32
  37. Hidden Empire 5
  38. Dark Droids 3
  39. Dark Droids 2
  40. The Spy Dancer