What happened
bootstrap_rtkx() now also fetches checksums.txt from the same release and verifies the archive's SHA-256 before extraction; a mismatch or missing entry raises BootstrapError without extracting or marking executable. The fix closes basic in-transit tampering but not a forged release pipeline.
Why it matters
This is a supply-chain hygiene issue in the AI-coding-agent bootstrap path: an agent framework silently downloading and executing a binary from the network is a classic injection point an attacker can use to compromise the developer machine.
Attack vector
rtk-install fetches a prebuilt rtkx release archive and marks it executable with no integrity check, so in-transit tampering or corruption of the downloaded artifact yields execution of attacker-controlled code with the developer's privileges.
Affected systems
sammyjdev/axon before 0.1.1 (src/axon/context/rtk_bootstrap.py)
Mitigation
Upgrade to axon 0.1.1 or later, which verifies the archive's SHA-256 against release checksums.txt before extraction. This does not close the precondition of a compromised rtkx release pipeline or maintainer token — that needs signed build provenance.