KX-series security droids,^[1] also known asKX-series enforcer droids,^[3]KX enforcer droids,^[18]KX units,^[19]KX droids,^[20] orexecutor droids,^[21] were a model ofsecurity droid manufactured byArakyd Industries that was in service to theGalactic Empire during theGalactic Civil War.^[1]

Description[]

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

―R0-GR^[20]

KX executor droids had an intimidating stature.

KX-series enforcerdroids were a model ofsecurity droid manufactured byArakyd Industries for theGalactic Empire. They had a black-colored body designed with exaggeratedhuman proportions but with the mobility of a humanathlete. They were able to operate a variety of tools, equipment andweapons and could carry gear without becoming exhausted, such as ablaster.^[9] Their size and strength made them intimidating and unsettling to many people, both Imperial andrebel alike.^[22] The shell that encompassed the droidscognitive module in their head,^[9] as well as their fists,^[23] was made out ofcarboplast-composite. Their upper legs had shock absorbing struts and their ring joints in their knees included aservo driver. Complexgyro-balance system kept them walking upright. They came equipped with a built-in comm package, recharge port, and adata spike hidden in their fist that allowed them to connect with standard communication frequencies for areas they were assigned to. TheImperial crest was imprinted on the side of each shoulder,^[9] one of which could be emblazoned in gold if the droid had received an enhanced status.^[24]

While theImperial Senate had prohibited the creation ofbattle 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 organicsentient lifeforms. The droids were programmed to recognize and defer toImperial Military officers ranked lieutenant or higher.^[9] KX units were also equipped with chest-mountedolfactory sensors, providing the security droids with an efficient "sense" of smell.^[13]

The KX-series droids were programmed to speak and interact with people, but were not as proficient at it asprotocol droids were. They could handle a wide range of tasks, including escorting dignitaries, protecting important people and defendingImperial installations.^[2] However, they could also fail to understand certain statements by processing them as orders meant to be taken literally.^[25] Nevertheless,Baron Espis Zanchal owned aservice droid that resembled^[26] the KX.^[7] Beyond security purposes, KX-series droids could serve in manual labor and translating, although the droids' programming made them find these tasks tedious. KX-series droids were pre-programmed in the operation of more than forty Imperialtransport vehicles, but were capable of quickly adapting to new ones.^[22]

The Security Droid Enforcer was more challenging in combat than a standard KX-series security droid.

A variant of this model existed by9 BBY,^[27] known as theSecurity Droid Enforcer, sporting tan plating rather than black. Like somescout troopers, these counterparts were equipped withelectro riot batons, combined with a reinforced chassis, making them far more dangerous than the standard model. They were primarily designed to trainstormtroopers in the use of the electrobaton.^[12] Oneservice droid model used the modified head of a KX-series unit.^[28] That same modified head design was used in amonster droid model.^[29]

History[]

Encounters with a Jedi[]

"Visitation is not permitted."

―A KX-series security droid, toCal Kestis^[14]

A large group of KX-series security droids from the Imperial garrison of Ilum was destroyed by Jedi Cal Kestis.

The droids were deployed as early as18 BBY,^[30] and served high-ranking Imperials.^[24] They were also used to guard Imperial installations, such as theImperial Refinery inKashyyyk, the mining headquarters onIlum and theFortress Inquisitorius onNur. During hismission to Ilum to find akyber crystal and build a newlightsaber, theJedi Cal Kestis confronted and destroyed a large group of these droids.^[14]

In9 BBY,K-4O5, aSecurity Droid Enforcer, led Kestis to Imperial SenatorDaho Sejan onCoruscant. 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 toPartisan 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.^[12]

Rebels and other insurgents[]

"I have carried out many Imperial directives prior to my reprogramming. Killing, maiming, kidnapping, arson, telemarketing. My orders were usually intended to do harm to the Rebel cause, is that what you mean?"

―K-2SO, during a mandatory psychological check-in^[31]

A KX-series security droid was present onCorellia among a trio ofstormtroopers during theheist on Corellia.^[32]

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

In5 BBY,^[33] several KX droids were stationed on the beaches ofNiamos alongsidecoastal defender stormtroopers^[25] during theImperial occupation.^[34] Six KX-series security droids participated in theGhorman Massacre, where they were used by the Empire against protesters demonstrating against the Imperial presence on theplanet. One of those units^[35] was designatedK-2SO,^[7] who was damaged afterGhorman Front operative,Samm, hit it with a vehicle, and salvaged by rebel agentCassian Jeron Andor,^[35] which would lead to K-2SO's reprogramming^[36] and service against the Galactic Empire.^[7]

