But Joe doesn’t need code execution. He just needs fragments . “Every video call is encrypted. But the metadata? The frame sizes, the timestamps, the bitrate spikes when she’s upset? That’s all plaintext. OpenH264 is open-source — beautiful, transparent, and mine to abuse.” He watches Beck’s call with Peach Salinger. No audio yet, but he sees the I-frames (full images) and P-frames (differences from previous frames). When Peach says something sharp, Beck’s video freezes, then stutters. Joe notes the timestamp.

Later, he replays a corrupted P-frame: half of Beck’s face, her eyes red from crying. “That’s not video. That’s a cry for help. And I’m the only one who knows how to decode it.” ACT TWO: THE CIPHER

Joe Goldberg polishes a glass display case. On the counter, a laptop screen glows. A tiny green icon in the corner reads: .

Joe has rigged a Raspberry Pi to the bookstore’s Wi-Fi. He exploits a known weakness in OpenH264’s reference software — a memory corruption bug (CVE-2016-1234, fictionalized). The patch log reads: “Decoder may allow remote code execution via crafted SEI messages.”