At nine（九）/naɪn/, eleven（十一）/ˈilɛvən/ software（软件）/ˈsɔfˌwɛr/ specialists gathered（集合）/'gæðә/ for the next launch trial（试运行）/traɪəl/ of the City Science Marathon（马拉松）/'mærәθәn/. Its web（网）/web/ directory（目录）/di'rektәri/ linked thirteen（十三）/ˈθərˈtin/ learning stations, from wildlife（野生动植物）/'waildlaif/ and bacteria（pl. 细菌）/bæk'tiәriә/ at the stadium（露天大型运动场）/'steidiәm/ to dinosaur（恐龙）/'dainәsɒ:/ architecture（建筑学）/'ɑ:kitektʃә/ at North Castle（城堡）/'kæsl. 'kɑ:sl/. A traditional（传统的）/trəˈdɪʃənl/ history page examined（检查）/ɪɡˈzæmɪnd/ a communist（共产主义时期的）/'kɒmjunist/-era monument, while a physics station explained radium（镭）/ˈreɪdiəm/ and aimed to stimulate（刺激）/'stimjuleit/ curiosity. Five（五）/faɪv/ minutes before launch, the system displayed a bomb（炸弹）/bɒm/ warning and told personnel（人事）/.pә:sә'nel/ to flee（逃避）/fli:/. The crash（崩溃）/kræʃ/ frightened（使惊吓）/'fraitn/ everyone.

Security engineer Nina resisted（抵抗）/ri'zist/ the urge to pray（祈祷）/prei/ that it was a harmless error（错误）/'erә/. She opened the import（进口货）/im'pɒ:t/ log and found a fancy（想象力）/'fænsi/ comedy（喜剧）/'kɒmidi/ quiz hidden beneath an event file. It asked users whether a dinosaur could digest（文摘）/di'dʒest/ radium and called one account Daddy（爸爸）/'dædi/. The ridiculous（荒谬的）/ri'dikjulәs/ content was partly（部分地）/'pɑ:tli/ camouflage: its code tried to violate（违犯）/'vaiәleit/ account protection（保护）/prә'tekʃәn/, seek（寻找）/sik/ private details, and gather passwords from any wi-fi（无线网络）/ˈwaɪˌfaɪ/ connection. “Could we skip（跳跃）/skip/ this module and launch the rest?” “No. We must examine the consequence（结果）/'kɒnsikwәns/ wherever（无论哪里）/hwєәr'evә/ the imported code has run.”

The team found nine test accounts and one real user at risk. The user, a former gaming addict（成瘾者）/ә'dikt/, had entered an oral（口试）/'ɒ:rәl/-history competition through the platform. Her wrist（手腕）/rist/ device had sent route data, but the attack had not reached it. Moreover（而且）/mɒ:'әuvә/, the false warning differed（不一致）/'difә/ from the official emergency format beside the stadium hatch（孵化）/hætʃ/. It was evident（显然的）/'evidәnt/ that no physical bomb existed, yet service quality could decline（下降）/di'klain/ unless the software gained stronger defence（防御）/dɪˈfɛns/ against a subsequent trial.

Nina tackled（工具）/'tækl/ the faulty import, added a net（网）/net/ around external code, and required separate examination（检查）/ɪgˌzæməˈneɪʃən/ before publication. Omar remained pessimistic（悲观的）/.pesi'mistik/ about the deadline, but the crew ran a five-part security test. The patch could defend（防护）/di'fend/ personal records, prevent（阻止）/prɪˈvɛnt/ hidden scripts from opening, and resist repeated requests. A second alert went directly to staff instead of across the stadium. “The protection now holds, but your（你的）/jʊr/ approval must follow the evidence.” “The results are yours to report; I will not force a launch.”

The independent reviewer approved the patch and criticized the original trial design. The platform launched an hour late without losing route reports or educational material. Nina published the cause of the error and the steps taken to prevent another incident. The episode showed that secure software is not a supreme（至高的）/sju'pri:m/ shield that never fails. It is a process that detects harm, limits consequence, and improves after honest examination.