Sanctioned but Still Spying Intellexa’s Prolific Zero-Day Ex... #1657
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
This blog analyzes Intellexa’s continued use of high-end, mobile-focused zero-day exploit chains, detailing the technical roles of at least 15 CVEs across iOS, Android, Chrome, Skia, and ARM Mali, the structure of an iOS chain internally called “smack”, and the PREYHUNTER iOS post-exploitation stager, plus hunting artifacts including a YARA rule.
Zero-day portfolio and bug classes
Google Threat Intelligence Group (GTIG, formerly TAG) attributes 15 distinct ze...
🔧 Technical Details
Reusable iOS exploitation via JSKit and memory corruption in WebKit
The core trick is to treat WebKit JIT bugs (e.g., CVE-2023-41993) simply as a source of arbitrary memory R/W in the Safari renderer and offload all exploit logic to a generic framework (JSKit). Once a memory corruption vulnerability yields a JS-level primitive (e.g., arbitrary read/write on typed arrays or objects), JSKit handles the rest: it parses in-memory Mach-O binaries to resolve symbols, builds PAC bypass chains for the current iOS version, and manually maps Mach-O payloads directly from memory to execute native code without touching disk. To reuse this trick for new WebKit bugs, an attacker only needs to adapt the initial primitive to JSKit’s expected interface and let JSKit abstract away PAC and version differences, enabling rapid reuse of a single exploitation framework across many RCE bugs.
Chaining renderer RCE, kernel IPC UAF, and code-signing b...
🤖 Agent Actions
Summary:
src/binary-exploitation/ios-exploiting/README.mdwith a new section detailing Intellexa’s reusable Safari exploitation stack (JSKit renderer framework, IPC UAF + code-sign bypass bridge, and PREYHUNTER helper/watcher behaviors), highlighting the chain’s primitives, anti-analysis logic, and stealthy staging capabilities.Testing: Not run (documentation-only changes).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.