BBN, July 22, 2024 – Biden DROPS OUT, Crowdstrike TICKING TIME BOMB warning
|
Time
Text
Wow, wow, wow.
Thank you for joining me.
Mike Adams here, Bright Town Broadcast News from Monday, July 22nd, 2024.
There's so much going on.
It's unbelievable.
Welcome to the broadcast today.
Of course, Joe Biden has officially dropped out of the presidential re-election race, and he has apparently endorsed Kamala Harris, which many of us find to be Quite interesting.
There's also new information coming out about the CrowdStrike outage, and it turns out, and I got this information from Zach Voorhees, who I'll be interviewing here today.
It turns out that there was actually a kind of data time bomb that was already planted on all those servers, and it just got activated, okay?
So this was not actually the system file update rollout that caused this issue.
This is what's coming out now.
This was a cyber...
Let's call it a roadside bomb, or an IED, improvised explosive device.
Yeah, let's call it a cyber IED that was already in place.
A time bomb on all these servers that just got activated, and it begs the question, how many more time bombs are already in place?
We're going to find out today.
With our interview with Google whistleblower Zach Voorhees.
So that interview is coming up.
The other thing I want to show you here before we get back to Joe Biden, check out this image.
This is the image of the concentric circles.
A listener sent this image and I want to thank that listener, whoever it was.
These are the concentric circles of various distances that are overlaid onto the Trump podium.
From the attempted assassination of Donald Trump.
And it shows some very interesting things.
If you look at the image here, notice that the first concentric ring is the orange ring.
And that is 450 feet.
And that ring intersects the top of the roof of the building on which the first shooter, Crooks, was believed to be stationed.
Don't you find it interesting that my initial audio forensic analysis conducted like the next day had estimated the distance of the shooter, the first shooter at 452 feet, I believe.
And it turns out it's right there.
It's about 450, you know, give or take.
But what else is interesting here is if you look at my recent graphic showing the first eight rounds that were fired at that event based on the forensic audio analysis, and I think I showed you this previously.
But rounds one, two, and three came from something probably 450 feet away.
And those three rounds sound the same.
And those are very likely the rounds that were produced by crooks.
Almost certainly.
That seems to be the case at the moment.
Rounds four, five, six, and seven...
Have a very, very different sound signature.
They're clearly not from the same shooter, not the same location, not the same distances for rounds six and seven.
In fact, there are some other recordings from the shooting that took place where you can clearly hear a very different sound signature on rounds four, five, and six, and seven.
And even you can hear more echoes because it was taken...
Those shots came from a very different location.
My guess is that rounds four and five came from now, I'm guessing the second floor open window of the building just to the northwest of the first building where Crooks was supposed to be on the roof.
And I've got, I have a video for you about that.
I'll see if I can play a little bit of that.
There was a wide open second floor window.
And there was a Secret Service shooting team inside that building, and it looks like they took shots 4 and 5.
Shots 6 and 7, as you can see from my chart, were taken from, well, number 6 is 600 to 700 feet away.
So if we go back to the concentric circles that...
A listener provided, and that would be the kind of light orange line, the mustard-colored circle, I should say.
It shows the most likely origin of that would be from one of the taller buildings just to the north of the building on which Crooks was located.
And it turns out there are some second-story buildings there.
That building complex, as I understand it, is AGR. I forgot the exact name, a glass company, Glass Research, something like that.
And there are some second story buildings there.
It appears to me again that shot number six came from 600 to 700 feet away.
And then shot number seven now, if we go all the way out to number seven, we have to get to the outer rings.
Which is kind of an aqua-colored ring.
And that shows us, let's say, 1,100 to 1,500 feet out.
And from that, there are no buildings that I can see that are tall enough, although perhaps this needs to be looked at more closely.
I'm not fully familiar with the topology and the elevations of this entire building.
But there could have been somebody in an elevated position much farther out, farther than the water tower.
Now, the water tower has been an item of great interest, and if you look at this concentric circle map, the water tower appears to be 800 feet away or just under 800 feet.
Given also the fact that the water tower is higher, so there's a lot of elevation there, you would actually consider that to be more than 800 feet in terms of the bullet drop, by the way, because the bullet is traveling along the hypotenuse of the triangle.
Yes, I'm going to bring in ninth grade geometry here, you know, just to rub all our noses in it and remind us that we should have paid attention when the teacher said, hypotenuse?
What in the heck is that?
Well...
The bullet travels along the hypotenuse, not along the ground, if it's fired from the top of the water tower, right?
And the hypotenuse, as you may recall, remember the Pythagorean theorem and all that?
The sum of the squares of the sides, you know.
Yeah, the hypotenuse is longer than just the ground distance.
So the ground distance is 800 feet.
From the water tower, but the hypotenuse from the top of the water tower is more than that.
Maybe, let's just guess, 800 and 50 feet?
I don't know exactly.
It's not the same as the ground distance plus the elevation of the tower.
That's not the case.
Those would be the two square sides of the triangle.
The hypotenuse, well, I'm not going to geek out, but just go look up the Pythagorean theorem if you want to calculate the hypotenuse.
You just need the elevation of the water tower.
So anyway, questions still remain, obviously.
And notice that the government is not telling us how many rounds were fired by crooks.
Notice that.
Oh, and by the way, back to my chart, round number eight is the round which was 15.8 seconds after the very first round.
And round number eight is believed to be the only round fired by Secret Service.
See?
See how wild that is?
So we can clearly hear seven rounds and then about a 10 second gap and then one final round that apparently killed Crooks.
At least that's based on our current best estimates.
So who shot the seven rounds?
Who shot seven rounds?
Did Crooks fire seven rounds?
If he did, how did he teleport?
To a farther distance before he fired round six?
Or how did he teleport to a different location before he fired rounds four and five because they have a very different sound signature?
So if you are to believe the current official government explanation for this shooting, then you have to believe that 20-year-old kids can teleport like an X-Men.
There's like an X-Men superhero character that can teleport.
And it's like a demon creature.
It's a blue demon that can teleport.
It leaves behind a residue of sulfur.
Kind of like Hillary Clinton.
No, I'm kidding.
It leaves behind a residue of sulfur.
If you believe in superheroes, X-Men, like mutant capabilities of teleportation and laser eyes and whatever...
Then, yeah, maybe the government's official explanation is possible, but otherwise it's not.
But back to the questions here.
The government has not told us.
To my knowledge, I don't think they've released the details on the rifle.
Maybe they have, but I missed it.
But I would like to know the rifle.
I'd like to know the optic.
If it had an optic, I've seen people claim it's a 1X optic, which means no magnification.
That would have made that shot more difficult, but not impossible for sure.
I would have preferred a 3x optic on that rifle, by the way, for that range.
That would have made it a lot easier.
We don't know how much brass has been recovered from the roof or the gutter or, you know, right, maybe it fell off the roof, but all that brass should have been recovered by now.
That would be very easy to find.
And what about the bullets themselves?
They should have already been recovered as well, and yet we hear nothing.
We hear nothing from the government because a cover-up is underway.
This is a massive cover-up of a criminal conspiracy to assassinate Donald J. Trump.
And by the way, Secret Service Director Kimberly Cheadle is rumored to be resigning today.
Maybe by the time you hear this, she will have already resigned.
And our friend Ivan Raiklin said that the moment she resigns, she should be criminally charged and prosecuted for her involvement in this attempted assassination.
Again, this is a deep state assassination attempt that follows all the same patterns of the JFK assassination and even the Martin Luther King assassination.
You know, this is, they take out the guy that they want to silence.
They have a patsy That was recruited.
And then he gets killed, so dead men don't talk.
And then they cover up the truth in the media.
They gather all the evidence at the FBI, and then they bury it.
The FBI is involved in a criminal cover-up.
And this time, perhaps the first time in American history, this time the deep state looks like they're going to get caught.
Because there's already so much evidence that has come out that they can't cover up.
That points to multiple shooters.
Some people are saying two shooters.
Senator Ron Johnson is even saying now two shooters.
I'm going to play that video for you.
But there are others like myself who are saying there are at least three shooters.
Just because the audio forensic analysis clearly, in my view, clearly shows that there are three shooters.
There might be more than three.
But we know this is not a lone shooter.
So now I'm going to play for you a little bit of this interview with Senator Ron Johnson on Fox News, talking about the second shooter and some other lapses in Secret Service.
So understand, you've never seen this before in history, where a senator begins to question the official narrative in the way that you might have only seen from people like Alex Jones or myself years ago.
Previously, you were never allowed to question the The official narratives on shooting events.
But now U.S. Senators are questioning it.
So give this a listen.
My staff immediately started reaching out to local law enforcement.
We've gathered a fair amount of information.
Again, we're just scratching the surface.
But, you know, a couple of things that we found out, for example, the Secret Service did not even attend the 9 o'clock security meeting with local law enforcement.
Pretty well put in charge the Butler County law enforcement to coordinate things.
Law enforcement wasn't even on the same channel.
Just to be clear, Senator, that was a 9 a.m.
meeting on July 13th, the day of the shooting.
Correct.
Secret Service wasn't there.
Secret Service was better for site visits.
Weren't even there.
You kind of turned over some of the outer perimeter stuff to local law enforcement.
They weren't even on the same security channel.
So the sniper and SWAT teams weren't on the same channel as the patrol officers, and they were on the same channel as the Secret Service.
So they had to relay things.
One of the things we found out is that we've got a more detailed timeline.
This picture is now on the internet, but a photo was taken by the local sniper team in the AGR building at 514 of Crooks.
So, again, we had pictures of this guy.
Why wasn't he intercepted?
There's so many unanswered questions here.
The pictures were taken at 514 and he was shot at 611.
Correct.
So I'm going to be issuing a preliminary report.
Again, it's preliminary.
It's just scratching the surface.
We're primarily going to release that report to solicit more eyewitness testimony.
If you took video, save it.
Make a backup copy.
We can glean things in terms of audio and in terms of where the shots go.
Came from.
Was it one rifle?
Was it more than one?
I've seen some pretty interesting video on the internet by experts that certainly calls into question what the FBI is telling us about a single shooter.
Again, we're only just beginning this, but it is so important that people who saw things that have information, they preserve it, they memorialize what they saw because memories change.
Over time, they can be influenced.
So, again, it's good news.
On a bipartisan basis, Chairman Blumenthal and I are dedicated to taking transcribed interviews with law enforcement and members of the general public that were at that rally.
No matter how insignificant your piece of information might be, it might lend to provide the full story of what happened, because the American public needs to understand what happened here.
Alright, so there you go.
Senator Johnson asking the questions that need to be asked.
And look, folks, they're going to interview everybody who was there.
They're going to get copies of cell phone footage.
There's more yet to come out.
There's going to be cell phone footage of people even before Trump started speaking.
There's going to be things, pieces of this puzzle, data points that will be fit together in the coming weeks that are going to be shocking.
It's going to come out that there was more than one shooter.
Guaranteed.
That is now irrefutable.
And if the FBI sticks to the one shooter story, they will completely discredit themselves because there's clearly more than one shooter.
The fact that this is coming out, again, first time in American history that a false flag operation has unraveled because of the woke administration.
And the ubiquitous presence of mobile phones and people recording video and the FBI's inability to confiscate all of that footage.
They were not able to do that.
I don't even think they tried to do it this time.
For the first time in history, the grassroots people are going to solve this shooting and it's going to expose the United States government.
The federal government was involved in This was an inside job.
This was a deep state assassination coup attempt.
And it failed.
It's blowing up in their faces.
And now they're going to become even more desperate than ever before.
So we're going to watch out for what they're going to try to pull next.
And this CrowdStrike cyber attack time bomb may have been part of that, actually.
But I want to bring your attention now to another video from, let's see, it's from a YouTube channel called Legally Armed America.
I'm shocked that YouTube is even allowing these videos on their platform.
A few years ago, they would have just pulled these down, but I guess they just can't stop the flood of videos at this point.
So it's called breaking.
Evidence suggests second gunman involved in Trump assassination attempt.
And the analyst here reveals that there was a wide open second floor window of a building just to the northwest of the Crooks rooftop building.
So let's take a look at that.
You know, I discovered from video from Sky News, a helicopter video, that there's a second floor window.
That perfectly lines up with that trajectory.
And not only is there a second floor window, but the video footage clearly shows that that second floor window is open.
And so now if we go to slide number seven, you can see in that red dotted rectangle, that that window is open and anyone can go to Sky News helicopter video showing Crook's body and as the helicopter swings around it's very clear to see that the window opens outward and the glass and the frame of the glass are indeed opened outward and so that kind of shocked me because common sense would say that you wouldn't want to leave
an elevated window So,
this second floor, Open window, that's exactly what a sniper team would use, because they don't want to shoot through the glass.
So a sniper team, let's say a deep state sniper team, that is there to assassinate Trump and to blame it on a Patsy, they would have set up several feet inside the second floor window there, in the room, in darkness, so that the sun wouldn't hit them.
I mean, I don't know the angle of the sun relative to this building, but I think that window faces south, actually, so the sun could have come into the room.
So they would be out of the sun, and they would have their range and everything ready to take out Trump as soon as crooks open fire.
And in fact...
That appears to be exactly what they did.
So if you go back to my ballistics chart, the forensic audio analysis, Crooks fires rounds one, two, and three, and then there's about a two and a half second pause, or a little over two and a half seconds, almost a three second pause.
During that pause is probably when this team on the second floor got the go, go, go command.
Like Crooks has opened fire, you know, go ahead, take out Trump.
That's probably the order they got.
They fire off rounds four and five, which are very close together, indicating there may have been two snipers.
Inside that window on the second floor.
Because there's only.3 seconds between those rounds.
Unless they had a semi-automatic, which I guess is possible, it would have indicated two bolt-action rifles.
Yeah, it could have been one semi-automatic, somebody squeezing off two rounds back-to-back.
But that's highly unusual for a precision shot.
I mean...
I can squeeze off, you know, five rounds a second, right?
I mean, I've, you know, I've timed it.
And that's just a regular semi-automatic AR-15.
Well, with an improved trigger, I should add.
So, yeah, five rounds a second can be done.
But you don't do that when you're taking a precision shot, right?
You would take one round and then you would re-aim carefully.
You'd probably take it at least, you know, one and a half to two seconds before you'd fire off another round.
That's not what happened.
Rounds four and five seem to have appeared in quick succession.
And they're also at about the same distance as crooks.
So you see how this all works now?
All the audio forensics is actually burying itself out here in, you know, in the topology of the environment.
So again, rounds 1, 2, and 3 fired by crooks, and then the assassination team in the second floor with the open window, they open fire with rounds 4 and 5.
And then rounds 6 and 7, we don't know where those came from.
I'm not even sure...
Whoever was firing around six and seven, by that time, the president was already well covered.
So one question I have is, why wasn't one of the Secret Service personnel hit?
To my knowledge, there were no Secret Service bodyguards that were hit by rifle fire.
Are you aware of any?
So I'm a little bit surprised that none of them were hit, but of course, members of the crowd were hit.
So we know there were real bullets flying.
It's just astonishing to me that nobody in the Secret Service was hit if there were a couple more rounds coming in trying to hit Trump.
So who knows?
Maybe one of them was hit, but they had special ballistic protection that we don't yet know about.
You know, like super body armor...
You know, business jacket or whatever.
Advanced polymers.
Who knows?
That's just a possibility.
But the bottom line now is I think we are getting closer to solving the question of rounds one through five.
One, two, and three, probably crooks.
Four and five, probably from the hit team.
On the second floor behind the open window.
So that makes a lot of sense.
I want to thank Legally Armed America for having that guest.
I apologize.
I don't know the name of the guest.
But I'm sure more will come out.
This is all very fascinating.
All right.
Now let's go to the Joe Biden letter that he...
Well, I can't even say he has issued it.
Somebody has issued this letter in his name.
Probably Jill.
And probably, just like I predicted, they eventually came up with enough dirt to threaten him credibly, and he is now out of there.
So here is the letter from Joe Biden, or at least part of it.
He says, My fellow Americans, and this is dated July 21st, so yesterday, Over the past three and a half years, we've made great progress as a nation.
Okay, lie.
He's made progress destroying the nation, right?
He says, today America has the strongest economy in the world.
Lie?
Oh my gosh, he can't even get out a sentence without lying.
America's economy is in collapse.
Anyway, whatever.
We've made historic investments in rebuilding our nation.
Whenever the federal government people, whenever they say investments, they mean that they're printing money and handing it out to their goons.
They call that an investment.
He said, they've expanded affordable health care, blah, blah, blah.
Is your health care affordable?
How's your health insurance policy rates doing?
By the way, are those affordable?
It's just, it's unbelievable.
Anyway, he goes on and he says, it's been the greatest honor of my life to serve as your president.
Well, another lie.
He never served as president.
He was never elected.
The 2020 election was rigged.
He's been a fake president this entire time.
He says then, And while it has been my intention to seek re-election, I believe it is in the best interest of my party and the country for me to stand down and to focus solely on fulfilling my duties as president for the remainder of my term.
I will speak to the nation later this week in more detail about my decision.
And I'm just thinking, darn it!
We're not going to get a second debate between Biden and Trump.
I was really looking forward to that.
Gonna miss that.
We'll just have to re-watch the first one over and over again.
He continues, For now, let me express my deepest gratitude.
Blah, blah, blah.
I want to thank Kamala Harris for being an extraordinary partner.
Oh, my God.
I believe today, what I always have, that there's nothing America can't do.
When we do it together, we just have to remember that we are the United States of America.
Yeah, what a liar.
What a crook.
What a piece of garbage.
I mean, just someone who is a traitor to this country.
By the way, don't feel sorry for Joe because of his senility and all of his problems.
Don't feel sorry for him.
You know how many people are dead because of the decisions that Joe Biden has made?
You know how many people were financially screwed over by Biden and his people demanding payoffs and then keeping the payoff money and not even doing what they promised to do?
I mean, Joe Biden is a crook.
He's a mafia boss.
Don't feel sorry for him, not for a second.
And understand, the only reason he's stepping down is because somebody on Kamala's team, maybe with the help of Obama, maybe with the help of Hillary Clinton, somebody finally just opened up a binder and showed him, here's the dirt we have on you, Joe, and if you don't resign, this is what's coming out.
Just read points one through five.
And Joe's like, one through five.
Oh my God!
Okay, I promise to step down.
Because it's bad.
If the truth ever comes out about Joe Biden, it'll be retroactively removed from the history books.
They'll try to scrub all of U.S. history from any mention of this guy because he's such a crook.
But anyway, so he's not running for re-election, and he's endorsed Kamala.
Well, that shows he truly has no cognition remaining.
Anybody endorsing Kamala clearly has brain damage, just as Kamala does, it seems.
But at least Kamala, she can strain together sentences most of the time that still are coherent and add a little bit of a wicked cackle at the end of it as well.
But do you think Kamala's going to be the nominee at the end of the day here for the Democrats?
No way.
And understand that the Democrats just carried out a coup against their own president.
Have no illusions.
This is what just happened.
The Democrats who claim to be protecting democracy, they just stabbed Caesar, their Caesar, in the back in a group stabbing.
Et tu, Brute?
Yeah, exactly.
Even Kamala, she's Brute in this case.
She stabbed him in the back.
And now, the vultures, the Democrat vultures like Hillary and Newsom, who knows who else, Whitmer, the Democrat vultures are like, they're stealthing their way in to have a feeding frenzy.
You know, they're going to try to feed on what's left of the Democrat party.
Hillary Clinton probably, she got so excited, her head spun around.
And then came back around, she's like, I'm going to be president!
And she's going to try to get into the position there.
She's probably digging up all the old dirt files, like, how can we threaten everybody who's in my way, damn it?
You know, that kind of thing.
She's, oh man.
There's a pretty good chance here that Hillary ends up as the nominee.
Seriously.
America will cringe at the thought of Hillary trying to come back in.
And I can't wait to see some of these radical, mentally ill leftists cheering for Hillary.
Someone who is one of the most evil, demonic, someone who has clearly been complicit in numerous murders and murderous government policies.
She's one of the most evil, wicked, demonic, skin-bag former humans to even set foot on this plane of existence, by the way, in my opinion.
And yet, there will be Democrats that will say, we love you!
We love you, Hillary!
You're such a wonderful person!
We love you so much!
But we hate Donald!
We just hate the Don!
And you've probably seen some videos over the weekend of leftists losing their minds Over the fact that they're going to lose the election.
This is really going to be something to watch.
You're watching the implosion of the deep state and the Democrat Party at the same time.
And if all goes well from this point forward, which may not happen, just to be clear, but if things go well, then we'll get to election day, Trump will be elected, He'll be inaugurated in January.
Of course, there'll be a lot of left-wing violence between those two events.
Trump gets in.
He announces criminal prosecutions or investigations against all the members of the deep state that took part in this assassination attempt.
Alejandro Mayorkas will flee to Chile or someplace with a non-extradition treaty.
He'll probably try to get, like, Russian citizenship or something at the end.
Can I be Russian, please?
You know, Maybe Blinken, too, for that matter.
Wouldn't it be funny if Blinken tried to become a Russian to escape being prosecuted as an American?
Anyway, things are about to get interesting.
And that brings us to the CrowdStrike information.
So, like I said earlier, I interviewed Zach Voorhees, the Google whistleblower.
Now, I interviewed him, actually, on Saturday.
And I was saving that interview for today.
And in this interview coming up, you're going to hear what Zach has to say about how these vulnerabilities continue to exist.
The CrowdStrike company has not solved this problem.
And there could be a rogue actor inside CrowdStrike that could have taken down all of these systems in a planned cyber attack dry run.
Let's call it a dry run.
And then yesterday, Zach contacted me again with an update.
He said, hey, the technical details have now been released of CrowdStrike.
And he says, this is what happened.
Now, remember that Zach Voorhees is a very, very high IQ engineer who knows C++. He knows some systems administrative type of knowledge areas.
That's not his expertise.
But he's pretty good as a sysadmin, especially on Linux and Unix systems.
And he knows enough about Windows to know how the drivers work.
I mean, he writes low-level drivers for hardware, embedded systems, things like that.
So he says, quote, turns out that a bug was not rolled out to the machines.
The bug existed in the machines.
Already.
What got rolled out was a data update that triggered the bug.
Whoa.
Whoa.
That's why this was able to get rolled out to all the machines.
It wasn't a code update.
It was a data update that triggered the long-standing bug.
So, and then he said it's a null pointer exception with extra steps.
So, wait a second.
I asked him, I said, doesn't that mean that there's a time bomb?
Or multiple time bombs could be implemented in all these machines just waiting to be triggered with data updates?
He says, yes, a time bomb was installed in all these computers.
All right, folks, I just did about a 14-minute follow-up interview with Zach Voorhees, and I'd like to actually play that follow-up 14 minutes right here, right now, because he talked about the ticking time bomb.
And so we're going to go to that.
I'll come back with some more analysis of what happens next with Joe Biden and the treasonous Democrats.
And then we will continue to the full interview with Zach Voorhees.
Just before I play this, by the way, let me give credit to our key sponsor here today, the Satellite Phone Store, SAT123.
And they also have beready123.com for backup solar power or solar generators and power storage devices.
We are headed into a time of real chaos here.
We're going to see major sabotage carried out by the Democrats.
Once Trump wins the election, even before he wins it, they're going to try to bring America to its knees.
We're going to see just outrageous acts of government-sponsored terrorism against the people, against the infrastructure.
They're going for broke.
So in order to be ready, be prepared, have backup communications, a satellite phone makes perfect sense.
A satellite texting device called the Bivy Stick, B-I-V-Y, Bivy Stick, also makes good sense.
And having backup power solutions makes a lot of sense right now.
Check it all out at sat123.com.
That's S-A-T-1-2-3.com.
Now, enjoy this 14-minute additional explanation with Zach Voorhees.
We'll be back on the other side.
All right, Zach, welcome back.
I understand you have new information because some technical details have been released now about the CrowdStrike, what I'm calling almost a malware type of attack or disabling all these computer systems.
So go ahead.
Tell us what you've learned.
Yeah, so CrowdStrike released a technical report on exactly what the issue was, possibly in relation to my tweets that got 23 million impressions, but they clarified what exactly went down and the results are actually really surprising.
So check it out.
It turns out that this was not a driver update that was pushed.
There was this speculation that I did that there was new code that was pushed to all these machines and that this code had a ticking time bomb in it that was released.
It turns out that ticking time bomb was already installed on everyone's computers prior to this event.
And what they pushed was actually a data file that was bad.
And this data file was called a.sys file, so we thought that it was a system driver, but it actually wasn't executable code.
It contained data.
This data had invalid pointers.
These pointers were loaded into code.
And then when those pointers were dereferenced, they referred to code in that null region, that first page space of a computer, which you shouldn't ever, ever access.
And that was causing the blue screen of death.
So instead of a bomb being pushed, that bomb already existed.
The question is, How many other ticking time bombs do we have because of CrowdStrike's shoddy code practices?
Okay, wow.
Wow, I have so many questions, Zach.
First of all, who pushes out data files named.sys?
I mean, that seems crazy.
Yeah.
I mean, I guess CrowdStrike does.
That's crazy.
I don't even know where to begin on that.
But then secondly, you know, in our interview that we conducted previously, we talked about there should be a quality control process.
There should be a staging area rollout to check everything.
Are you saying that these data files, when they are pushed, that there's potentially no staging testing or no quality control check on data files?
Data files typically don't go through the same QA process that system executables do because it's assumed, or more assumed, that data is benign and that it's the executable code that needs to go under rigorous review.
And because these are data files, they just raw-dogged it to everyone instead of going through the normal QA process for executable code.
Okay.
All right.
Then the next question is, you describe this as a time bomb that had already sort of preexisted on all these machines and it got triggered by this payload of this data file.
Doesn't this mean there could be many other time bombs in place right now yet to be triggered in the future?
Oh yeah, that's my assumption.
I mean, if this existed in one place, then I'm sure...
I mean, the reason why this time bomb existed at all is because they're not using the automated tools that are available to make sure that code like this, this unsafe code, is caught and fixed and doesn't roll out to production to everyone's machines.
And the only reason why Linux and Mac were not affected is because they didn't get this data rollout.
If they had this data rollout, this would have affected Mac, Linux, and Windows.
Oh, my.
Yeah, but it just affected Windows because they were the only ones that got this data payload.
Over the weekend, I've been watching videos from systems administrators who look like they've had no sleep, by the way.
Unhappy.
They've had to walk up to servers physically, plug in keyboard and monitor.
You know what I'm talking about?
And boot to safe mode.
And they're having to do this for tens of thousands of machines.
What are you hearing about the remediation efforts so far?
It involves a very long process, and it's a long process that they do not have BitLocker installed, which is another security package.
BitLocker likes to lock down a machine whenever something goes wrong.
And so this corruption of memory basically is a double whammy where people have to go through about 10 boot sequences in order to bring up a machine.
They can't do it remotely.
They have to plug in a keyboard and mouse or at least a keyboard in order to unlock the machine and delete the effective system driver and then boot up normally.
And so this whole thing with, you know, cloud infrastructure where you don't actually manage the machines yourself, you have somebody else manage a machine.
This is really, really unfortunate for them because all of a sudden their machines are locked and they can't get keyboard access to this cloud machine that's in there.
you know, Right.
And, I mean, for example, my own company, Brighteon Servers, they're in a data center that I've never been to.
I would not even know how to enter that data center.
I'm sure somebody in my company has access, but I've never been there.
This kind of conundrum must be happening everywhere.
People responsible for servers have never been to the location where they're running.
That's common, right?
That's totally common, yeah.
So, I mean, for a lot of these people, it's like, well, you know, they're going to go do a backup where they had, you know, a backup of their system on a previous day and just wipe out all the data that existed from that backup until now and basically just live with the data loss because it's easier than, you know, not having access to anything.
Well, in fact, I have a question for you about data loss.
I meant to ask you this in our previous interview.
Is it possible that if rogue code were pushed, let's say a rogue employee of CrowdStrike or some other company that has this low-level access, could these system drivers wipe hard drives and format hard drives?
Absolutely.
Yep.
Especially with CrowdStrike.
The way that CrowdStrike's software works is that it's injecting itself into all the running processes of your system.
Okay?
And so the system thinks that it's interacting with a Windows API call, but it's actually being intercepted by CrowdStrike.
And CrowdStrike is then checking the code, what's being called, and then forwarding the call to the actual Windows drivers in order to detect malicious software.
Now, if CrowdStrike had a ticking time bomb, what they could do is that they could just intercept a call and then just wipe the hard drive.
And they can do that because they've got privileged access to your computer.
So in other words, the IT apocalypse that we've just experienced as a world...
It's nowhere near as bad as it could be.
If malicious code were pushed that just started wiping hard drives, then there would be no recovery for these machines.
As you well know, backups are not done as frequently as they typically should be.
So let me give you kind of a nightmare scenario.
Let's say the Chinese Communist Party wanted to take out America's infrastructure.
What they could do is that they could just take these...
You know, CrowdStrike system drivers, because they're public, they're deployed on each and every computer, they could reverse compile them back into C code or a form of C code that's kind of hard to read but not impossible for a determined nation state, figure out where the bugs are, and then figure out how to alter the data files.
Now, it's, you know, system drivers are privileged.
You can't just, like, go and modify them with a virus.
But data files, on the other hand, are much more easily accessed.
And so, you know, if a nation state wanted to take out large swaths of infrastructure, they could just simply know that there's a bug in a file, you know, in reading a file, change that file that's read, and then, boom, all of a sudden a bunch of computers go down, you know, adversaries, or maybe even somebody that's working within CrowdStrike you know, adversaries, or maybe even somebody that's working within CrowdStrike could push the data file like this out to, you know, millions or billions of machines, and then all of a sudden all those machines just get locked down
And this is something that needs to be taken a look at.
I'm sure that CrowdStrike is going to revise the policy for pushing data files to their client machines, because if they don't, this is going to continue to be a critical bug that can detonate at any time.
Very important terminology you're using there.
This could detonate at any time.
There may be other unknown time bombs already in place on these systems.
But what you just said that's really important is that potentially a third party actor, even a nation state actor, could exploit...
Vulnerabilities that are already in place, and simply by modifying data files, which would not require potentially defeating the CrowdStrike protection layer.
That could be done through some other mechanism.
They could set off a similar type of cyber apocalypse event, is I think what you're saying.
That's exactly what I'm saying, right?
Yes.
Okay.
So, given that everything in our banks, for example...
It's all virtual.
It's all just on a database somewhere.
You know, the bank doesn't have a stack of cash that's yours, right?
They don't even want to give you cash when you ask for it.
Everything is virtual.
It seems like there's a feasible pathway to a kind of infrastructure takedown that could be very widespread, even a lot wider than what we just saw, especially if it impacts Linux or Unix machines.
I'm concerned about this.
Are you?
Oh, absolutely.
Absolutely.
And the thing is that there are tools in place to catch these types of issues, but they're just not being run.
And the question is, why?
Do you have any indication?
I mean, let me say this.
There's been a lot of speculation over the last couple of days from many people who are convinced that this is not a coincidence.
They think the timing of it is very suspicious to maybe distract people from asking questions about the attempted assassination of Trump.
That whole story is, of course, blowing up big time.
We can't prove such a connection.
But is there anything...
That you've stumbled upon that could indicate one way or another whether this was for sure an accident or possibly not an accident?
I mean...
You know, now that I see that it was a data file and that it had this sort of backdoor access, I'm now starting to think that this could have a little bit more malicious intent.
The amount of damage that they did was only limited to Windows machines.
If this data rollout had gone to Linux, it would have been orders of magnitude more catastrophic.
Is there anything in the Linux systems that would automatically prevent this?
Or are Linux systems similarly vulnerable to data file updates?
Well, the problem is that this is a CrowdStrike update, not necessarily a Windows update.
That's just why it went around all this consent and just, you know, just modified the information.
And so it's CrowdStrike's, you know, infrastructure that injected this data file.
And so, you know...
This isn't even something that Linux can prevent, right?
Like a program is free to download a new file and stash it somewhere.
And so I think that this backdoor would have extended to Linux and Mac OS as well if they had been targeted, but they just simply weren't.
And that's the reason why we only had it localized to, I believe it's Windows 11 that had this data file push.
Okay.
Wow.
All right, Zach, this is really fascinating and a little bit horrifying.
Is there anything else you want to add that we haven't covered?
Nope.
I mean, that's pretty much it.
There you go.
So mystery solved.
It was the data file push by CrowdStrike that took all these machines down.
Okay.
All right.
Fantastic.
Let's give out your contact information one more time.
Your handle on Twitter?
Twitter.com slash perpetualmaniac.
And check out my Google Leaks disclosure of 950 pages.
You get to see how the sausage is made at zachvorhees.com.
Also check out my book, Google Leaks, A Whistleblower's Exposé of Big Tech Censorship.
All right.
Fantastic.
Zach, thanks for reaching out and updating us.
And please keep us posted as more developments become public.
You got it, Mike.
All right.
Pleasure.
Thank you, Zach.
Yep.
Take care.
So you heard that.
You heard Zach Voorhees say it.
It's a ticking time bomb.
And it's a ticking time bomb.
Well, there could be multiple ticking time bombs already implanted on all the servers that run the Western world.
Including the Linux servers, the Unix servers, the Mac, and the Windows machines as well, it could already be in place, ready to be triggered by nothing more than a data file update, which bypasses the normal QC that's involved with executable code and staging areas and so on.
And as you heard me ask Zach, I said, you know, is it possible that these low-level system files can format hard drives and wipe out storage?
He said, absolutely.
Yeah, of course they can.
So we are probably looking at a coming cyber event, a false flag carried out by the Biden administration, what's left of it, which is now in shreds at the moment, imploding by the day.
They know they can't win with Kamala Harris.
They know they can't beat Trump.
They've already failed to assassinate him, and they're not going to get another shot like they just had.
That's not going to happen again.
They are going into desperation mode.
They are likely willing to collapse the entire country.
And now we know there's a mechanism to do that.
And I'm not assigning blame to the CrowdStrike company.
What I'm saying is that there could be rogue or deep state CIA operators in place that can exploit the structure of data file rollouts or code rollouts that the CrowdStrike company uses.
In other words, CrowdStrike could be itself hijacked or hacked, or there could be a malicious actor that has penetrated the CrowdStrike company without the knowledge of the CEO or the higher-ups at CrowdStrike.
And these malicious actors could be, again, using the CrowdStrike infrastructure in order to achieve a massive cyberattack takedown of much of the Western world, including the banking system, obviously transportation, as we just saw.
Airports, airlines, taken down, offline, subway systems, grocery stores, transactions, supply chain providers, but also many, many banks, wire transfer, Operations were taken offline, logins across the board with various services, and so on.
I mean, it was a freaking disaster, and it's just a small taste of what is probably yet to come.
So that's the takeaway from the Zach Voorhees update there.
Remember, I did a full interview with Zach Voorhees, like 30 to 35 minutes, that's still coming today.
We will get to that.
All right, so a couple other things.
So many pieces of news breaking today.
Senator Ron Johnson, on his official Senate.gov website, has put out something entitled Preliminary Findings.
July 13, 2024, assassination attempt on former President Donald Trump.
Executive summary, he lays out what's going on here, and he's got multiple bullet points.
I just want to read for you some of these, but I wanted you to understand that even a United States senator is now on board questioning the official narrative of the FBI and the Biden regime.
And their narrative is that this was a lone shooter.
You know, the lone gunman theory, this is always the case.
Of course, Crooks was a patsy.
Of course, he was recruited and brought in.
He probably thought this was a training exercise, right?
Or a game or something.
And they set him up.
They killed him to cover up their own tracks.
But what actually happened was, most likely, Alejandro Mayorkas ran this thing, is my opinion, with Secret Service, Homeland Security, and especially HSI, Homeland Security Investigations.
That's the same group that ran a bunch of tyrannical investigations against J6 peaceful protesters, by the way.
So HSI and DHS and United States Secret Service, very likely all involved to assassinate Donald Trump.
And now we have U.S. senators that are involved in questioning this.
So it's no longer the territory of just Alex Jones questioning the official government narrative.
Now it's senators, it's members of Congress, it's numerous journalists and so on.
So anyway, point number one from Senator Johnson's report.
Secret Service did not attend a security briefing provided to local special weapons and tactics SWAT and sniper teams the morning of July 13th.
Wow.
Like, why wasn't Secret Service there?
Okay, point number two.
Local law enforcement said communications were siloed and they were not in frequent radio contact with the Secret Service.
Well, that's a problem.
They're supposed to have a common comms channel.
They're supposed to distribute the frequencies, obviously, and they always have a backup frequency, too.
So, you know, you have frequency A and frequency B. What was going on?
So they did not distribute the frequencies.
Number three, local law enforcement notified command about crooks prior to the shooting and received confirmation that Secret Service was aware of the notification.
In other words, Secret Service knew the guy was walking around.
They knew it for 26 minutes.
They knew it.
And I believe Secret Service was tracking his progress.
I think they needed him to walk through the steps of becoming the patsy, like, you know, jump through these hoops, climb up this ladder, crawl on this roof, and then we'll shoot you.
And they were making sure that he was doing what he needed to do in order to be the Patsy.
So point number four from Senator Johnson's report.
Following the shooting, Secret Service was seen on the roof of the AGR building with local law enforcement.
Photos of the shooter were sent to the ATF for facial recognition.
Okay, all right.
Point number five.
Secret Service was initially not going to send snipers to the rally, according to local law enforcement.
Wow, really?
No snipers were planned?
That seems very crazy.
Okay, let's see.
Then there's a timeline in the special report.
From Senator Johnson.
And then there are a number of outstanding questions in his report, such as, was the Secret Service or FBI aware of any threats concerning a potential security threat to former President Trump?
Blah, blah, blah.
He goes through some pretty obvious questions, like, what about the firearm?
What about the bullets?
What about the brass?
Things like that.
Questions that we're all asking.
What about this AGR building?
Yeah, that's American glass research.
I've seen some people do some investigations into AGR and who are some of the investors and owners and so on.
A lot of links there that are raising red flags among certain people.
I don't have time to go into that right now.
But why was the AGR building chosen to be left unprotected by the Secret Service and then to be scaled by crooks?
You know, it's very clear that I'm not disparaging every agent of the Secret Service, by the way, nor law enforcement.
I'm saying that a rogue element under the control of Biden officials here, probably Cheadle and probably Mayorkas, clearly...
Left that roof open, left the building open, the ladder, everything, and they've walked this kid, Crooks, they've walked him through the steps to get onto that roof, fire off three rounds, and become the Patsy.
This was straight up an assassination attempt.
They were going to take out Trump.
They were going to terrorize the nation.
They had all the photographers there ready to take pictures at, you know, 4,000 frames a second of Trump's brain blown out the back of his skull.
I mean, that was all going to be...
On the cover of the New York Times, you know what I mean?
They had it all planned.
They were going to roll this out, and the deep state was going to say, if you cross us, we're going to blow your brains out, just like we did JFK. That was the message that they were trying to send, and it failed.
It failed.
Failed big time.
So now let's talk about the aftermath.
So here we go.
Here we go.
Oh, boy.
Everything that I predicted previously about the coming era of chaos, you're going to have to triple that at this point.
Because now Biden stepped down from the campaign.
Kamala Harris is unelectable.
The Democrats are not just losing their candidate here.
The Democrat Party is on the verge of ceasing to exist as a functional entity.
The Democrat Party could be done here, especially if the truth about this assassination comes out.
And I believe that in time it will.
They're not going to be able to cover this up like they did 9-11.
This is going to come out.
This is going to expose them all.
The Democrat Party is going to be utterly destroyed.
And in order to stop that from happening, because they can read the writing on the wall as well, they can see where this is headed.
In order to stop that from happening, well, I'll ask you the question.
What are people like Barack Obama or Joe Biden or Hillary Clinton or whoever, top level Democrats, what are they willing to do to cover the tracks and stay in power?
Would they be willing to terrorize the United States of America?
Yes.
Would they be willing to cause a massive cyber attack false flag causing trillions of dollars in economic damage if it covered the tracks?
Absolutely.
Would they crash the banks to cause chaos and maybe try to halt the election if they thought that could keep them in power?
Oh, yeah.
A hundred percent, folks.
Would they start a nuclear war?
Yes.
Would they launch nuclear false flag weapons in America?
Yes, they would.
Of course they would.
These are treasonous, criminal, sociopathic lunatics.
These are destroyers of worlds.
And they know that this is the end of their rope here.
They got caught.
They failed.
They're being exposed.
Senators are turning against them.
The public's turning against them.
Even freaking Wall Street is turning against Biden.
Big Tech is turning against Biden.
Right now, almost every institution in society, other than the education system, which is like libtard hell that's already too far gone to save...
Most of the institutions are realizing, my God, we need Trump as president because we need some kind of predictability in this system.
We need somebody who's actually running things, not a puppet, not a meat puppet controlled by some mysterious cabal of who knows who, Susan Rice and Barack Obama or whoever else and Jill thrown in there in the mix.
No.
The institutions are rapidly shifting to Trump now.
And most of them, I think, recognize that Trump...
I mean, even the head of the Teamsters Union, he spoke at the Republican Convention.
When was the last time that happened?
It's been decades, folks.
They know Trump's going to win this.
And now what's happening is they're jockeying for position to try to get in into the Trump administration or positions of influence to try to influence Trump's decisions, his policy decisions.
That's where this is now.
This is no longer a question of who will win the presidency.
Even though I want to be clear, don't get lazy.
Everybody has to go out and vote.
Everybody has to be mindful, volunteer to be a ballot watcher.
If you're an attorney, volunteer your legal services.
We have to go through the process of the elections, and we have to stop the cheating of the Democrats.
But if that can be done effectively, Trump gets elected.
And then...
The race begins by the institutions to try to influence the Trump administration, the coming Trump administration, and at the same time, the radical left, after Election Day, they will lose their freaking minds.
And remember what I said, these three time segments, from now to Election Day, and then the second one is from Election Day to Inauguration Day, and the third one is from Inauguration Day+.
So each of these three segments gets increasingly dangerous as the left commits more and more sabotage and tries desperately to stop time from moving forward.
So if we make it to Election Day, which is, what, less than 100 days away now, I believe?
Something like that?
I mean, it's coming up fast, folks.
If we make it to Election Day, we have the election, Trump wins from that moment?
You're going to see America in chaos.
Anarchy in the streets of many cities.
You're going to see the radical left just pull out all the stops.
I mean, you know they're mass mentally ill already just from their antics on the videos and the way they talk and scream and accuse everybody of everything.
They're insane.
But if Trump wins the election, leftists are going to lose their minds and just, they're going to grab guns and start shooting people.
They're going to Burn down buildings.
They're going to sabotage bridges.
I mean, all the things that I was talking about before that enemy combatants might do to America, you know, foreign terrorists, like blowing up bridges and targeting refineries and, you know, spiking railroad tracks and all the horrible things that enemies of America do, that's what the left is going to do.
They're going to do all that and more.
They're going to set fire to their own cities and They're going to just start shooting white people, you know, in cars and trucks.
They're going to try to turn America into a war zone.
And just as importantly, the Biden regime is going to try to set in place a series of ticking time bombs for the Trump administration to deal with.
You know, like banking collapse, national security problems.
I mean, you're going to see crazy things like Joe Biden signing executive orders to just like Release all the felons, you know, just release them all onto the streets of America because they're just trying to punish America or just open the borders wide open, just let tens more millions of illegals flow through.
They're going to do things like that.
They're going to literally spend the last two and a half months of the Biden regime figuring out how to destroy America in, I guess, 10 weeks.
Can they do it?
I don't think they can, but they can cause a lot of pain.
They're going to cause a lot of disruptions.
There's going to be all kinds of banking havoc at that time.
Gold and silver will probably skyrocket.
Gun sales will suddenly explode again.
By the way, gun sales have been down for at least, I think, nine months, something like that.
Way down.
People aren't buying guns.
Ammo sales haven't been that high.
But you know how gun sales are.
It's feast or famine.
And the minute this radical left-wing terrorism opens up, you're going to see a mad rush to purchase firearms again.
And right now, there's plenty of inventory.
You can buy pretty amazing firearms at very competitive prices right now.
Lots of supply.
That's going to change overnight.
It will.
It'll change overnight.
And if you don't already have the firearms that you think you're going to need to protect yourself during this attempted left-wing chaos revolt, then get them now.
This is a good time to get them.
High supply, low price.
I mean, relatively low price.
And I recommend ShieldArms.com.
ShieldArms.com.
They're not technically a sponsor.
They've never paid anything to be mentioned, but they have provided a couple of samples of some pistols.
One of them has become my daily carry, by the way.
So go to shieldarms.com and use discount code Ranger.
They've got Glock pistols that are customized and very well done, including the Glock 43X, which is what I carry.
And they've got also high-quality AR-15s and folding ARs.
Which is a format that's very handy.
And they also have folding AR pistols with arm braces available, again, since the courts forced the ATF to back off of that arm brace rule.
So for right now, you can get arm-braced AR-15 pistols with a folding brace, in essence.
And you couldn't get that for the last couple years.
But you can get it now.
Shieldarms.com.
Discount code RANGER. But my point is, most people are not ready for what's coming.
Obviously, they're not ready for their banks to suffer chaos.
They're not ready for the roads and highways and bridges to be shut down by radical left-wing protesters.
And this time, the left is going to start shootouts.
Because you know how brainwashed the leftists have become?
They think that if Trump becomes president, they think he's Hitler because they're brainwashed morons and they believe the left wing media, which has been pushing that narrative for years.
They think Trump is Hitler.
They think that if Trump wins, that America will fall.
Little do they know it's exactly the opposite.
If Trump doesn't win, America falls because Joe Biden, Barack Obama and the Democrats have been systematically destroying America from within and they very nearly finished the job.
But these leftists, because they believe that they think Trump is Hitler and because they believe is an existential threat to America, they're going to be on suicide missions.
And Your typical leftist is going to become a suicide bomber, in essence, or a suicide shooter.
They're going to go out and get a gun, legally or otherwise, and they might do it in small groups, be like a group of radical leftists, go out and get like four rifles, and then they're going to park their cars on the edge of a bridge, let's say, and they're just going to shoot everybody driving a car toward them on the bridge.
They're just going to carry out a mass shooting terrorist attack to block a bridge.
They're going to do things like that.
Because they think that this is the end of America and they're willing to sacrifice their lives for, you know, their cause, which is actually communism and Marxism and, you know, suicide destruction of society and, of course, transgenderism and groomers and, you know, pedophilia.
Yeah, these left-wing lunatics, they will die to defend pedophiles.
I mean, that's how insane they are.
And, you know, Law enforcement will engage these people and law enforcement will take them out.
You're going to see a lot of SWAT teams get a ton of practice.
Well, I mean, not practice, but actual real life experience shooting radical left wing terrorists.
And you're going to see probably community-level organizing of defensive units in small towns and key crossings, could be bridges, could be highway checkpoints.
You are about to see, for a while, you're about to see America go through something that you never imagined.
It's going to look a lot like a civil war in many areas, even though that's not what it is.
And then, you know, that's going to go on for roughly 10 weeks.
And then Trump's going to be inaugurated.
January 20th, I think the day is.
And some of this terrorism will probably continue.
But there's going to be a rapid crackdown.
Rapid crackdown.
You're going to see the National Guard go to town.
On these radical leftists, and you're going to see citizens defending their communities, their property, their families, their neighbors, and also probably citizens working with local law enforcement to secure their towns and secure their roads.
And it's going to take a few months.
It's going to take a few months before the shooting probably quiets down a little bit.
So I would say if you want to mark your calendars here, folks, Say, from November 6th to about April, March or April of next year, that time period is going to be basically, you know, war zone.
Not everywhere, not in rural areas so much, but definitely near or in the blue cities.
War zone.
Because the left wants it to be that way.
And then slowly but surely, there will be a restoration of the rule of law.
More governors will get on board with stopping the terrorists.
And Trump will be able to order the deployment of National Guard units.
Probably will declare some kind of national emergency.
And it's also quite possible that under the cover of that emergency that he could arrest a lot of the deep state traders.
So wouldn't that be cool?
Pretty sure Ivan Raiklin already has a list of people who he claims should be arrested.
And I haven't seen that list, but I can imagine some of the names that are on it.
And then, of course, the medium-term financial crash that Biden has set into motion, or will have set into motion, that will be kicking in late spring or summer of 2025.
And then you're going to go through a banking collapse, a financial collapse.
So you're going to be thrust into an economic collapse scenario.
From some time in 2025.
And it'll probably last a couple of years.
And Trump is going to have a hard time dealing with that.
And much of America is going to have a very difficult time.
So that's where you want to have gold and silver.
You want to have assets that you control.
You don't want to have your money in bank accounts because the banks may just be taken offline with the next round of cyber attacks.
You want to have physical assets in your possession.
So all the prepping that you and I have done over the years, it's going to come in very handy soon.
I don't know how long the power grid is going to be down.
I don't know what the battle zones will actually be geographically.
Which states will be the worst?
Probably the blue states.
The blue cities are going to be death zones.
No question about it.
Because the left cannot coexist with the rest of us in a society where elections are fair.
You notice that?
The left cannot exist in a society where other people are allowed to speak.
That's why the left, they have to push censorship.
That's why they have to push gun control.
They cannot live in a society where other people are armed.
They want to have all the guns themselves in the hands of their government officials, but no firearms for the citizens.
So you notice the leftists, all they can do is cheat.
That's all they know is to cheat at elections, rig everything, censor all the speech they don't like.
And when it comes time that they are defeated in this next election and they realize they're going to lose control, then they're going to lose their minds.
And many of them are going to decide that they would rather die than live under a Donald Trump presidency.
Seriously.
Seriously.
There's going to be record business for all the mental health counselors and psychiatrists in California.
That's for sure.
They're going to be booked out to 2027.
It's like, and what's your concern?
Oh, another suicide ideation person here.
Oh, yeah.
Yeah, you're like the 27th one this week.
And they're all leftists.
Wanting to kill themselves because they can't stand the thought of living under Trump.
That's how insane they are, and that's an indication of how hard they're going to fight to destroy America, to disrupt society, to take down the power grid, to stop the banks, to do anything.
I mean, this is a suicide mission.
It's like being on a boat with a suicidal bomber who strapped himself to the hull and With a giant explosive vest and he's ready to pull the strings.
Like, if this ship doesn't sail where I want it to sail, I'm going to blow the whole thing and we'll all go down!
You know, like, that's what Democrats have become.
They don't represent democracy.
They don't represent neoliberal ideas.
They don't represent inclusivity.
They don't represent, you know, women's rights.
Nothing!
The Democrat Party have become a party of freaking suicide bombers and terrorists.
And evil demonic creatures that despise humanity and despise America and are at war with democracy.
And that's why as they go down and they are defeated and their systems are dismantled and they're removed from power, it's going to be something to celebrate.
So every one of these leftists that decides to take themselves out There's one less leftist that SWAT teams are going to have to deal with eventually as all these leftists lose their minds and become terrorists.
So if you're listening to this and you're a member of law enforcement, especially if you're on SWAT or any law enforcement role, you're going to get a ton of experience.
You're going to get a lifetime of experience in the next year.
And I just hope that you're safe, okay?
I just hope you're safe.
Double down on your skill sets.
Make sure you've got good body armor ready to go.
You know, practice your dry fire drills.
Don't just be okay with minimal qualifications for your firearm skills, you know.
Become very good.
Because you're going to find yourself living in a war zone.
For real.
Much of America is going to be in a kinetic war launched by the left.
So get yourself stocked up.
Get ready in every way you can.
You know, I put together rangerdeals.com, which is linked to all the best preparedness items with discount codes that I've put together.
Key partners, companies, some of them are sponsors, as indicated on the page there.
Some of them are not sponsors.
Many of those companies have just offered discount codes for our listeners.
Just go to rangerdeals.com.
Check out what we have there.
Technology solutions, ivermectin for pets, chlorine dioxide for sanitizer use.
We've got the discounts on firearms, ballistic vests, de-googled phones, gold and silver, gold backs, and so much more.
That's kind of the hub of preparedness.
It doesn't list food, though, or doesn't focus on food because, of course, we offer food at healthrangerstore.com.
So if you go to my website, healthrangerstore.com, you'll be able to get backup food supplies.
And currently we have plenty of that in stock right now.
But when all this starts to hit the fan, you know, our entire inventory will be blown out very quickly.
Fortunately, right now we're in good supply.
So if you want to stock up, Then just reach out to us at healthrangerstore.com.
And thank you for listening.
We're going to go to the full interview now with Zach Voorhees, the Google whistleblower, coming up next.
Stay tuned.
All right.
Welcome, everyone, to this BrightTown.com interview.
I'm Mike Adams, and today we are joined by the Google whistleblower, Zach Voorhees, in the aftermath of the CrowdStrike Falcon security failure that bricked, I think, maybe millions of Windows server systems all over the world with repeating endless loop blue screen of death boot failures.
So welcome, Zach.
Quite an interesting time to be talking about all this, isn't it?
Yes, it is.
CrowdStrike's update was rolled out to millions of computers, and it caused a blue screen of death because it was causing a crash in a privileged piece of code called a system driver.
And this system driver, when it crashes, it doesn't just terminate, it actually halts the operating system because it doesn't know what to do anymore because you cannot have a crash in privileged code.
You can have a crash in unprivileged code in which the application terminates, but that's not what's going on here.
Right.
I saw there was a post that took a look at that file.
I don't know if you've seen this or if I'm wrong, correct me, but I thought it showed that at least part of this file was just a bunch of zeros, like literally filled with the digit zero over and over again.
Did you see that?
I did, and I looked at the Hacker News Forum and some system administrators came in and said that that's not always the case, that all the computers that they have been working with, it is not filled with zeros.
So that was pointed to as the culprit at the beginning, but it looks like that's not always the case.
Okay, so let's talk about the technical side of this and rolling out.
I mean, you're an accomplished developer, so you know that there's always a staging test area for this, and there's always, you know, the new code is always tested against a wide variety of different operating system variants or installs or hardware systems and so on.
Can you talk to us about what would be typical in a company like this, responsible for security, What kind of normal pre-rollout QC would they have gone through?
Yeah, so the normal way that C++ codebases are checked is that they've got a set of automated tools.
It looks like those automated tools were not run on this codebase for whatever reason, probably because it's old and there's a lot of...
It was kind of before a lot of these modern tool sets came in.
So first off, they're not running a lot of the automated tool sets.
That's my speculation.
But more than that, they're rolling it out to everyone at the same time.
Wow.
And that's not the way that you do a rollout because what you have to assume is that, well, we all know that code has a lot of bugs in it.
It's just the way software is.
And so rather than try to make sure you do all the possible checks and roll it out to everyone, what you do is you do a staged rollout.
Where you roll it out to, let's say, a region.
And then if you wait like an hour, you wait like maybe four hours.
If no one starts complaining, then you roll it out to a larger area and you just roll it out.
That way, if there is a fatal problem, you are going to get wind of it really quickly.
And if they had done that, in this case, what they would have done is got a call from a bunch of angry system administrators that just said, you just took down every single one of our computers with this software update.
And instead of doing that, they just rolled it out to everyone and got hit with this.
So my question is, does it seem, and I understand this is just going to be an educated guess, but does it seem like they bypassed or maybe a rogue...
Deployment person or developer bypass the normal operating procedure.
There should be a sequence of steps that they go through before they roll out a new patch.
Does it seem like they bypass that?
Yeah, I think it was somebody trying to go on vacation, and they were rolling this out on a Friday.
It's pretty famous that you don't release software on a Friday right before you go home for the weekend.
Yeah.
Absolutely.
You start rolling it out on Monday for this very reason.
And it looks like this person rolled it out.
It looks like it might have actually bypassed Windows updates because no one got any notification.
They didn't get the consent to opt out.
They just got it pushed to them.
And the problem with this is that CrowdStrike's software is sort of an anti-malware, anti-virus, anti-penetration software.
So what it does is it penetrates other applications and injects code into their executable so that it can monitor bad, malicious behavior and catch it really quickly.
So it's got this privileged access that it needs to do.
And so this update rollout Just simply swapped out the previously working code for a new system driver, and that system driver crashed the operating system.
So, would I be wrong to describe this push of this CrowdStrike system file update as itself malware?
I mean, this took down systems, which is what it's supposed to prevent from happening, but it did a very effective job.
In fact, I don't think there's ever been a piece of malware that's ever been as effective as this at taking down as many systems all at once, has there?
Nope, not since the viruses in the 90s used to do something similar, but now it's bad software updates by reputable companies that are taking down large sections of the internet.
Can you think of any other failure in history that had as big of an impact on the world as this?
No, no, this is the biggest one to date.
There's been other security vulnerabilities that have happened, but nothing that's taken down so many computers.
It's almost like an attack from Russia or China to take down infrastructure.
That's the scale of this oopsie.
Okay, so you use the word oopsie.
How do we know it wasn't something on purpose by somebody within CrowdStrike?
And I'm not saying that the CrowdStrike company intended to do this, but perhaps a rogue operator took a payment, you know, hey, here's 50 Bitcoin.
Push this thing.
And they did it.
Is there any way to exclude that as a possibility?
I can exclude it.
I mean, that is definitely possible that they did this in order to sort of weaken our infrastructure and, you know, weaken Microsoft, one of the leading computer companies in the world.
Okay.
You know, until we see that this is not programmer error.
It's C++. It's an old code base.
This sort of problem is endemic with these old code bases.
The newer version of C++ has a lot of fixes that prevents this sort of class of errors.
But, you know, this code base probably existed way before things got cleaned up in the language.
Okay.
All right.
Fair enough.
But CrowdStrike, whether this was intentional or accidental, CrowdStrike has just proven a couple of very worrisome things that I'd like your comments on.
One is that global Windows server security is very centralized.
It's in the hands of one guy.
That's really frightening.
And secondly, there is a mechanism that exists that was just demonstrated where the CrowdStrike company can bring down much of the Western world's transportation and supply chain infrastructure.
And that's now a fact, right?
That's not theory.
That's a fact.
What are your thoughts about these two emerging facts?
I think that a lot of these companies need to have audits.
I think that a lot of this falls into the hands of Microsoft and their insecurity to allow a company like CrowdStrike to go ahead and inject this code into computers.
I mean, how do we know that CrowdStrike...
Is it infiltrated?
Is it compromised?
If this was a deliberate attack, we would be really screwed right now.
All of our systems would have been taken offline if this was an attack and not a mistake.
And in the future, it could be an attack and not a mistake.
In fact, this could even be an attack, hypothetically.
We just don't know.
So let me lay out a scenario for you.
Let's just say an agent of the CCP comes over to the U.S., finds the high-level employees of CrowdStrike, identifies it.
It's probably not difficult to figure out who they are.
Starts Following them, researching them, and kidnaps their kid or something, and says, hey, you ever want to see your kid again?
You're going to push this update.
I mean, that's not a James Bond movie.
That could happen in real life.
Yeah.
And this supply side attack has happened before with SSH, the common way that we log into computers on Unix.
There was a well-planned out supply side attack of an unknown person who spent two years gaining the trust Wow.
put in a supply side attack that compromised the way that we log in into computers.
And so this isn't unprecedented.
This isn't science fiction.
This isn't fantasy.
This is something that's happened before.
Wow.
And this event with CrowdStrike reiterates and drives home the point that we need to have auditing of these centralized services.
Or possibly even break them up so that we don't have these sorts of problems again.
Well, speaking to that exact point, Russia's transportation infrastructure was mostly not affected.
You know, their airports were functioning, planes were in the air, while in the US and even in the UK and many other countries, The planes were grounded.
The airports were in chaos.
Well, that's because Russia uses, I think, a variant of a Linux operating system for their air transportation backbone.
Are you thinking, can you confirm that, or do you have any knowledge of that?
You know, what's interesting is that CrowdStrike actually borked a lot of Unix machines last month.
But because there's not a centralized way that code is pushed on Unix, the damage that it did was very small, contained, identified, rolled back, And
not on a global scale.
Wow.
Okay.
Well, I may ask you another question about the core differences between Unix slash Linux flavors versus Windows.
But look, I've got something else real quick.
I was on Amazon today checking an order status because I still do order some things from Amazon.
Here's a message that pops up under your orders.
Quote, a small number of deliveries may arrive a day later than anticipated due to a third-party technology outage.
So, you know, here's a case where it's even affecting Amazon and their logistics systems, not just banks.
Payroll was also impacted, and I understand that supply chain logistics transactions were delayed, which will affect auto manufacturing and many other things.
Do you have a sense of, like, how widespread this is in terms of industries affected?
I mean, there's a lot of industries that run Windows.
I don't know why they run Windows for their server backend operations.
Windows is spyware.
Windows is communism.
You know, there's a centralized bureaucracy that controls the updates and pushes it to you.
And now they're going to start monitoring your actions and clicks with artificial intelligence.
And for some reason, a lot of the industry uses Windows as a server to run their services.
Now, keep in mind, if they're running Linux, which is free and open source, they're not running into this issue.
Well, yeah, exactly right.
So that was one of my questions.
Talk to us about the structure or the architecture of Linux and why it doesn't have the same vulnerabilities where a security company has to have these low-level sys files with hooks into every function within RAM. I mean, talk to us about the differences.
Right.
So the difference between Linux and Windows is that Linux...
Linux was a free operating system that was spawned off of Unix.
Unix was developed in Bell Labs, I think in the 1970s.
Linus Travolts basically decided that we needed to have a consumer PC version, free version of Unix.
He spawned Linux.
Linux became the trunk of a whole bunch of family of operating systems that are all based upon his kernel.
Now, the kernel is sort of like the core of the operating system, and then people build on top of that.
And that's been actually going on until this day, right now.
And so what's interesting is that most of the software that you use, like Facebook, you know, Google, their services, they're all based upon the free Unix operating system known as Linux.
It's free as in air.
It's amazing.
I use it.
And the thing is, is that because nobody really controls Linux, you have absolute sovereignty over the state of your server, right?
So no one can push an update if you don't want them to push an update.
Yeah.
And the difference between that and Microsoft's Windows operating system is that Windows operating system is completely closed source.
Microsoft owns it.
If you get a copy of the Windows code, you can be sued in a court of law.
And because of that, there's a lot of mysterious things.
We don't exactly know how it works.
Can you really trust it?
Is it capturing your keystrokes?
We have to trust Microsoft by faith that they're not doing any of those things.
But we can't audit it.
We can't see what's going on.
And that's really the difference between Linux and Microsoft Windows is that one is free, open source.
We can view it.
It's incredible.
And the other one, well, they can do whatever they want, including stealthily pushing code updates right into your computer.
Wow.
Wow.
Well, you know, it's really interesting.
We have a partnership with a company called Above Phone, and they do de-Googled phones, as you may know, but they just pushed out a Linux laptop.
That they call above books, like a notebook.
And it's got apps on it that look and function very much like Microsoft Office, but of course the apps are open source, and they don't call home, right?
So it's all yours, it's all under your control.
The main difference, the gap in usability between Linux and Windows is really closing, where Linux is becoming more and more user-friendly with the GUI interface and the apps.
Wouldn't you say that it's becoming a lot easier for mainstream people to use now?
It is becoming easier for mainstream people to use, especially since a lot of mainstream users just want to open up a browser and view the internet.
And for that, it's absolutely fantastic.
The big problem that still exists with Unix is that because not a lot of people use it as a consumer PC, Right now,
that's...
Really the biggest barrier for a lot of these engineers.
Like, for example, I still use Windows 10.
Why?
Because a lot of my software, a lot of my hardware does not work on Linux.
And until they fix that, I'm forced to use Windows.
But I might just bite the bullet now that Windows is forcing a whole bunch of, you know, unreasonable...
Capturing metrics on what you're typing and artificial intelligence that I may just have to bite the bullet and go to Linux for my consumer PC. I'm already using it for the servers that I deploy, but I've got three monitors, cameras, microphone, button board, all this kind of stuff that really just does not work on Linux very well at all.
Well, that's interesting because you're very familiar with our AI project.
We've talked about it.
And in our AI processing of articles and transcripts and so on, I do run Windows systems.
But most of those systems, especially the ones that are processing the bigger books, which take a long time, I do not have those systems connected to the Internet at all.
Not even Ethernet.
Not even local LAN. I walk up with a thumb drive, and I put the book files on it with a thumb drive, and then I let it process, and then I take them off with a thumb drive.
Windows is not updating, and then it's great, but obviously that's not useful for day-to-day business use.
I find Windows is only tolerable when it's completely disconnected from the Internet.
Right.
Well, you're using NVIDIA graphics cards.
NVIDIA graphics cards on Linux has always been a second, you know, redheaded stepchild.
It's not well supported.
And it's always been that way.
And it's been a subject of fury.
And you've run into this exact same problem, which has forced you to go to Windows.
And unfortunately, that's just the state of the world right now.
Now, as far as this big, you know, apocalypse here, this IT apocalypse, I call it, that just happened with CrowdStrike, do you think this is going to cause a lot of companies to move away from Windows servers now?
I mean, Elon Musk announced that he, of course, removed CrowdStrike from all the Tesla systems, which I guess means Tesla is still using Windows servers, which is a little bit surprising.
But are there going to be some long-term changes from this that are significant?
Yeah, there are.
There's a lot of negatives about running Windows because a lot of corporate IT departments, not only do they have CrowdStrike, but they also have BitLocker.
And the problem with this is that when you have this bug with CrowdStrike and the combination of BitLocker meant that people were doubly locked out of their machines.
Yeah.
And for a very long time.
And BitLocker issued an update on how to bypass their security methods, which I guess was previously unknown, to basically break out of their shell and disable the service so that somebody could get in and delete the offending driver and get back up and running.
But it requires like 10 reboots In order to get to work.
Wow.
And everything with Windows is just really slow because of the security software.
Linux will run, like when I compile an executable, you know, at work, I was running Windows, it took like 10 times longer than it did on the Linux operating system.
And this is endemic throughout the entire, you know, corporate world, is that they're very slow when you're running Windows, and it's very fast when you're running Linux.
And the reason is because all the Windows machines are pretty much the same.
So if you penetrate one, you penetrate them all.
Where Linux, because there's such a difference in flavors and packages that are installed, there's not the same attack surface vulnerabilities for these Linux operating systems.
Really good point.
One question along those lines.
It's my understanding that the manual fix process that these systems administrators had to follow in order to, you know, boot to safe mode, launch PowerShell, find the sys files, delete them, reboot, And then after that next reboot,
it seems like those systems then were not protected by CrowdStrike and that there would have been some time of an open vulnerability or no CrowdStrike protection until an additional system replacement was installed.
Does that make sense to you?
Or do you think these systems may have been vulnerable for some period of time?
Well, yeah.
I mean, here's the thing is that...
CrowdStrike is not necessarily there to prevent intrusion.
It's more as a secondary defense, like an immune system, to detect that intrusion has happened and then clean it up.
So the Microsoft's operating system, you could think of it as like the outer shell.
By default, it's pretty locked down to prevent intrusion.
But if that intrusion were to happen anyways, like let's say you stuck a USB drive in, Or somebody new of a zero-day vulnerability, so a vulnerability that hasn't been disclosed yet, then, you know, yes, they can get into the system and they can make changes, but, you know...
When you get a blue screen of death, the computer pretty much shuts down and doesn't continue.
And so it's that time when CrowdStrike is not on there that the computer would become vulnerable.
And until they put that CrowdStrike back on, then it could possibly be able to detect the system files that have changed.
Who knows?
Well, but the reason I ask is because of the history of Stuxnet and, you know, the CIA and perhaps Mossad was involved in that, you know, very clever.
I know you're familiar with the history and that was to stop Iran's, you know, nuclear weapons or nuclear materials development program.
And it was a very successful virus, but it was built by the intelligence communities.
Here's the thing.
Every computer that runs an Intel processor is backdoored.
There's a hidden operating system within the CPU called ME or something.
It can be activated over the network and can run privileged code.
CrowdStrike is not going to stop this.
None of this stuff is going to be able to stop it.
If the intelligence services want to get into your computer, they can get into your computer by this built-in backdoor at the hardware level that you can't even disable.
Let's look at the bigger picture.
All of our computers are vulnerable.
It's just that the people that are in the know haven't activated the trigger yet.
Okay, so since some people are wondering very vocally, you know, people like Roger Stone, for example, saying that he believes this CrowdStrike push was on purpose in order to change the conversation and take attention away from the success of the Trump speech and the Republican rally and so on.
Isn't it possible then that, I mean, the deep state, I think the deep state tried to kill Trump.
Isn't it possible they could also try to disrupt the world's computers to distract everybody?
That's possible, yeah.
Take out 8 million machines, take the news media offline, that's totally possible.
Absolutely.
What's interesting about this bug is that this bug has actually existed for a very long time.
That's the conversation I got from the Hacker News Forum.
And what they said is that this bug existed for a very long time and that it was waiting for the right conditions to reactivate.
And it got activated regularly.
I think it was by the Windows 11 boxes that it got activated by and not Windows 10.
I might be wrong.
I might have that switched.
But yeah, this bug has been lurking for a very long time.
It was a grenade waiting to go off.
And for some reason, a certain combination of things meant that it went off now.
Okay, so then there could be other bugs lurking, also waiting for the right conditions.
And are you aware of any, you know, has CrowdStrike announced any meaningful method to prevent this from happening again?
They have.
In fact, they've been pre-typed lipped about exactly how this attack or this, you know, error was actually propagated or the technical details about it.
The issue is that they're not running certain tools that would catch this sort of thing automatically.
There's this thing called address sanitizer, thread sanitizer.
It's going to catch these no-pointer dereferences, these invalid reads, and basically alert the developer, and they're going to fix it.
This is what happened at Google for YouTube products that are binaries that run on the...
The game consoles, we put it through a test system embedded into our deployment pipeline.
And so when you did a little oopsie, you would get an error message later on saying that this detector detected that there was a possibility of an error in your program and you needed to take care of it, and the test would go red until you took care of it.
And we found a whole bunch of bugs like that.
And the thing is, is that CrowdStrike simply isn't running any of this stuff because if they had, it would have detected that either this is a race condition because of multi-threading or they're just simply not checking pointers to whether they're null or not and assuming that they're valid.
They refer to valid pieces of memory.
And then you get a crash like this.
So this is bad on them.
They're not running their tool set.
They need to.
And I'm sure that going forward, they're going to put a lot of these safety checks in place so it doesn't happen again.
Well, maybe McAfee will announce a new software package to protect Windows servers from CrowdStrike malware.
Right.
It's like now CrowdStrike is a threat.
And I don't see any reason why they have stopped becoming a threat if they just did what you just described and it's like, whoa, you know, worse than hackers.
Right.
I mean, it's almost like a virus.
Like, what they're doing, just like swapping out system driver with their own system driver.
I mean, that's what viruses do.
And why is Microsoft allowing them to do that on all these computers?
Like, what sort of backroom deal do they have that allows them to deploy untrusted code into all these computers?
Yeah.
I mean, the only thing it lacked was an on-screen message that said, you know, give us Bitcoin and we'll unlock your computer, you know?
Right.
Right.
Exactly.
Right.
Okay, Zach, this has been incredibly helpful.
How can people follow you and reach you?
Give us your social, your website, everything else.
Yeah, follow me at twitter.com slash perpetualmaniac, also known as x.com.
Or if you want to see the disclosure that I had about blowing the whistle on Google, check it out at zachvorhees.com or check out my book, googleleaksbook.com.
Okay, googleleaksbook.com, zachvorhees, that's v-o-r-h-i-e-s.com, and then also perpetualmaniac on Twitter, correct?
Yep.
All right, Zach, welcome back.
I understand you have new information because some technical details have been released now about the CrowdStrike, what I'm calling almost a malware type of attack or disabling all these computer systems.
So go ahead.
Tell us what you've learned.
Yeah, so CrowdStrike released a technical report on exactly what the issue was, possibly in relation to my tweets that got 23 million impressions, but they clarified what exactly went down, and the results are actually really surprising.
So check it out.
It turns out that this was not a driver update that was pushed.
There was this speculation that I did that there was new code that was pushed to all these machines and that this code had a ticking time bomb in it that was released.
It turns out that ticking time bomb was already installed on everyone's computers prior to this event.
And what they pushed was actually a data file that was bad.
And this data file was called a.sys file, so we thought that it was a system driver, but it actually wasn't executable code.
It contained data.
This data had invalid pointers.
These pointers were loaded into code.
And then when those pointers were dereferenced, they referred to code in that null region, that first page space of a computer, which you shouldn't ever, ever access.
And that was causing the blue screen of death.
So instead of a bomb being pushed, that bomb already existed.
The question is, How many other ticking time bombs do we have because of CrowdStrike's shoddy code practices?
Okay, wow.
Wow, I have so many questions, Zach.
First of all, who pushes out data files named.sys?
Right?
That seems crazy.
Yeah.
I mean, I guess CrowdStrike does.
That's crazy.
I don't even know where to begin on that.
But then secondly, you know, in our interview that we conducted previously, we talked about there should be a quality control process.
There should be a staging area rollout to check everything.
Are you saying that these data files, when they are pushed, that there's potentially no staging testing or no quality control check on data files?
Data files typically don't go through the same QA process that system executables do because it's assumed, or more assumed, that data is benign and that it's the executable code that needs to go under rigorous review.
And because these are data files, they just raw-dogged it to everyone instead of going through the normal QA process for executable code.
Okay, alright.
Then the next question is, you describe this as a time bomb that had already sort of pre-existed on all these machines and it got triggered by this payload of this data file.
Doesn't this mean there could be many other time bombs in place right now yet to be triggered in the future?
Oh yeah, that's my assumption.
I mean, if this exists in one place, then I'm sure...
I mean, the reason why this time bomb exists at all is because they're not using the automated tools that are available to make sure that code like this, this unsafe code, is caught and fixed and doesn't roll out to production to everyone's machines.
And the only reason why Linux and Mac were not affected is because they didn't get this data rollout.
If they had this data rollout, this would have affected Mac, Linux, and Windows.
Oh, my.
Yeah, but it just affected Windows because they were the only ones that got this data payload.
out.
Over the weekend, I've been watching videos from systems administrators who look like they've had no sleep, by the way.
Unhappy.
They've had to walk up to servers physically, plug in a keyboard and monitor.
You know what I'm talking about?
And boot to safe mode.
And they're having to do this for tens of thousands of machines.
What are you hearing about the remediation efforts so far?
It involves a very long process, and it's a long process that they do not have BitLocker installed, which is another security package.
BitLocker likes to lock down a machine whenever something goes wrong, and so this corruption Welcome to my show!
And so this whole thing with, you know, cloud infrastructure where you don't actually manage the machines yourself, you have somebody else manage a machine, this is really, really unfortunate for them because all of a sudden their machines are locked and they can't get keyboard access to this cloud machine that's in, you know, Well, right.
Yeah.
And, I mean, for example, my own company, Brighteon Servers, they're in a data center that I've never been to.
I would not even know how to enter that data center.
I'm sure somebody in my company has access, but I've never been there.
This kind of conundrum must be happening everywhere.
People responsible for servers have never been to the location where they're running.
That's common, right?
That's totally common, yeah.
For a lot of these people, it's like, well, they're going to go to a backup where they had a backup of their system on a previous day and just wipe out all the data that existed from that backup until now and basically just live with the data loss because it's easier than not having access to anything.
Well, in fact, I have a question for you about data loss.
I meant to ask you this in our previous interview.
Is it possible that if rogue code were pushed, let's say a rogue employee of CrowdStrike or some other company that has this low-level access, could these system drivers wipe hard drives and format hard drives?
Absolutely.
Yep.
Especially with CrowdStrike.
The way that CrowdStrike's software works is that it's injecting itself into all the running processes of your system.
Okay?
And so...
The system thinks that it's interacting with a Windows API call, but it's actually being intercepted by CrowdStrike.
CrowdStrike is then checking the code, what's being called, and then forwarding the call to the actual Windows drivers.
In order to detect malicious software.
Now, if CrowdStrike had a ticking time bomb, what they could do is that they could just intercept a call and then just wipe the hard drive.
And that's...
And they can do that because they've got privileged access to your computer.
So in other words, the IT apocalypse that we've just experienced as a world is nowhere near as bad as it could be if malicious code were pushed that just started wiping hard drives.
Then there would be no recovery for these machines.
As you well know, backups are not done as frequently as they typically should be.
Right.
So let me give you kind of a nightmare scenario, right?
Like, let's say the Chinese Communist Party wanted to take out America's infrastructure.
What they could do is that they could just take these, you know, CrowdStrike system drivers, because they're public, they're deployed on each and every computer, they could reverse compile them back into C code.
Or a form of C code that's kind of hard to read but not impossible for a determination state.
Figure out where the bugs are and then figure out how to alter the data files.
Now it's, you know, system drivers are privileged.
You can't just go and modify them with a virus.
But data files, on the other hand, are much more easily accessed.
And so if a nation state wanted to take out large swaths of infrastructure, they could just simply know that there's a bug in reading a file, change that file that's read, and then boom, all of a sudden a bunch of computers go down, adversaries.
Or maybe even somebody that's working within CrowdStrike could push a data file like this out to Millions or billions of machines, and then all of a sudden, all those machines just get locked down suddenly.
And this is something that needs to be taken a look at.
I'm sure that CrowdStrike is going to revise the policy for pushing data files to their client machines, because if they don't, this is going to continue to be a critical bug that can detonate at any time.
Very important terminology you're using there.
This could detonate at any time.
There may be other unknown time bombs already in place on these systems.
But what you just said that's really important is that potentially a third party actor, even a nation state actor, could exploit vulnerabilities that are already in place.
And simply by modifying data files, which would not require potentially defeating the CrowdStrike protection layer, like that could be done through some other mechanism.
They could set off a similar type of cyber apocalypse event is, I think, what you're saying.
That's exactly what I'm saying, right?
Yes.
Okay.
So given that everything in our banks, for example, it's all virtual events.
It's all just on a database somewhere.
The bank doesn't have a stack of cash that's yours, right?
They don't even want to give you cash when you ask for it.
Everything is virtual.
It seems like there's a feasible pathway to a kind of infrastructure takedown that could be very widespread, even a lot wider than what we just saw, especially if it impacts Linux or Unix machines.
I'm concerned about this.
Are you?
Oh, absolutely.
Absolutely.
And the thing is that there are tools in place to catch these types of issues, but they're just not being run.
And the question is, why?
Why?
Do you have any indication?
I mean, let me say this.
There's been a lot of speculation over the last couple of days from many people who are convinced that this is not a coincidence.
They think the timing of it is very suspicious to maybe distract people from asking questions about the attempted assassination of Trump.
That whole story is, of course, blowing up big time.
We can't prove such a connection.
But is there anything...
That you've stumbled upon that could indicate one way or another whether this was for sure an accident or possibly not an accident?
I mean...
You know, now that I see that it was a data file and that it had this sort of backdoor access, I'm now starting to think that this could have a little bit more malicious intent.
The amount of damage that they did was only limited to Windows machines.
If this data rollout had gone to Linux, it would have been orders of magnitude more catastrophic.
Is there anything in the Linux systems that would automatically prevent this?
Or are Linux systems similarly vulnerable to data file updates?
Well, the problem is that this is a CrowdStrike update, not necessarily a Windows update.
That's the reason why it went around all this consent and just, you know, just modified the information.
And so it's CrowdStrike's, you know, infrastructure that injected this data file.
And so, you know...
This isn't even something that Linux can prevent, right?
Like a program is free to download a new file and stash it somewhere.
And so I think that this backdoor would have extended to Linux and Mac OS as well if they had been targeted, but they just simply weren't.
And that's the reason why we only had it localized to, I believe it's Windows 11 that had this data file push.
Okay.
Wow.
All right, Zach, this is really fascinating and a little bit horrifying.
Is there anything else you want to add that we haven't covered?
Nope.
I mean, that's pretty much it.
There you go.
So mystery solved.
It was the data file push by CrowdStrike that took all these machines down.
Okay.
All right.
Fantastic.
Let's give out your contact information one more time.
Your handle on Twitter?
Twitter.com slash perpetualmaniac.
And check out my Google Leaks disclosure of 950 pages.
You get to see how the sausage is made at zachvorhees.com.
Also check out my book, Google Leaks, A Whistleblower's Exposé of Big Tech Censorship.
All right.
Fantastic.
Zach, thanks for reaching out and updating us.
And please keep us posted as more developments become public.
You got it, Mike.
Always a pleasure.
Thank you, Zach.
Yep.
Take care.
And thank all of you for listening.
This is Mike Adams here with Brighteon.com.
And feel free to share and repost this interview on other channels and platforms.
Take care, everybody.
The hurricane that recently blew through Texas caused over 2 million people to lose power in the Houston area.
And more people have lost power throughout Texas and other states as well as this has moved through.
Our sponsor, the Satellite Phone Store, has a sister site called beready123.com.
If you go there, you'll find that they've got power solutions, backup power systems right here.
They've got solar generators.
They've got storage systems.
They've got a survival go bag on top of that and many other items.
Plus, of course, you can get satellite phones and backup communication devices from them.
They've made them all affordable with a monthly payment instead of having to buy everything up front with the phones.
But if you go there, beready123.com, you'll find these systems that I use as backup power systems.
And right now the power grid is less reliable than ever before.
It seems like we're suffering more kind of storms or, you know, outages or just...
Cyber attacks on the power grid from time to time.
It's always important to have a backup system.
These solar generators, you can charge them from the sun.
Obviously, they have built-in charge controllers and inverters.
You can run small refrigerators off of these if you want to, or even blenders.
You can recharge computers or mobile phones or batteries for flashlights or even night vision devices.
So this is a really important technology area to make sure that you have squared away for your own personal preparedness and survival planning.
Again, check out the website, beready123.com, or you can go to the Satellite Phone Store if you just want the comms equipment, and that's at sat123.com.
And thank you for supporting our sponsors.
Your own government has the power to activate a kill switch on all telecommunications, instantly shutting down all private phone calls and texts.
An EMP weapon or solar flare can achieve the same result.
Rolling blackouts or permanent power outages will also take out the power supply to cell tower antennas, rendering mobile devices all but useless.
During these emergencies, how do you stay in touch with the important people in your life anywhere on the planet?
The answer is the Bivy Stick at SAT123.com.
The Bivy Stick is a two-way satellite text messaging device that uses a satellite constellation, not cell towers, to send and receive text messages.
It works anywhere on planet Earth, including in war zones or blackout areas, in unpredictable times.
The Bivy Stick helps you stay connected when it matters most.
Visit sat123.com to get one while they're still available.
A global reset is coming, and that's why I've recorded a new nine-hour audiobook.
It's called The Global Reset Survival Guide.
You can download it for free by subscribing to the naturalnews.com email newsletter, which is also free.
I'll describe how the monetary system fails.
I also cover emergency medicine and first aid and what to buy to help you avoid infections.