OpenAI is partnering with Hacktron to find vulnerabilities in its systems. Read the announcement.

Skip to content Hacktron Sign in [S]
Hacktron Sign in [S] Customers Blog Docs Contact Sign in
Select example:

Hacktron Whitebox

Full white-box pentests. At machine speed.

Hacktron Whitebox gives your pentest what black-box testing lacks: your source code. With it, Hacktron finds the business-logic and data-flow flaws an outside tester can’t see, and proves each one.

You see the price before you start and finish with a report ready for SOC 2 or ISO 27001.

Book a demo or start a pentest.

Scope

One application, from its source code to its deployed app.

Code

A connected repository, a public
URL or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the
folders you pick.

Dynamic testing

Optional. Your app’s URL and test
sign-in steps.

Context

Optional. Architecture notes or a
threat model.

Estimate Pentest starts
Code

A connected repository, a
public URL or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the
folders you pick.

Dynamic testing

Optional. Your app’s URL and
test sign-in steps.

Context

Optional. Architecture notes
or a threat model.

Estimate Pentest starts
Code

A connected repository, a
public URL or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the
folders you pick.

Dynamic testing

Optional. Your app’s URL and
test sign-in steps.

Context

Optional. Architecture notes
or a threat model.

Estimate Pentest starts
Code

A connected repository, a
public URL or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the
folders you pick.

Dynamic testing

Optional. Your app’s URL and
test sign-in steps.

Context

Optional. Architecture notes
or a threat model.

Estimate Pentest starts
Code

A connected repository, a
public URL or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the
folders you pick.

Dynamic testing

Optional. Your app’s URL and
test sign-in steps.

Context

Optional. Architecture notes
or a threat model.

Estimate Pentest starts
Code

A connected repository, a public URL
or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the folders
you pick.

Dynamic testing

Optional. Your app’s URL and test
sign-in steps.

Context

Optional. Architecture notes or a
threat model.

Estimate Pentest starts
Code

A connected repository, a public URL
or an archive.

Revision A branch, tag or commit. Scope

The whole repository, or the folders
you pick.

Dynamic testing

Optional. Your app’s URL and test
sign-in steps.

Context

Optional. Architecture notes or a
threat model.

Estimate Pentest starts
Code A connected repository, a public URL or an archive. Revision A branch, tag or commit. Scope The whole repository, or the folders you pick. Dynamic testing Optional. Your app’s URL and test sign-in steps. Context Optional. Architecture notes or a threat model. Estimate Pentest starts Code A connected repository, a public URL or an archive. Revision A branch, tag or commit. Scope The whole repository, or the folders you pick. Dynamic testing Optional. Your app’s URL and test sign-in steps. Context Optional. Architecture notes or a threat model. Estimate Pentest starts Code A connected repository, a public URL or an archive. Revision A branch, tag or commit. Scope The whole repository, or the folders you pick. Dynamic testing Optional. Your app’s URL and test sign-in steps. Context Optional. Architecture notes or a threat model. Estimate Pentest starts

Testing

Agents read the application and trace untrusted input from where it enters to where it is used. Each candidate finding is tested in an isolated sandbox, or against your deployed app when dynamic testing is on, then confirmed or dismissed with the reason. Security researchers validate findings and deliver reproducible issues with remediation guidance.

Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46 Creating environment Building call graph Mapping attack surface Tracing data flow Dynamically testing exploits 26:46

Fixes

Choose Remediate on a finding and a Hacktron agent writes a fix, tests it and opens a pull request.

Learn more about Automations .

New finding Verify No fix needed False positive Fix Test Failed Success New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed New finding Verify Fix Test Success No fix needed False positive Failed

Reporting

Each confirmed finding comes with where it is, how it was proven and how to fix it. The full report is for your engineers and the executive report for leadership and auditors. Both are reissued after the free retest, and an attestation letter confirms the pentest.

The sample full report is from a pentest of a demo expenses app.

Page 7 of the sample full report: finding HCK-001, predictable password-reset tokens permit account takeoverPage 7 of the sample full report: finding HCK-001, predictable password-reset tokens permit account takeover
Full report
Page 6 of the sample executive report: findings summary and key findingsPage 6 of the sample executive report: findings summary and key findings
Executive report
Sample attestation letter confirming a retested pentestSample attestation letter confirming a retested pentest
Attestation letter

Price

The price follows the size of the code.

Questions

Is it a black-box test?

No. Whitebox reads the source, so it follows implementation details, data flows and business logic. For sensitive code, upload an archive, or run it inside your own network on the Enterprise plan.

Is dynamic testing safe?

Point it at a staging deployment with test accounts. Before the pentest starts, Hacktron follows your sign-in steps while you watch, and every action is logged.

Can we start it from our own tools?

Yes. Start a pentest from Slack, over MCP or through the API. An organisation admin approves the start.

Contact

Book a demo or start a pentest.

[↓] [↑] [enter] to visit
Menu
[M]
Next in menu
[J]
Previous in menu
[K]
Find
[F]
Ask
[A]
Sign in
[S]
Copy page
[C]
Listen
[L]
Justification
[R]
Language
[G]
Dark mode
[D]
High contrast
[H]
Shortcuts
[I]
Close
[Esc]