Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://github.com/TheQmaks/soSaver Content Categories: Based on the analysis, this content was categorized under "Mobile Pentesting -> Android Applications Pentesting -> Frida Tutorial (or a new page under Android RE/Dynamic analysis: "Dumping runtime-decrypted .so from memory with Frida")". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
Collaborator
Author
|
merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
soSaver is a Frida-based dynamic analysis utility designed to extract native Android libraries (
.so, ELF) directly from a running app’s memory. This is specifically useful when conventional filesystem/APK extraction fails because the real libraries are not present on disk in usable form (e.g., they are encrypted/packed and only decrypted at runtime, dynamically downloaded, generated/unpacked during execution, or otherwise protected against standard extraction).<br...
🔧 Technical Details
Runtime-decrypted native library recovery via in-process instrumentation: When Android apps keep real native code unavailable on disk (encrypted/packed in the APK, decrypted only at runtime; or downloaded/generated during execution), instrument the process with Frida and extract the mapped ELF images directly from memory. This converts “only exists decrypted in RAM” protections into an offline artifact (
.so) suitable for static reverse engineering.Load-time discovery with dynamic loader hooks: Hook native loader entry points such as
dlopenandandroid_dlopen_extto detect exactly when a library is loaded. Upon a hit, identify the corresponding mapped module and dump its bytes from memory, then exfiltrate the dump to a host tool via Frida’s message passing.Non-standard load detection via periodic ELF header scanning: Some protections may map libraries without triggering the expected loader APIs. A generic count...
🤖 Agent Actions
Summary:
.somodules directly from memory using the Frida-based soSaver tool, including workflow and usage commands.Tests:
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.