Reborn in 2010, the AI ​​in my mind is too powerful.

Chen Yiran is not a very bold person, especially now that he is making more and more money, he is becoming more and more cautious and cherishes his life as a wealthy man.

He didn't even want to hire bodyguards because he felt he couldn't trust them at all. He felt it was more dangerous to be a group of armed men who hadn't even undergone a background check.

So since moving to Silicon Valley last year, Chen Yiran and Jasmine have been building a comprehensive defense system. Initially, it was a rudimentary "3000 Deadly Defenses" system, which basically consisted of various defenses in their home.

Then, the scale was escalated layer by layer, becoming increasingly outrageous, eventually leading to Chen Yiran's greatest work after his rebirth.

Of course, it should be said that it was Jasmine's work. Jasmine had accumulated enough knowledge and combined it with her own perception in Chen Yiran's mind to write the first program that could be called an intelligent agent.

It possesses basic learning abilities, but because current computing power cannot compare to the future, it's hard to say it has any intelligence, and it's not even like Doubao, which can chat with you and make you happy.

However, in today's online world, it can wreak havoc everywhere, infiltrating without leaving a trace.

Chen Yiran's task for him was to infiltrate without leaving a trace, targeting everything it could reach. He named it the Man-Eating Flower, because he believed that if enough were planted, they could devour any enemy that tried to approach.

Low-level defense simply waits at home; high-level defense first invades the entire globe.

The carnivorous plant's initial mission was to infiltrate the entire Silicon Valley, then the entire Bay Area, and subsequently the entire California police network. After that, it targeted various government and banking systems.

The carnivorous plant splits everywhere, controls computers, and acquires botnets (computers that have been controlled).

Two months later, the carnivorous plant began using the computing power of the botnet computers, and its splitting and intrusion became faster and faster, affecting not only nearby information.

The man-eating flower has already infiltrated major government departments across the United States. After all, too many people work from home using VPNs, and many people don't pay much attention to physical isolation. If you give the man-eating flower a chance, it will take root in various internal networks.

Chen Yiran set up many keywords to ensure that he would discover any company that was associated with him.

After establishing the company, Chen Yiran instructed Jasmine to add all company employees to the surveillance list. This wasn't just about monitoring them, but also about monitoring who was in contact with them.

So when the red-haired weirdo Robert was looking for a headhunter, the information had already been pushed to Chen Yiran's phone.

The headhunting firm had also been hacked long ago. The headhunter's request for documents triggered an alarm, and the carnivorous plant traced all related phone numbers upwards according to the procedure, intercepting the call records. Within two hours, Chen Yiran had grasped the whole picture.

Two days later, while Amit was still at work, his bank information was illegally accessed.

Chen Yiran realized that Amit was Xin Si's target. Sure enough, subsequent CCTV footage showed that someone had begun tailing Amit. All information about Amit's family began to be investigated.

Chen Yiran could have ended this farce on the spot, but he felt it was better to give the other party a weakness, or rather, to give Amit a chance to prove himself.

He was very satisfied with the final result; Amit ultimately did not do anything foolish.

If Amit really did something wrong, it would be quite troublesome. Chen Yiran would feel uncomfortable if his family wasn't implicated, but he couldn't bring himself to harm a seriously ill child.

Chen Yiran opened his laptop, ready to take revenge: "He's ruthless, so I'll be ruthless too. Come on, Jasmine, think of some tricks to secretly kill him."

Let me state my requirements first: it must be completely impossible to discover, so that the other party will not feel like they are being hacked.

I don't want them to be unable to find me; I want them to not even bother looking for me and just assume it's bad luck. After all, whoever benefits is a suspect, and I don't want to be one.

"Don't worry, I already have three brilliant plans to take them down stealthily. The first plan is to attack their financial system. We've already hacked into Synaptics' internal network and checked the directory. Although the financial system is on a separate server, it's also connected to the internal network."

We can secretly modify their tax software, changing a single word in the formula section for the R&D tax credit declaration in their first quarter's electronic tax return, changing the label for separate federal and California calculations to a combined calculation.

This doesn't affect any monetary figures; they definitely declared R&D expenditures. However, this formatting will cause the IRS's automated screening system to classify Synaptics as a federal and California consolidated claim when scanning it.

The merged format will cause the IRS system to consider that the same batch of hours is being used for both federal and California credit calculations, which constitutes double reporting. The IRS will then determine that Synaptics has falsified its hours allocation.

Synaptics' legal department has to deal with an IRS audit, and all engineers in the R&D department will be required to fill in their work hours records for the past three years, which is disgusting. Even if nothing happens in the end, it will still severely drain their energy.

"Are you sure it won't be discovered that someone changed their information?"

No, the logs of tax return modifications can be deleted without leaving a trace. Besides, this form has already been submitted to the IRS; it's just that the IRS review process is very long, and it hasn't been reviewed yet. If we modify the IRS version as well, NewThink will only assume it was a mistake by the finance staff.

"Sigh, the poor accountant probably won't be able to find a job after this. Let's see who takes the blame in the end and find a way to help them get lucky. Strategist Jasmine, what brilliant plan is in the second secret bag?"

[Second strategy. Let's start from their internal network and take a look at their baseline data. We can be very careful, for example, changing 3.14159265358979 to 3.14159265358981.]

This will result in occasional failures in 2% of the tests, and the difference is so small that the impact is completely unpredictable, making it impossible for them to pinpoint the problem. In the end, they will have to rebuild the baseline data, which itself will take a month or two.

After rebuilding, we can simply repeat the same method to ensure they continue to encounter problems. Furthermore, the underlying data is automatically accessed by the code after a task is submitted; I won't leave any trace, so they'll never know they've been doing useless work.

"What a brilliant strategist! You're truly a first-rate, ruthless villain. What about the third plan?"

Thank you for the compliment. The third point is my trump card; it can directly cut off NewThink's escape route.