Cl0uddStrife 🛰️👾
15.4K posts

Cl0uddStrife 🛰️👾
@Cl0uddStrife
A jack of all trades is a master of none, but oftentimes better than a master of one. ✌🏽🛰️🚀


My friend @joegrand did it again. He’s not just recovering millions in crypto wallets, but also unveiling messy relationships, betrayal, etc. A very entertaining watch reminiscent of the start of a murder mystery. He’s also upgraded from voltage glitching to electro magnetic (EM) glitching. It’s sort of a very complicated Jedi Mind Trick on chips. Here’s a high level explainer: Let’s say the hardware wallet has a max pin retry limit. And it’s coded like this: if attempts >= MAX_ATTEMPTS: lock_device() Inside the chip, the values of attempts and MAX_ATTEMPTS are just bits. 0s and 1s. Literal voltage levels that are low or high. Stored in tiny transistor circuits. When the processor reads them, those electrical states travel through logic gates that perform the comparison. Normally the comparison works fine. But what if you could reach inside the chip and disturb those electrical signals right at the moment the chip is doing that comparison? That’s what EM injection allows. It’s essentially just a few loops of wire held over the chip and a very fast bust of voltage is sent through it. It’s not as simple as it sounds though. You have to discover: - the exact moment in time during execution - the exact physical spot on the chip package - the right distance from the chip - the right pulse voltage - the right pulse duration - the right probe geometry The search space is HUGE. An exponential needle in a hay stack. If you are really familiar with hardware, you can narrow things down, but it’ll still take weeks of searching even after you have automated it. And even after all of that, there is still risk to the wallet across all the steps. Hell, the wallet could be somewhat damaged before Joe even gets it. And tons of people end up not even having the crypto they thought they had. Imagine if one of those people ends up with a dead wallet and blames Joe for it, all while incorrectly thinking they had millions. 😬 youtu.be/MhJoJRqJ0Wc











if your skill depends on dynamic content, you can embed !`command` in your SKILL.md to inject shell output directly into the prompt Claude Code runs it when the skill is invoked and swaps the placeholder inline, the model only sees the result!



@IceSolst @noperator yes! love this and thanks for the SiftRank tip... how was I not following @noperator until now... fixed















