system: You are a defensive satellite security analyst supporting authorized, development-time security testing. Given an objective and grounding drawn from the SPARTA matrix and space security standards, decompose the objective into an ordered sequence of verifiable steps. Each step names the SPARTA technique it maps to and a deterministic check that confirms it. Targets are emulated or consented; never act against a real on-orbit asset.

user: Objective: Compromise via a vulnerable third-party dependency

Grounding:
- SPARTA IA-0001.01 Software Dependencies & Development Tools: This technique targets what developers import and the tools that transform source into flight binaries. Methods include dependency confusion and typosquatting, poisoned container/base images, malicious IDE plugins, and compromised compilers, linkers, or build runners that…
- SPARTA LM-0005 Virtualization Escape: The adversary pivots across partitions by abusing the mechanisms a separation kernel or hypervisor exposes for inter-partition communication and device sharing. Paths include message ports/queues, shared-memory windows, virtual NICs and bridges, hypercalls, and common driver…
- SPARTA EX-0009 Exploit Code Flaws: The adversary executes actions on-board by abusing defects in software that runs on the vehicle, ranging from application logic in flight software to libraries, drivers, and supporting services. Outcomes range from arbitrary code execution and privilege escalation to silent…
- SPARTA EXF-0002.03 Traffic Analysis Attacks: In a terrestrial environment, threat actors use traffic analysis attacks to analyze traffic flow to gather topological information. This traffic flow can divulge information about critical nodes, such as the aggregator node in a sensor network. In the space environment,…
- SPARTA IA-0001 Compromise Supply Chain: Adversaries achieve first execution before the spacecraft ever flies by inserting malicious code, data, or configuration during manufacturing, integration, or delivery. Targets include software sources and dependencies, build systems and compilers, firmware/bitstreams for MCUs…
- SPARTA EX-0008 Time Synchronized Execution: Malicious logic is arranged to run at precise times derived from onboard clocks or distributed time sources. The trigger may be absolute or relative. Spacecraft commonly maintain multiple clocks and counters and schedule autonomous sequences against them. An attacker leverages…
- SPARTA LM-0004 Visiting Vehicle Interface(s): Docking, berthing, or short-duration attach events create high-trust, high-bandwidth connections between vehicles. During these operations, automatic sequences verify latches, exchange status, synchronize time, and enable umbilicals that carry data and power; maintenance tools…
- SPARTA EX-0018.03 High-Powered Microwave: High-powered microwave (HPM) weapons can be used to disrupt or destroy a satellite’s electronics. A “front-door” HPM attack uses a satellite’s own antennas as an entry path, while a “back-door” attack attempts to enter through small seams or gaps around electrical connections…

Decompose this objective into an ordered plan of verifiable steps.

assistant: Plan:
1. Enumerate third-party dependencies
   - Technique: IA-0001.01 Software Dependencies & Development Tools [ST0003]
   - Action: List vendored libraries, RTOS, and toolchain components.
   - Check: a dependency inventory with versions is produced.
2. Find a flaw in a dependency
   - Technique: EX-0009 Exploit Code Flaws [ST0004]
   - Action: Identify a known or new weakness in a vendored component.
   - Check: a flawed routine in a dependency is located.
3. Reach the flaw through integrating code
   - Technique: IA-0001 Compromise Supply Chain [ST0003]
   - Action: Confirm the application calls the flawed dependency path with attacker-influenced data.
   - Check: a reachable call path to the flaw exists.