Page 32 of Rescuing Ally: Part 2
“Everywhere they went.” The picture crystallizes in my mind. “Everything they touched. What else failed soon after?”
“Our phones,” Gabe interjects, stepping forward. “Remember? Right after Ally plugged her USB drive into her laptop. Both our phones started draining faster than normal.”
I nod once, the memory precise.
Everything Ally, Malia, and Malikai touched after returning from Kazakhstan subsequently malfunctioned.
Doc Summers frowns, her expression shifting as she accesses a memory. “There’s something else. The medical scanners.”
“What medical scanners?” Forest asks, turning toward her.
“The ones we used during the initial assessment of the Kazakhstan survivors,” she explains, her words gaining momentum. “They weren’t catastrophic failures, just—glitches. Calibration errors. Signal dropouts. I thought it was just equipment fatigue from the field deployment.”
“When was this?” I ask.
“Immediately after extraction,” she replies. “On-site, before transport back to HQ. Standard medical protocol for all rescued hostages.”
“That would make the medical scanners patient zero,” Mitzy says, already updating her timeline. “Even before they arrived at Guardian HQ.”
“They were packed back up with the rest of our gear and haven’t been anywhere else. The likelihood of them transmitting whatever this is to other systems is virtually nil. However, Guardian Grind and Ally’s computer and the connection with Malikai all point to the fact that each one of them was an epicenter of spread.”
“What about the other rescuees from Kazakhstan?” Walt asks.
Doc Summers shakes her head. “None of them came to Guardian HQ. They went to The Facility, where they were processed, treated, and offered standard rescue services. Ally, Malia, and Malikai were the only ones who came here.”
“Which means whatever is causing this came back with them from Kazakhstan.” I look at Gabe. Ally. Our Ally. Used as a vector for Malfor’s infiltration.
“Mitzy,” Sam says, “gather all potentially affected devices. Full forensic analysis. Isolate and destroy.”
“I don’t think isolation protocols are necessary,” Mitzy says, already moving. “If these devices are carrying something, it’s already spread throughout our systems. It’s better to examine them in their current state. Not to mention, we shouldn’t destroy anything until we know what we’re dealing with.”
“Get it done.” Sam accepts Mitzy’s expertise.
I’m like Sam. I want to burn everything to the ground, but what Mitzy says makes sense. The first step in destroying an enemy is understanding them, and there’s a lot we don’t understand right now.
Hours pass.
Mitzy’s lab is a fortress of advanced technology. She gathers equipment and sets up diagnostic systems. Ally’s laptop sits on the central workstation, surrounded by our phones, the register component from Guardian Grind, and circuit boards from various failed systems throughout the facility.
“If there’s something embedded in these devices,” Mitzy explains as she initializes the diagnostic sequence, “it has to be microscopic. Our standard security scans would have caught anything larger.”
I watch as she methodically scans the laptop’s components. Power regulation system. Battery connection points. Circuit boards. Nothing appears unusual at standard magnification.
“Nothing visible at baseline,” Mitzy mutters, frustration evident in her voice. “This doesn’t make sense. Something is affecting these systems, but I can’t find any physical or digital evidence.”
“What’s the maximum resolution on that scanner?” Gabe asks, his eyes fixed on the display.
“Standard electronic microscopy tops out at around 10,000x magnification,” Mitzy responds, “but we rarely need to go beyond 1,000x for component analysis.”
“Push it higher,” I instruct, a hunch growing despite the lack of visible evidence.
She gives me a questioning look but complies, adjusting the equipment. “2,000x… 5,000x… still nothing but standard electronic components.”
“Keep going,” Gabe insists, leaning forward, hands braced on the workstation.
“Interesting.” She increases magnification, zeroing in on what appears to be corrosion along one of the connection points.
“What’s that?” I ask.
Table of Contents
- Page 1
- Page 2
- Page 3
- Page 4
- Page 5
- Page 6
- Page 7
- Page 8
- Page 9
- Page 10
- Page 11
- Page 12
- Page 13
- Page 14
- Page 15
- Page 16
- Page 17
- Page 18
- Page 19
- Page 20
- Page 21
- Page 22
- Page 23
- Page 24
- Page 25
- Page 26
- Page 27
- Page 28
- Page 29
- Page 30
- Page 31
- Page 32 (reading here)
- Page 33
- Page 34
- Page 35
- Page 36
- Page 37
- Page 38
- Page 39
- Page 40
- Page 41
- Page 42
- Page 43
- Page 44
- Page 45
- Page 46
- Page 47
- Page 48
- Page 49
- Page 50
- Page 51
- Page 52
- Page 53
- Page 54
- Page 55
- Page 56
- Page 57
- Page 58
- Page 59
- Page 60
- Page 61
- Page 62
- Page 63
- Page 64
- Page 65
- Page 66
- Page 67
- Page 68
- Page 69
- Page 70
- Page 71
- Page 72
- Page 73
- Page 74
- Page 75
- Page 76
- Page 77
- Page 78
- Page 79
- Page 80
- Page 81
- Page 82
- Page 83
- Page 84
- Page 85
- Page 86
- Page 87
- Page 88
- Page 89
- Page 90
- Page 91
- Page 92
- Page 93
- Page 94
- Page 95
- Page 96
- Page 97
- Page 98
- Page 99
- Page 100
- Page 101
- Page 102
- Page 103
- Page 104
- Page 105
- Page 106
- Page 107
- Page 108
- Page 109
- Page 110
- Page 111
- Page 112
- Page 113
- Page 114
- Page 115
- Page 116
- Page 117
- Page 118
- Page 119
- Page 120
- Page 121
- Page 122
- Page 123
- Page 124
- Page 125
- Page 126
- Page 127
- Page 128
- Page 129
- Page 130
- Page 131
- Page 132
- Page 133
- Page 134
- Page 135
- Page 136
- Page 137
- Page 138
- Page 139
- Page 140
- Page 141
- Page 142
- Page 143
- Page 144
- Page 145
- Page 146
- Page 147
- Page 148
- Page 149
- Page 150
- Page 151
- Page 152
- Page 153
- Page 154
- Page 155
- Page 156
- Page 157
- Page 158
- Page 159
- Page 160
- Page 161
- Page 162
- Page 163
- Page 164
- Page 165
- Page 166
- Page 167
- Page 168
- Page 169
- Page 170
- Page 171
- Page 172
- Page 173
- Page 174
- Page 175
- Page 176
- Page 177
- Page 178
- Page 179
- Page 180