Amsterdam, NL
Accepting engagements
Every system
has a way in_
Penetration testing / Vulnerability research / Products from the lab / Cloud security / API security / Reverse engineering / Coordinated disclosure / PoC or it did not happen /
Penetration testing / Vulnerability research / Products from the lab / Cloud security / API security / Reverse engineering / Coordinated disclosure / PoC or it did not happen /
What we do
(01) Hover to run
01 / 02[pentest]
Penetration testing
Web applications, APIs and cloud environments across AWS, Azure and GCP. Scoped engagements with evidence for every finding.
$ ./run engagement _
$ ./run engagement --scope app.target.com
↳ spawning agents: recon · authz · inject · cloud
[recon] 214 endpoints, 3 roles mapped
[authz] 200 OK on another tenant’s invoice
[authz] chained with /export → bulk read
[cloud] storage policy reviewed, no exposure
↳ human review: PoC verified · CVSS scored ✓
02 / 02[research]
Vulnerability research
Reverse engineering and original 0-day research, reported to vendors through coordinated disclosure.
$ ./run research _
$ ./run research --target vendor/product
↳ diff patch v4.2.0 → v4.2.1
$ fuzz parser · 1.2M execs
↳ crash: heap overflow, sibling path
$ triage → controlled write
$ ./exploit --target 10.0.0.12:8443
↳ sending payload... shell received
# id
uid=0(root) gid=0(root) groups=0(root)
From the lab
(02) Products
P/01
Early access
Wren
Our offensive methodology, packaged as software. It keeps testing your web applications and APIs between engagements, so new exposure is found before it is exploited.
- 01Runs on the schedule you set, against the scope you approve.
- 02Findings come with evidence, not just a scanner score.
- 03Built by the people who do the hands-on testing.
Request early access →
P/02 · In development
More from the lab
Tools that come out of our research and client work. Announced here when ready.
status: building_
How an engagement runs.
Four stages, one point of contact. You always know where the test stands and what lands in your inbox next.
-
0x01 · stage
Scope
We agree targets, test windows and rules of engagement, and get authorisation in writing before any traffic is sent.
→ You get
Signed rules of engagement and a test plan.
-
0x02 · stage
Attack
Expert-led testing from an adversary perspective, combined with our own tooling for coverage.
→ You get
Critical issues raised immediately, not held for the report.
-
0x03 · stage
Report
Reproducible findings with calibrated severity and remediation your engineers can act on.
→ You get
Full report with PoCs and CVSS, plus a walkthrough call.
-
0x04 · stage
Retest
Once fixes are in, we verify each one before the engagement is closed.
→ You get
Retest results and an updated report.