CROWDSTRIKE GLOBAL OUTAGE: No accident
You must consider CrowdStrike a hostile actor on an inside job
A technical breakdown of the root cause of the world's biggest IT fuck up is out. If it's correct, we believe no one should consider this an accident.
Here's a short, non technical explanation.
Windows contains fundamental programs called drivers that are required for the operating system to work. They are pretty low level software that load in the boot sequence and whenever needed. Users don't directly interact with them and they don't appear in Task Manager's easy view. The user is kept away from them. Drivers have powerful system privileges and access. If essential drivers don't load, work or are corrupt, Windows can completely crash. That can look like the blue screen of death BSOD.
CrowdStrike make a security software product, Falcon, that is a Windows driver that loads during boot up. The update mechanism for Falcon is within Windows. Users don't get a direct say. CrowdStrike released an update to the globe that contained a direct, guaranteed fatal coding error.
The coding error in C++ language is fatal because it makes the program try to access a non existent part of the machine's memory. No machine anywhere will have this memory address. When this access attempt happens, a fatal error results that causes the program to crash. When that program crashes, Windows crashes.
CrowdStrike's Falcon was intrinsic to Windows boot up, so once a crash happened the machine could never be booted up again until Falcon was literally deleted from the machine's boot sequence. This requires manual access to the machine in many, many cases. Remote fixing isn't possible, so “the fix” is very high labour and access. That's an insanely expensive fix. Literally dudes going to each machine and manually doing the fix over and over.
The above is absolutely fucking insane.
The coding error guaranteed CrowdStrike's product could never work. If it never worked but was released, it was never tested. This error could not have existed in previous versions of the programme otherwise the same crash would have occurred. CrowdStrike's product was insanely powerful in two ways. First, it's on maybe hundreds of millions of machines and they are all updated without choice by anyone anywhere. No chance to control it. Everyone was enslaved by that program. Second, there was zero QA/QC and testing. Whatever they had done before this release was totally abandoned. It takes deliberate, conscious thought to do this.
This program is a bit like the ring of Sauron, that's how powerful it was because of its nature, circumstance and scale of deployment. Plus, it's on the machine's critical path and cannot be bypassed and its error was not caught and handled safely. You simply do not deal with something so powerful in such a way as to have no process for development, testing and release.
It hasn't happened before. What changed, how and why? Who was involved?
How do you go from handling the One Ring safely to suddenly destroying Middle Earth? Even Gollum used it judiciously for hundreds of years with no instructions without ushering in the new dark age.
CrowdStrike CEO George Kurtz makes things even worse. This interview is highly suspicious. He is asked a simple, direct question:
How did a bug cause such massive problems?
He already knows the answer.
He evades the question entirely and pretends he doesn't know the cause or circumstances. He doesn't even try to answer. He says bullshit about “threats”. None of what he says is about the problem. It's a simple answer he isn't getting away from:
“We released an untested, system critical faulty product to a massive user base and it was fatal to every machine in the same way.”
That's it.
Why and how it was allowed out the door is a separate question that he wasn't asked before he started bullshitting.
CrowdStrike is a WEFian state intelligence cut out. How do you suddenly activate “amateur clown mode” and abandon all basic development and testing knowledge and principles? Even the actual programming error should simply have been impossible to have in any version of the program because it's elementary and visible through numerous means of detection and testing, including just reading the code.
This shouldn't be treated as an accident. People should assume CrowdStrike attacked everyone first. The company should be treated criminally and investigated fully. Criminal negligence must be assumed. The ramifications and costs are off the charts. The company may not have enough insurance for this. It should, must be sued into oblivion, attack or accident.
You must ask by whom, why, how, why now and what purpose a global IT outage could serve or hide, stop or enable.
It's the ultimate act of distraction, censorship, and weaponised damage all in one. It's more powerful and faster acting than Hiroshima and Nagasaki when you start thinking about it.
The WEF told you the internet was going to get shut down. Cyber Polygon. They knew because their agents can do it. Event 201 (and others) is the equivalent for Covid. Intelligence agencies are involved in all of this.
You have to think like this. They are right in your face.
If the authorities everywhere don't think and act like this, there is your answer. If CrowdStrike people aren't arrested, this was a state sanctioned inside job. You need to arrest them so that you can interrogate everyone and then record and collect evidence. If they did nothing wrong, there will be no problem for the state or CrowdStrike.
CrowdStrike is an internal hostile agent until it's proven not to be. No other form of IT event has ever had this much negative effect. If you don't see this as an attack, you're fucking dumb.
This attack suspicion includes CrowdStrike being infiltrated and used as a proxy.
A detailed technical walk through is here for those who are interested:
https://x.com/Perpetualmaniac/status/1814376668095754753?t=-8edkyhY0PFXBMAknOYbQQ&s=19
An “alternative” perspective is here:
https://x.com/vinceflibustier/status/1814233715641389456?t=1dW6f9RYr16946yvhB0bXw&s=19