During theGalactic Civil War, they were present on bothJedha and theImperial facility onScarif.^[7]K-4D8 was an example of these droids.^[24] At least one KX-series security droid was stationed aboard anImperial II-class Star Destroyer.^[37] Around1 ABY,^[38] theastromech droid R2-D2 staged arescue of his friendC-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.^[37]

Also around that time,^[39] a KX-series security droid was among the forces that detainedDoctor Chelli Aphra and hercrew onSkako Minor. Caught in an explosion caused by aFlufto, one of Aphra's genetically-modifiedtookas,^[40] the droid was destroyed but auto-transmitted footage of the events unfolding upon deactivation. The footage was captured by Imperial scanners and was sent toInspector Magna Tolvan, having tripped several active search filters set by Tolvan. Tolvan and acorporal reviewed the posthumous transmission and associated location data, providing them a lead on Aphra's location.^[41]

A machine with the head and torso of a KX-series security droid was constructed by theTarkin Initiative but ultimately frozen and put into storage aboardHivebase-1, where it was found by Aphra, her crew, andHera Syndulla.^[42]

Threats from within and without[]

In3 ABY,^[38] a KX-series security droid was present aboard the Imperial II-class Star DestroyerExecutor. Whenbounty hunters Boba Fett andBeilert Valance infiltrated the destroyer in an attempt to rescue thecarbon-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 hispalm blaster, causing it to question whether Valance himself was a droid before thecyborg fired a second blast, incapacitating the Imperial machine for good.^[43]

At least two KX droids who managed to think for themselves were part of theSecond Revelation.^[15] Two KX-series security droids were present in thecity ofKantiema onBrentaal IV at the time of thebombing orchestrated byJul Tambor and caught in the ensuing blast.^[44] Another two KX droids were among those formerly wronged byDarth Vader and rebuilt in an effort to take revenge on theSith Lord as part of thedroid uprising.^[16]

KX-series security droids and DT-series sentry droids infected by Scourge on Ryloth.

Sometime after theBattle at Amaxine Station, four of these droids were transported to theAmaxine Space Station aboard aSentinel-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 theScourge, a being born of theSpark Eternal^[8] and adroid dropped by theFermata Cage.^[45] Upon returning to anImperial 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.^[8] The Scourge used a number of KX units as bodies on the Star Destroyer^[46] and began to carve into one to alter the droid's body.^[47]

Waning Empire[]

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

Between4 ABY and5 ABY,^[48] KX-series droids armed withE-22 reciprocating double-barreled blaster rifles were deployed to the surface of^[11] the besieged^[49] world ofMandalore,^[11] a world which hadlong resisted Imperial rule^[50] and, in response, was targeted^[51] with a "Great Purge" to exterminate theMandalorian people. In the so-called "Night of a Thousand Tears," after ImperialTIE/sa bombers had wiped out^[11] Mandaloriancities,^[52] KX units picked through the wreckage and eliminated any survivors they uncovered with the help ofviper probe droids.^[11]

Imperial Refining Platform M36 hosted no organic life-forms, and was instead guarded solely by KX-series security droids armed withE-11 blaster rifles andT-21 light repeating blasters. The platform's security force was dispatched byJedi Knight Luke Skywalker when the Rebellion launched araid on the facility.^[10]

Beyond the Empire[]

Following thedefeat of the Empire, theNew Republic elected to use the KX-series for its own security.^[17] In9 ABY,^[53] the modified KX-series security droidK-A0S participated as aHunter in theHunters of the Outer Rim competition on the planetVespaara.^[54]Decades later,^[55] theB1-series battle droid-turned-authorR0-GR recorded details about the KX-series security droid in his "droidography."^[20]

Behind the scenes[]

KX-series droids were developed for theStar Warsanthology filmRogue One: A Star Wars Story. Their firstcanonical appearance was inStar Wars: Commander. They later appeared in the ambiguouslycanonStar Wars: Visions.

The following section contains information fromStar Wars: Visions media that was referenced in no othercanon source.Lucasfilm has stated thatVisions stories and their related media are not required to "tie into the larger chronology" ofStar Wars storytelling. Editor discretion is advised.

At some point between1 ABY and5 ABY, a KX droid accompanied anImperial officer when he raided a club on the occupied worldB-bel to intimidateLoi'e, but the rebels were able to escape.^[56]

Star Wars: Visions information ends here.