Skip to content

MalFixer Toolkit for Inspecting and Recovering Malformed And...#2134

Open
carlospolop wants to merge 1 commit intomasterfrom
update_MalFixer__Toolkit_for_Inspecting_and_Recovering_Ma_20260415_191546
Open

MalFixer Toolkit for Inspecting and Recovering Malformed And...#2134
carlospolop wants to merge 1 commit intomasterfrom
update_MalFixer__Toolkit_for_Inspecting_and_Recovering_Ma_20260415_191546

Conversation

@carlospolop
Copy link
Copy Markdown
Collaborator

🤖 Automated Content Update

This PR was automatically generated by the HackTricks News Bot based on a technical blog post.

📝 Source Information

  • Blog URL: https://github.com/Cleafy/Malfixer
  • Blog Title: MalFixer: Toolkit for Inspecting and Recovering Malformed Android APK Files
  • Suggested Section: Mobile Pentesting -> Android Applications Pentesting (new subsection: "APK Anti-Analysis: Malformed ZIP/APK, Corrupted AndroidManifest.xml, Malformed Asset Names"; include MalFixer as a tooling reference)

🎯 Content Summary

Title/Scope: MalFixer is a Python toolkit (Python 3.8+; tested on Linux and macOS) for malware analysts / reverse engineers / mobile security researchers to inspect and recover intentionally malformed Android APKs. These APKs attempt to evade static analysis by abusing ZIP/APK container structure weaknesses, corrupting AndroidMa...

🔧 Technical Details

APK anti-analysis via malformed ZIP structures: Attackers can craft APKs (ZIP containers) with inconsistent/corrupted local headers and central directory metadata so that different ZIP parsers disagree on file offsets/sizes, causing decompilers/extractors/scanners to crash or skip entries. A robust response is to parse both views (local headers vs central directory), detect inconsistencies, and rewrite/normalize ZIP metadata so file enumeration and extraction become deterministic again.


Anti-analysis via corrupted binary AndroidManifest.xml: Because many Android analysis pipelines require a valid decoded manifest, attackers can break the manifest encoding/structure to halt processing. A recovery approach is to decode what is salvageable, reconstruct a minimally correct manifest representation, and reinsert it into a rebuilt APK so tooling can proceed.


Anti-analysis via malformed asset filenames: ...

🤖 Agent Actions

I’m mapping the Android/mobile sections first, then I’ll read several candidate pages to decide whether this belongs in an existing APK-analysis page or requires a new one.
I found the Android app pentesting section. Next I’m reading the index plus several APK/reversing/deobfuscation pages to see whether malformed-APK anti-analysis already has a natural home.
The existing content already covers APK basics, decompilers, and deobfuscation, but I haven’t seen malformed-container anti-analysis documented yet. I’m now searching the repo for direct coverage of corrupted ZIP/APK structures, broken binary manifests, and hostile asset names before I choose the target file.
There’s no existing MalFixer or malformed-APK recovery coverage in the repo. The strongest fit is the main Android applications page, inside static analysis / deobfuscation, because this is an analysis-enablement technique rather than an app vulnerability class.
I’ve narrowed the edit to a single file: src/mobile-pentesting/android-app-pentesting/README.md. I’m locating the exact subsection now so the addition stays short and consistent with the page’s existing static-analysis workflow.
I’m editing the Android applications page now. The addition will be a short static-analysis subsection covering malformed ZIP/APK containers, corrupted binary manifests, hostile asset names, and a concrete MalFixer workflow plus references.
Updated README.md in src/mobile-pentesting/android-app-pentesting/ with a new static-analysis subsection on APK anti-analysis through malformed ZIP/APK metadata, corrupted binary AndroidManifest.xml, and malformed asset filenames. I placed it in the main Android applications page because this is an analysis-enablement technique, not a standalone app vuln class, and there was no existing direct coverage of malformed-APK recovery in the repo.

The new section adds a practical triage workflow, explains the parser-differential angle, includes MalFixer usage examples, and adds the MalFixer GitHub URL to the file’s final ## References block. I verified the inserted section and reviewed the final diff.


This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.

@carlospolop
Copy link
Copy Markdown
Collaborator Author

🔗 Additional Context

Original Blog Post: https://github.com/Cleafy/Malfixer

Content Categories: Based on the analysis, this content was categorized under "Mobile Pentesting -> Android Applications Pentesting (new subsection: "APK Anti-Analysis: Malformed ZIP/APK, Corrupted AndroidManifest.xml, Malformed Asset Names"; include MalFixer as a tooling reference)".

Repository Maintenance:

  • MD Files Formatting: 972 files processed

Review Notes:

  • This content was automatically processed and may require human review for accuracy
  • Check that the placement within the repository structure is appropriate
  • Verify that all technical details are correct and up-to-date
  • All .md files have been checked for proper formatting (headers, includes, etc.)

Bot Version: HackTricks News Bot v1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant