<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk" -->

---
title: Unified Code, Unified Risks: Uncovering Vulnerabilities…
description: A security research writeup details how .NET MAUI's shared C# codebase creates a unified attack surface across iOS and Android. The shared assembly compiles to...
canonical: https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Unified Code, Unified Risks: Uncovering Vulnerabilities… | daily.dev
og:description: A security research writeup details how .NET MAUI's shared C# codebase creates a unified attack surface across iOS and Android. The shared assembly compiles to...
og:url: https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk
og:image: https://api.daily.dev/og/posts/u0AzvJjfK.png
og:image:alt: Unified Code, Unified Risks: Uncovering Vulnerabilities…
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Unified Code, Unified Risks: Uncovering Vulnerabilities…

**[Sliver C2 Documentation](https://daily.dev/sources/bishopfox)** · 10 min read · 0 upvotes · 0 comments

## Summary

A security research writeup details how .NET MAUI's shared C# codebase creates a unified attack surface across iOS and Android. The shared assembly compiles to readable Intermediate Language even in release builds, allowing decompilation with ILSpy after extraction via a custom tool called mauidll for Android and simpler direct extraction on iOS. The piece walks through the full extraction pipeline (fingerprinting, split-APK handling, AOT stub identification, XALZ payload extraction) and ranks common vulnerability patterns: high-fidelity IL decompilation, hardcoded secrets in shared code, over-reliance on the SecureStorage abstraction, single points of failure in shared authorization/crypto logic, and NuGet supply chain risk. Recommendations include obfuscation, moving sensitive logic server-side, verifying hardware-backed storage, auditing dependencies, and treating both platforms as one attack surface during testing.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://bishopfox.com/blog/unified-code-unified-risks-uncovering-vulnerabilities-net-maui-applications>

## Questions this post answers

### How do you extract the readable .NET assemblies from a .NET MAUI Android app?

Extract the DLLs from the assembly store file (libassembly-store.so or libassemblies.<abi>.blob.so) that ships alongside the app, since each assembly is wrapped in a per-assembly XALZ block-compressed section rather than shipped as a plain DLL. A custom tool called mauidll automates locating the payload, calculating offsets, and decompressing the entries into valid PE files that ILSpy can then open directly.

_Teams securing MAUI apps can follow ongoing mobile security research like this on daily.dev._

### Why is .NET MAUI code easier to reverse engineer than native iOS or Android code?

Standard MAUI release builds rely on Mono ahead-of-time compilation rather than true Native AOT, so the shipped assemblies still contain readable Intermediate Language. A decompiler like ILSpy can turn that IL back into something close to the original C#, preserving method names, class structure, string literals, and control flow on both the Android and iOS builds, unlike stripped native binaries.

_Developers weighing cross-platform frameworks can track security trade-offs like this via daily.dev._

### What are the biggest security risks specific to .NET MAUI's shared codebase architecture?

The main risks are hardcoded secrets in the shared assembly exposed on both app stores at once, over-reliance on the SecureStorage abstraction which does not guarantee hardware-backed protection by default, single points of failure where a flawed authorization or crypto check ships identically to iOS and Android, and NuGet supply chain exposure since a compromised dependency affects both platforms simultaneously.

_Anyone hardening a shared MAUI codebase can follow this kind of vulnerability research on daily.dev._

## Similar posts on daily.dev

- [How to Transition to Cross-Platform Development](https://daily.dev/posts/how-to-transition-to-cross-platform-development-uga1o4nlv) · Telerik · 0 upvotes · 0 comments
- [Integrating Native Device Features in .NET MAUI with Built‑In APIs](https://daily.dev/posts/integrating-native-device-features-in-net-maui-with-built-in-apis-afigz5kxo) · Syncfusion · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#reverse-engineering](https://daily.dev/tags/reverse-engineering), [#.net-maui](https://daily.dev/tags/.net-maui)

[View this post on daily.dev](https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Unified Code, Unified Risks: Uncovering Vulnerabilities…","url":"https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk"},"datePublished":"2026-09-24T22:03:09.740Z","dateModified":"2026-09-24T22:03:36.649Z","description":"A security research writeup details how .NET MAUI's shared C# codebase creates a unified attack surface across iOS and Android. The shared assembly compiles to...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8b9f7f409051d161e56b336e9481d30a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8b9f7f409051d161e56b336e9481d30a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Sliver C2 Documentation","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Sliver C2 Documentation","logo":"https://media.daily.dev/image/upload/logos/placeholder.jpg","url":"https://daily.dev/sources/bishopfox"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,reverse-engineering,.net-maui","timeRequired":"PT10M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Sliver C2 Documentation","item":"https://daily.dev/sources/bishopfox"},{"@type":"ListItem","position":3,"name":"Unified Code, Unified Risks: Uncovering Vulnerabilities…"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/unified-code-unified-risks-uncovering-vulnerabilities--u0azvjjfk#faq","mainEntity":[{"@type":"Question","name":"How do you extract the readable .NET assemblies from a .NET MAUI Android app?","acceptedAnswer":{"@type":"Answer","text":"Extract the DLLs from the assembly store file (libassembly-store.so or libassemblies.\u003cabi\u003e.blob.so) that ships alongside the app, since each assembly is wrapped in a per-assembly XALZ block-compressed section rather than shipped as a plain DLL. A custom tool called mauidll automates locating the payload, calculating offsets, and decompressing the entries into valid PE files that ILSpy can then open directly. Teams securing MAUI apps can follow ongoing mobile security research like this on daily.dev."}},{"@type":"Question","name":"Why is .NET MAUI code easier to reverse engineer than native iOS or Android code?","acceptedAnswer":{"@type":"Answer","text":"Standard MAUI release builds rely on Mono ahead-of-time compilation rather than true Native AOT, so the shipped assemblies still contain readable Intermediate Language. A decompiler like ILSpy can turn that IL back into something close to the original C#, preserving method names, class structure, string literals, and control flow on both the Android and iOS builds, unlike stripped native binaries. Developers weighing cross-platform frameworks can track security trade-offs like this via daily.dev."}},{"@type":"Question","name":"What are the biggest security risks specific to .NET MAUI's shared codebase architecture?","acceptedAnswer":{"@type":"Answer","text":"The main risks are hardcoded secrets in the shared assembly exposed on both app stores at once, over-reliance on the SecureStorage abstraction which does not guarantee hardware-backed protection by default, single points of failure where a flawed authorization or crypto check ships identically to iOS and Android, and NuGet supply chain exposure since a compromised dependency affects both platforms simultaneously. Anyone hardening a shared MAUI codebase can follow this kind of vulnerability research on daily.dev."}}]}
```

