The package examined
The sample records package com.cryptnox.cryptnoxwallet, version 2.15.1, build 57. It contains static findings from the packaged code.
This is an analysis example, not a customer endorsement or a recovered wallet API.
Findings tied to files
The report lists PairIP in classes2.dex, certificate pinning references in classes5.dex, and debugger method references in several DEX files. It also includes Play Integrity and signing-certificate check references.
Each finding includes the matched marker, method, file, confidence, and evidence basis. The record makes the finding traceable.
Presence and behavior are different results
A packaged SDK or method reference shows that code is present. Runtime tests determine whether that code runs in the chosen workflow and what effect it has.
The sample marks runtimeVerified as false. It does not claim to have recreated integrity tokens, bypassed a protection, or completed an authenticated request.
Coverage makes the report useful
Read confidence and coverage together. A marker gives a concrete lead; missing evidence from an unread part of the package remains unknown.
Use the findings to plan the runtime work and its tests. Keep the app build, account requirements, and requested calls tied to the project.
From findings to a working client
The API client delivery needs successful tests for the requested calls in the intended environment. A protection list is one input to that work.
Our public client example shows the separate evidence needed to prove a runnable result.
Build what you need.
Upload your app. We extract its APIs and build your client.
Upload your app