←
Michael6,517 posts
Michael avatar

Michael

@MasterMike88

Biggest moron on the platform (probably). iOS Jailbreaking stuff. Openly Autistic. Not a security researcher or developer. Side Account: @MasterOfMike88

◷ Joined February 2019▧ 541 Photos and videos
Michael avatar
Michael@MasterMike88·Nov 15

Note: I’m not going to block just because someone says “wen eta” or asks a legitimate question in good faith - that’s sort of an inevitability (though if you’re that person who does ask wen eta: learn to not do that, it’ll make everyone’s lives better - patience is golden)

Michael avatar
Michael@MasterMike88·Nov 15

Just as a general PSA/reminder: if you’re outright harassing other people for eta’s and whatever, I have zero qualms with blocking you in the slightest I cannot believe how difficult it is for people to at least have a small amount of patience for stuff.

POC_Crew avatar
⟳ Michael retweeted
POC_Crew@POC_Crew·Nov 12

🛡️ Time for some iOS security! Alfie CG (@alfiecg_dev) - “How a Nation State Broke the Last Line of Defence: Inside Coruna’s PPL & SPTM bypasses” #POC2026

Post attachment
opa334@infosec.exchange avatar
⟳ Michael retweeted
opa334@infosec.exchange@opa334dev·Nov 11

Good thing the App Store does not have a history of apps shipping sandbox escapes to spy on whether users have installed some app they don't like and Apple does not have a history of not sanctioning / removing apps shipping such a sandbox escape.

A vulnerability (worse_query) affecting iOS 26.7.1, 27.0.1, and 27.2 allows malicious apps to read local files from other apps, putting seed phrases, private keys, and login credentials at risk across the entire ecosystem. This is an iOS-level issue, not unique to Binance. Immediate Action Required: - Delete any apps installed from untrusted sources (such as sideloaded or manually signed IPAs). - Update iOS and all apps to the latest official versions. - If you suspect a breach, transfer funds to a new wallet created on a clean device and reset all active login sessions. Never install unauthorized packages, and keep your software up to date.

Jake James  avatar
⟳ Michael retweeted
Jake James @Jakeashacks·Nov 10

there’s multiple people sharing screenshots of apps that do literally nothing claiming it’s an exploit, assume everything is fake until proven otherwise

Michael avatar
Michael@MasterMike88·Nov 10

I hate interacting with the crypto side of this platform, but since Binance has completely failed at what we call being accurate: - worse_query is a reported 0-day, it is not patched on 27.2.1/27.3b1 (latest release/beta) - this is (realistically) only going to be exploited in a malicious App Store app or an app you explicitly sideload To the crypto people on this platform who do not care about jailbreaking or tweaking devices or whatever in the slightest: updating is what you should be doing, but it also doesn’t fix this. And of course, to the people who actually care for jailbreak stuff and whatever: - worse_query has absolutely zero value in terms of an actual jailbreak - all it lets you do from a tweak perspective (practically) is some minor gestalt stuff on 27 (which is mostly irrelevant for most devices) - obviously don’t update, if you’re competent you're fine

A vulnerability (worse_query) affecting iOS 26.7.1, 27.0.1, and 27.2 allows malicious apps to read local files from other apps, putting seed phrases, private keys, and login credentials at risk across the entire ecosystem. This is an iOS-level issue, not unique to Binance. Immediate Action Required: - Delete any apps installed from untrusted sources (such as sideloaded or manually signed IPAs). - Update iOS and all apps to the latest official versions. - If you suspect a breach, transfer funds to a new wallet created on a clean device and reset all active login sessions. Never install unauthorized packages, and keep your software up to date.

Michael avatar
Michael@MasterMike88·Nov 10

I am increasingly becoming more annoyed at the human species at large and how gullible they are to obvious larp/slop. anyways on a better note: yesterday’s update didn’t change anything meaningful, palera1n still works on iPadOS 18.7.12, still don’t update and stay where you are

Michael avatar
⟳ Michael retweeted
Michael@MasterMike88·Jul 20

I’m just going to put this out for future reference. If something (for modern) is not posted here, there’s a few reasons why something might not be posted here: 1. I legitimately haven’t seen it (assume I have though) 2. It’s from an individual who has been provably incompetent before 3. It’s something that I do not have high confidence will have anything of value come from it 4. It’s just someone wanting attention/clout 5. It’s not something that is meaningfully relevant for anything

Michael avatar
Michael@MasterMike88·Oct 26

As to my thoughts on the new iPad mini from a practical perspective: they’re simple: - It’s not worth the $700 base price - It’s good from a longevity perspective that it has an A20 Pro (probably also means it will be another 2-3 years before it gets updated) - The iPad mini also makes the iPad Air look absolutely terrible right now (imo the next iPad Air should get an OLED display, but that also means it’ll probably be even more expensive which will just make the lineup even worse) - The iPad lineup as a whole is a complete mess and I honestly think it’s not worth getting a brand new iPad at all right now (used/discount market could be interesting though)

