Windows - Crowdstrike issue
The file that caused CrowdStrike to alert was C-00000291-00000032.sys, which was 42KB of null values.
The replacement file, C-00000291-00000033.sys, was 35KB and appeared to be a normal file.
Anonymousss
Was crowdstrike hacked???
Okay hear me out, the kernel panic happened because of a channel update. For those who don't know channel updates consist of updating files not the code itself. So the BSOD happened because of a new file update and not the code. Although it's true that they didn't handle the null check. But what if some hackers deliberately replaced the affected file with a faulty one where code tried to access it at a memory location that doesn't exist. Because it seems too far fetched to me to believe that they didn't do proper testing as even crowdstrike is aware of the importance of such updates. What if they decided to let people assume that it was a stupid null check error and not they getting hacked? As that would have been really bad for a cybersecurity company. Share your view !!!!
4mo ago3.5K views
WorstVista
Stealth4mo
This if true will eventually come out later if not now. And that will hurt their reputation very badly.
They are aware of this hence would have taken necessary steps
Anonymousss
Accolite4mo
I doubt that later they would accept something like this. Once all the mess cools down all they have to do is just reject all the allegations.
Discover more
Curated from across
