tnkre.devGet in touch
Menu

Software security.
From the inside.

TNKRE
Software analysis & source recovery

I examine protected Python, native binaries and mobile applications to understand what can be recovered, how they behave, and where the limits are.

Explore the research

What can a binary
actually tell you?

Unpacking an archive, reconstructing readable code and explaining native behaviour are different kinds of work. Start by knowing which result you need.

Read the technical guide Python, native code and mobile applications
One artifact. Different questions.
Extract
Files & resources
Reconstruct
Readable components
Analyze
Behaviour & findings

Areas of investigation

The questions guide the tools.
The sample determines the scope.

Python recovery

PyArmor / PyInstaller / bytecode

Separating packaging from protection. Assessing recoverable code, resources and the information a build no longer contains.

Native binary analysis

Nuitka / Go / Rust

Following control flow, available metadata and runtime behaviour when the original source is not available.

Mobile application security

Android / iOS / runtime

Examining application artifacts and device behaviour, with a clear boundary between app-side and server-side findings.

Behind the analysis.

More about TNKRE

A useful answer starts with a precise question.

TNKRE is the operator behind this portfolio. My focus is software structure, source recovery assessment and binary security analysis across Python, native executables and mobile apps.

The writing here explains methods and limits. It is not a list of client case studies or a claim that every protected build can be recovered.

Discuss a technical question

How I approach a review

Scope first. Evidence throughout.

  1. Define the question

    Identify the sample, intended result and constraints before choosing a method.

  2. Follow the evidence

    Separate extracted material, reconstructed code and runtime observations.

  3. State the limits

    Record what the evidence supports, what remains unknown and what would resolve it.

Technical scope

Platforms and formats I assess.
Feasibility is confirmed per sample.

PyArmor 8/9 Security Audit & Recovery

Assess the supplied PyArmor edition, protection settings and runtime requirements to identify what can be analyzed or reconstructed.

Agreed Recovery Output & Analysis Report

Nuitka C++ Compiled Executable Audit

Nuitka compiles Python through a C-based toolchain to native code. Review compiled behaviour, C-API interactions and available metadata.

Agreed Native Analysis & Technical Report

Golang Binary Security Evaluation

Go binaries may retain runtime metadata even when debug symbols are stripped. Review available type data, pclntab structures and security logic.

Available Metadata & Security Analysis Report

Rust Native Binary Analysis & Audit

Review native code, available symbols and relevant behaviour in Rust executables. Optimization and inlining can limit source-level reconstruction.

Agreed Binary Analysis & Technical Report

Android APK / AAB Deobfuscation & Reverse

Scoped review of Android APK/AAB packages, available DEX output, JNI native libraries and runtime behaviour on an agreed test device.

Agreed App Artifacts & Technical Report

Scope, price and timing are agreed after review. See service details

A few useful answers

Recovery, deliverables and getting started.

Can PyArmor 7, 8, and 9 recovery restore the exact original source?

Recovery depends on the supplied build, Python version, protection settings and runtime access. A feasibility review determines whether readable Python, selected components or an analysis report is realistic. Comments, original names and exact project structure may be unavailable; complete original-source recovery is not guaranteed.

How does PyInstaller and packed executable unpacking work?

Package inspection identifies bundled modules, resources and bytecode. Extraction can recover those artifacts; producing readable Python is a separate step that depends on bytecode version and decompiler support. PyInstaller, py2exe and cx_Freeze use different layouts, so the expected output is confirmed after reviewing the sample.

What deliverables are provided for Nuitka, Golang, and Rust binary audits?

An agreed audit can include control-flow findings, available symbols or type metadata, reproducible observations and a technical report. Patches or instrumentation are separate scoped deliverables. Native compilation does not preserve an original Python, Go or Rust project that can always be reconstructed.

Do you support Android (APK / AAB) and iOS (IPA) reverse engineering and security audits?

Yes. Reviews can cover Android DEX and native libraries, iOS Mach-O binaries, local storage, network behaviour and application protection. Results depend on the supplied package, permissions, test device and available runtime access. App analysis alone does not cover server-side security or guarantee recovery of original Java, Kotlin or Swift source.

What is the standard turnaround time for project delivery?

Timing and price are confirmed after the sample and acceptance criteria are reviewed. Complexity, protection settings, runtime access and review depth can change the estimate. Ask for a written scope and delivery estimate before work starts; the website does not offer a universal delivery SLA.

How do I place an inquiry or request a technical security evaluation?

Contact TNKRE via Telegram @tnk_k07vn with the platform, file type, known protection and desired result. Agree the scope, transfer method, retention and any NDA before sharing a sensitive artifact. Ordinary Telegram cloud chats are not end-to-end encrypted by default.

Have a different question?

Prepare an inquiry