KNULL / ABRIENDO CANAL

We hack you before they do.

Web, API and mobile pentesting under written authorisation. Every finding comes with the full path: how we got in, what we reached and what to fix first.

Hackers picked for your system

We build the team around what needs testing: web, mobile or infrastructure. A person confirms every finding before it reaches your report.

Certifications
  • CPTS
  • OSCP
  • OSED
Methodology

OWASP ASVS · PTES · NIST SP 800-115

Included
  • Fix retesting
  • NDA before data
  • Quote within 48h
For your audit

A report and attestation letter your auditors and customers accept for SOC 2, ISO 27001 and vendor security reviews.

How someone would get in, step by step

Breach Path links findings into routes: where someone gets in, what they reach and which step breaks the chain. Try the demo.

BREACH PATHINTERACTIVE DEMO · FICTIONAL DATA
PATH 01

Exposed panel

OPEN PATH
STEP 01 / 04

Forgotten subdomain

staging.acme.example, no owner.

STEP 02 / 04

Exposed admin panel

reachable without VPN.

STEP 03 / 04

Default credentials

never changed after deploy.

STEP 04 / 04

Customer data access

full export possible.

WHAT TO FIX FIRST

Take staging.acme.example off the internet and rotate the default credentials.

PATH 02

Leaked token

OPEN PATH
STEP 01 / 03

Employee public repo

linked from their profile.

STEP 02 / 03

API token in git history

old commit, never rotated.

STEP 03 / 03

Cloud storage access

backup bucket.

WHAT TO FIX FIRST

Revoke the leaked token and purge the secret from the repo history.

PATH 03

Reused credentials

OPEN PATH
STEP 01 / 03

Credentials in a third-party breach

from an unrelated service.

STEP 02 / 03

Reused on remote access

same password, no second factor.

STEP 03 / 03

Foothold on the internal network

from outside, as an employee.

WHAT TO FIX FIRST

Force a reset on the reused passwords and require a second factor on remote access.

Explore the steps. See where to break the chain.acme.example

What we test

We set the scope with you. Every finding is reproducible, and once you fix it we test it again.

Our research

We publish browser and mobile security research, with the methodology and evidence so anyone can check it.

  • Browser security
  • Mobile security
Explore research

Continuous Offensive Assessment

A 30, 60 or 90-day window: we watch what changes on your perimeter and tell you before someone else takes advantage of it.

  1. 30 days

    Baseline

    We map your external surface and set the starting point. You know exactly what you expose today.

  2. 60 days

    What changed

    We compare against the baseline and show you what is new, what reopened and what is already fixed.

  3. 90 days

    Continuous validation

    We retest earlier findings and only close the ones we confirm are fixed.

What we watch in the window
  • New subdomains
  • Patch diffs
  • Exposed services
  • Leaked credentials
  • Repos
  • Apps
  • APIs

With or without AI, your call

In both modes, a person validates every finding.

Hybrid AI

AI to correlate information and prioritise review. Our hackers test and validate every finding.

Data and models agreed before the project starts.

AI-less

Reconnaissance, testing and analysis without AI models. For projects that need to exclude AI throughout the engagement.

Conventional tools. No AI models.

Based in Mexico, working across four regions

All remote: Mexico, the United States, Europe and India.

  1. Mexico
  2. United States
  3. Europe
  4. India / Bengaluru
Remote coverage · Illustrative routes

Tell us what you want tested

We reply with a proposed scope and working mode.

Or write to us directlysales@knullcorp.com

We reply with a proposed scope and working mode.

sales@knullcorp.com
What do I receive?

Findings with evidence, impact, reproduction steps and prioritised fixes. Includes retesting and a session with your team.

How does the project start?

We agree on assets, testing windows, data handling and a technical contact. Testing starts with written authorisation.

Can we sign an NDA?

Yes. We sign a confidentiality agreement before exchanging sensitive technical information.

Want to work with Knull?Show us a sample of your work. ↗
KNULL / DATOS
DATA / CONTACT

Only what
we need.

What we store

For company requests: organisation name, services of interest, context, timeframe, chosen mode and email. For applications: handle, email, a public link to your work and whatever context you choose to share. Your consent and its date are stored with it.

What for

To assess the request and continue the conversation about a project or collaboration. These forms are not used to sign you up to any marketing list.

Where

Requests are stored on the server hosting this site. The form does not use an AI model and does not send your answers to analytics services.

What to avoid

Do not include passwords, secrets, third-party data or confidential vulnerability details. Exchanging sensitive information is agreed after the contact and scope are defined.

Share only information you are authorised to provide. Keep your request reference so we can identify it when the conversation continues.