Authorized Software Reverse Engineering
Structured analysis of software you own or are authorized to examine — understanding an undocumented binary, an inherited system with no source, a protocol you must interoperate with, or the behaviour of a dependency you cannot audit any other way.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.
What's covered
- Binary structure analysis: format, sections, imports, exports and linkage
- Behavioural analysis in an isolated, instrumented environment
- Protocol and file-format reconstruction for interoperability
- Dependency and third-party component identification
- Security-relevant findings: hardcoded material, weak crypto usage, unsafe patterns
- Documentation of the recovered design and behaviour
What you receive
- Technical analysis report with the recovered structure and behaviour
- Protocol or file-format specification where that was the objective
- Component and dependency inventory
- Security observations with severity and rationale
- Annotated findings suitable for your engineers to build against
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Written authorization is required before any work begins — ownership, a licence permitting analysis, or an incident mandate
- No DRM circumvention, licence bypass, activation defeat or piracy tooling, under any framing
- No extraction of third-party proprietary source for reuse
- No credential recovery from software belonging to someone else
- We decline engagements whose evident purpose is circumvention, and say why
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Is reverse engineering legal?
- It depends on the artifact, the jurisdiction and the purpose. Analysing software you own, or hold a licence permitting analysis for, is commonly lawful — interoperability and security research have specific protections in many jurisdictions. We require written authorization and will decline work whose purpose is circumvention, whatever it is called on the brief.
- We inherited a system and lost the source. Can you help?
- This is one of the most common and most legitimate reasons to engage. We recover enough of the design and behaviour for your team to maintain, migrate or replace it safely, and we document what we could not determine rather than filling gaps with guesses.
- Can you remove a licence check for us?
- No. That is circumvention regardless of how the request is worded, and it is outside what we do. If you have a genuine licensing dispute, that is a matter for your counsel and the vendor.
Related services
Reverse Engineering
Malware Reverse Engineering & Threat Analysis
Defensive analysis of a sample you encountered: what it does, what it touched, how it persists, what it talks to — turned into indicators and detection logic your team can deploy today.
Reverse Engineering
Firmware & Embedded Binary Reverse Engineering
Analysis of authorized firmware images and embedded binaries — filesystem extraction, hardcoded secret discovery, cryptographic usage review and update-mechanism security for devices you build, deploy or must assess.
Offensive / Testing
Secure Source Code Review
Some flaws only reveal themselves in the code. Our experts read your source — by hand, guided by tooling — to find vulnerabilities, insecure patterns and design weaknesses that black-box testing can miss.