Michael avatar
Michael@MasterMike88·Oct 26

Here is a mega-post of everything about the latest updates from today (+ the iPad mini (A20 Pro)) First, as to iOS/iPadOS 27.2 and iOS/iPadOS 26.7.2: These versions are believed to have patched the bugs in the chain that Calif showed off, as well as the likely SPTM bug (which was patched in 27.2b3). As a result: - If you’re on 27.2/26.7.2 already: restore to 27.1 (Duo)/27.0.1 (non-EoL)/26.7.1 (EoL) - If you have an iPhone Duo: stay on 27.1 - If you have an iPhone 18 Pro/18 Pro Max: restore to 27.0.1 if you‘re on 27.0, otherwise stay on 27.0.1 - If you’re currently on a 27.0 beta: restore to 27.0.1 - If you have any other device: stay on your current version and wait to see what happens (the aforementioned 90 day delayed ota timer starts today for those on 26.x and lower, so you have until then to decide to update or not) Next, as to iOS/iPadOS 18.7.11: There are some CVE’s here, but nothing provably relevant to the above was patched (kernel version was also unchanged between 18.7.10/18.7.11). Based on that, if you have a device that hit EoL on 18.x, I wouldn’t update to 18.7.11, but - compared to the other updates - this does not appear to be as significant. Additionally, for checkm8 devices: palera1n works on iPadOS 18.7.11 (iPad 7th Generation) and tvOS 26.6.1 (Apple TV HD and Apple TV 4K 1st Generation). Lastly, as to the iPad mini (A20 Pro): I’ll leave my thoughts on the iPad itself as a reply to this. However, there’s a slightly interesting thing about this that makes its inclusion in this main post relevant. When the updates came out today, we also got a delta OTA to a 27.2 build for the new iPad mini. Delta OTA’s - for reference - are smaller OTA’s that usually only include baseline stuff and the things that changed between a base version and the target version (this is how an OTA from 27.0 -> 27.0.1 is smaller than an OTA for 26.0 -> 27.0.1, as an example). The interesting thing about this delta OTA? The delta is from 27.0 (24A7427). The implication of this is - of course - the possibility that the preinstalled version for the new iPad mini will be vulnerable to all the relevant bugs patched in 27.2. My recommendation? If you’re getting a new iPad mini and care about any of this: activate with a computer, don’t use a backup, and setup the device before connecting to any form of internet.

TheSAS2026 avatar
⟳ Michael retweeted
TheSAS2026@TheSAScon·Oct 21

You've definitely heard of #DarkSword. @imnotclarity is now walking us through the inner workings of some key elements of this exploit chain and re-implementation of the DarkSword kernel exploit supporting iOS 26.0.1. #TheSAS2026

Post attachmentPost attachmentPost attachmentPost attachment
Michael avatar
Michael@MasterMike88·Oct 17

Something else I've only thought about recently that I'll add to this: If you're considering getting an iPhone 18 Pro Max specifically (all other iPhones are fine), I would highly recommend getting one sooner rather than later. Due to Apple/AT&T somehow managing to screw stuff up with 27.0 for the 18 Pro Max in the US (I have absolutely no idea how but they did), if you get a brand new 18 Pro Max *and it comes on 27.0* (27.0.1 is fine), you will likely get a forced update to whatever latest is when you try to activate it. Right now, this is a non-issue because latest for the 18 Pro Max is 27.0.1. The problem is more if you get an 18 Pro Max on 27.0 in like a month from now when 27.0.1 is no longer latest.

If you’re on any iOS 27.x beta: please restore to 26.6.1 RC (heavily preferred since it has DelayOTA) or 27.0.1. If you’re on an iPhone 18 Pro (Max): install 27.0.1, it patches some important issues for usability If you’re on any other stable iOS release: *STAY WHERE YOU ARE!*

Michael avatar
Michael@MasterMike88·Oct 17

For some more information, here's a post from opa on the elephant platform: infosec.exchange/@opa334/117… Additionally, it's worth noting that this bug type realistically probably doesn't matter for A12(X/Z) and A13 devices, as those devices now have momentarius.

Michael avatar
Michael@MasterMike88·Oct 17

For those that aren't aware: 27.2 beta 3 did likely patch an SPTM Bypass. The advice through everything has still been "stay and wait for stuff", and that hasn't changed in the slightest However, as there's more "known" (for lack of a better term) about this (compared to the exact specifics of the Calif chain), I would say that - if you end up in a situation where you absolutely have to update - I would highly recommend avoiding anything past 27.0.1/27.2b2 (and probably 26.7.1 for AlternateSU)