Our news today has some pros and cons about it. Not all is doom and gloom here, I assure you. We’re going to talk about what we already know, as per the headline. We’ll also touch upon the silver lining with the headline and what you can do to protect yourself.
What’s Happening:
Nintendo hasn’t really done much to block the current exploit we use on the Switch but that all changes with reports of new Switch’s that have been recently purchased. Two users over at GBAtemp have reported getting these new Switch’s that come with FW4.xx. They can still get into RCM mode but when sending payload nothing happens and it sits on a black screen. The good news is these are not the new Mariko units as FW5.0.0 was when support was added for the new upcoming hardware. 
So it’s not a hardware improvement. Just a software patch to only new units as we all knew this would happen sooner or later to countermeasure Team Xecuter SX since it’s considered a piracy tool.
What You Can Do to Protect Yourself:
Buy a used Switch. Or, if you buy a new one, it comes on 4.x.x. This is vital to stay where you are. It is still susceptible to a different vulnerability called deja vu.
https://twitter.com/SciresM/status/1016724847504736256
If you bought an SX Pro or SX OS before a Switch, hope and pray that it will work but if it’s one of these new units it shouldn’t. Since it uses the same hardware exploit that works on current Switches. Team Xecuter will most likely also add in support for the other exploit for 4.x.x.
But for now, these new units have been reported to block sending any payloads to the Switch like hekate (ipl & ctc), SX 1.3 & 1.2. So if you got one of these units DO NOT UPDATE and stay on FW 4.1.0 if you’d like to use homebrew as I’m sure the wait will be well worth it.
If you’re looking for an older Switch I recommend looking for bundles like Super Mario Odyssey .
If you like the author’s work, follow him on Twitter @V1RACY and don’t forget to enter the weekly giveaways!
And as always, stay tuned here on Hackinformer.com for so much more and follow us on Twitter @Hackinformer