Font Size
15px

Aiden worked with JoAnna, Sophia, Felix, Michael, Oni, and Zack on understanding the current situation and figuring out the most effective way to tackle it. Noah also joined online several tis, to coordinate resources from the Army of Chaos.

Because Eve is down and drones lost their Eve-driven capabilities, Noah assigned more manpower to guard strategic points of the Army of Chaos, and they prioritized other locations.

Several ships owned by Long Industries which are on the ocean reported failures and Noah assigned n from the Army of Chaos to accompany chanics from Long Industries to go and check them with helicopters.

"The biggest problem is that new locations are showing up." Zack said while rubbing the back of his neck.

Aiden agreed with Zack. "I can't believe that it's less than one hour since we started tackling this ss. It feels like days…"

They all looked at the map of the Los Angeles and surrounding area and all the dots which showed where the locations of interest are. Colors indicated if the location was visited, if the n are assigned, or if it's still pending to be checked. And Zack is right. Steve, Charlie, and Jeff are sending them updates every fifteen minutes, adding more locations to the list.

"These two are important, and there is a technology failure." Felix said while pointing at two dots. "I will go to one, and Nico and Beck can go to the second one."

Sophia frowned. "What? You are staying here."

Felix frad Sophia's face with his palms and looked into her eyes which simred with concern. "Ma chéri, I will go with bodyguards. These locations need to be checked by soone who understands hardware. I can do it, and I believe that Nico and Beck are capable. Everyone is doing their part. I will be careful…"

On the lowest level…

Sarah was typing fervently while isolating modules of code. She wants to get help from the Sigma army mbers, but she does not want to give them access to everything. Her plan is to give them specific parts, and then to tackle the problem with a divide-and-conquer strategy.

It didn't take her long to separate code by functions and to get on the call with Mishi, Lucija, Petar, Emir, and Teresa.

"These are parts of my pet project." Sarah vaguely explained. "Soone corrupted it. I hope that you can help figure out what happened."

"Of course." Mishi assured Sarah in his usual calm and collected tone. "Tell us what we are working with."

"You are looking at modules that I developed with a goal to create an assistant. It is on a number of servers, and all of them are on my internal network which is heavily secured. Other than and Aiden, no one has access. Even for , it would take a lot of effort to access it without knowing the passwords and protocols. I don't know who got in, or how he did it, and that is where you co in."

"Do you think that it was a targeted attack?" Lucija asked.

Sarah thought about how to answer this. "Only a handful of people knew that this exists. And other than and Aiden, no one is skilled in coding."

"Is it possible that it's Aiden?" Tereza asked reluctantly.

Sarah's whole body stiffened. If Aiden betrayed her, her heart would stop on the spot. "No. I trust him with my life and with my code."

Tereza smiled ekly. "Sorry, I had to ask."

Sarah exhaled and relaxed slightly. "It's OK. I am tense because this was one of my most guarded secrets and if soone got their hands on it, who knows what else they've got."

"You are saying that the person who did this is either very skilled or very lucky." Petar said.

"Or maybe a mix of skills and luck." Lucija said and added: "Sarah could be a target because she is the owner of Ceresc Solutions. Or maybe they wanted to use her to access her brother-in-law who is the CEO of the White corp. Or maybe they targeted Sigma and Oga. There are so many options."

Emir was looking at the modules and mumbled: "This looks like speech recognition… and this one reminds of reading heat signatures... Self-learning?" He paused for a second, reminding himself to stay focused. He easily gets distracted with random chatter, and this is important. This is the first ti that Sarah called them, asking for them to help her out. That is why Sigma's army was ford and it's his ti to shine.

"Is it possible that so function was revealed? Maybe the hacker knew about one thing, and the rest was luck?" Emir asked.

Sarah shook her head. "Even if the hacker knew about one function or all of them… Knowing about the interface and getting access to the code behind it, are two different things."

Emir bobbed his head. "I am a hardware expert. And I can tell you that I can get into things without knowing what is inside. Also, every system has entry points. What are your entry points? Maybe you think of this system as sothing that will handle automated ssages on your phone, but that tells how your phone is an entry point and that I can send my scripts to your server through your phone."

Sarah knows that Emir makes sense. She rembered ear-studs and bracelets and Eve-lens… But they have a clear policy that if anyone misplaces an item, it needs to be reported imdiately. She will ask Nala to do a count of equipnt, just in case.

Sarah swiftly typed a ssage to Nala and mumbled: "Thanks for the idea, Emir. I need to think about possible entry points. If you can figure out how code got corrupted, maybe you can reverse-engineer the virus and that could be the clue to who did this."

"Whoever did this, targeted you and Aiden." Lucija said.

Sarah shook her head. "It's not only us. Aiden's brother, Jeff, and several other friends are facing issues with their companies. I'm asking you to look into one piece of the puzzle."

"Everyone leaves traces. We will find them." Mishi said. "We will get on this right away and we will keep you updated with the progress."

Sarah was grateful. "Thanks. You are the best. Ping if you have any other questions as you work on this."

Sarah got offline and rubbed her face forcibly. Her Sigma army mbers got independent modules to inspect, and Sarah has the biggest chunk.

She took a minute to think about their conversation and the current situation.

Jeff, Charlie, and Steve got attacked at the sa ti as Eve. And there is a flood of negative traffic online. That requires money, skills, planning, manpower… Who can pull that off? In order to get an answer to that question, she needs to figure out how those people got information on White corp., Smithsonite corp., Long Industries, and most importantly, on Eve. So information about those companies is available to the general public but so is restricted.

Sarah was frustrated. There are so many unknown things!

Sarah took a deep breath and told herself to focus on Eve, she is the only one who can tackle this task, and soone else can look into the information leak. But who is that 'soone else'?

Aiden is the next person who is good at gathering information and analyzing it, but he is busy. Other than him… there is no one else with enough knowledge or access to tackle all this. Ah, they need more people! Soone top-notch. Sarah rembered how when she needed help with Mr. Patel, she recruited Phoenix and Viper. But she used them already and… Sarah's eyes widened when she rembered one person. Her father gave her a number, and Sarah stored it.

Sarah got her phone and made a call.

---

If you are not reading this at 'W e b n o v e l .. c o m', then the content you're reading is stolen! Please support the author by reading this novel from the original source.

You are reading Is this destiny? Chapter 1692 - Under Attack (4) on novel69. Use the chapter navigation above or below to continue reading the latest translated chapters.
Share with your friends
Library saves books to your account. Reading History saves recent chapters in this browser.
Continuous reading

You may also like

The Alpha's Bride cover
Same author

The Alpha's Bride

RedSonia ·Action

AlphaDamon,theunmatedAlphaofthelargestpackinNorthAmerica,isfacingarealitywhereEldersarepressuringhimtomarryabrideoftheirchoice.Amarriageofconvenien...

No reviews yet. Be the first reader to leave one.
Please create an account or sign in to post a comment.