Harden commercial apps and protect core code

Yudun hardens commercial Android and iOS apps with code obfuscation, Java2C, DEX/SO protection, and VMP. It focuses protection on core algorithms, authorization logic, and critical business paths, raises reverse-engineering and code-reuse costs, and verifies performance and compatibility on real candidate builds.

Are these problems holding back your app?

  • Core algorithms remain easy to locate and reuse after decompilation
  • Blanket protection slows launch or frequently used flows
  • A hardened build crashes but no one can isolate the responsible policy
  • Every release risks bringing an old compatibility problem back

How Yudun handles them

  • VMP for high-value functions

    Focus protection on algorithms, authorization, protocols, and entitlements instead of applying the most expensive policy to the whole app.

  • Layered code protection

    Combine VMP, Java2C, DEX/SO protection, and obfuscation according to the project, with a clear job for each layer.

  • Candidate compatibility testing

    Test launch, critical flows, crashes, performance, and target systems on the actual deliverable, not on a configuration preview.

Public assessment: obtaining DEX and ELF did not by itself recover the core algorithm

A four-level assessment of a Yudun Android candidate separated recoverable material from program structure, invocation relationships, and algorithmic equivalence.

Read the full assessment

What the assessment disclosed

  • Reviewed standard recovery, deeper recovery, secondary decompilation, Native mapping, and algorithmic equivalence
  • Examined the relationship between DEX, ELF, the loading chain, and the core algorithm
  • Recorded what each level actually recovered and which conclusions remained open

Scope: This is a redacted assessment of one candidate, not a universal result for every app, version, or attack condition.

From assessment to delivery

See the delivery method
  1. 01

    Choose the assets

    Identify the algorithms, authorization, and protocol paths whose recovery would cause business loss.

  2. 02

    Build the PoC

    Configure the scope in the real build chain and keep comparable, recoverable candidates.

  3. 03

    Accept the scope

    Run performance, compatibility, and critical-flow regression on the same candidate before delivery.

Questions customers often ask

Why Blanket VMP Hardening Is Not Recommended

Define the scope of VMP protection across five dimensions: business assets, attacker ROI, execution frequency, blast radius, and release candidate acceptance. Includes actionable configuration and regression strategies.

View details
View all articles

Questions before purchase

Should VMP protect an entire application?

Usually not. Prioritize code with clear value to an attacker and a path that can be tested independently.

How is VMP different from obfuscation?

Obfuscation changes names, structure, or control-flow readability. VMP further changes the execution representation of selected code, with a different acceptance cost.

Does VMP make an application unbreakable?

No. It raises analysis and reuse cost. Outcomes still depend on implementation, scope, runtime conditions, and server-side policy.

What should a team prepare before VMP?

Prepare the candidate build, critical paths, performance baseline, compatibility range, and rollback version before selecting functions.

Security standards and platform references

  1. OWASP MASVS

    Mobile application security controls and verification scope

  2. Android security best practices

    Android application security design and release boundaries

  3. Apple Platform Security

    Apple platform code signing and runtime security context

  4. Android app signing

    Signing identity, upgrade continuity, and release integrity

  5. Play Integrity API

    Server-side decisions and the limits of application integrity signals