Skip to content
BCTI

Web3 & offensive security · Andorra

We attack your protocols and systems before someone else does.

BCTI is an Andorran security firm with a Web3 focus. We audit smart contracts with manual review, fuzzing and formal verification, attack the apps and keys around them, and run penetration tests and red teams on traditional infrastructure.

  • Manual review, fuzzing and formal verification
  • Proof of concept for every serious finding
  • Strict confidentiality

Web3 security

From line-by-line review to mathematical proof

Smart contracts are public, hold real value and are hard to patch. We stack three layers of assurance on your code and also test the Web 2.5 layer around it, where many of the largest losses actually begin.

Three layers of assurance

  1. L1

    Manual review

    Auditors read every line, model how value moves through your protocol and hunt for the logic, economic and integration flaws no tool can see.

    Best atDesign, logic and economic flaws

  2. L2

    Invariant fuzzing

    Stateful fuzzers run millions of random transaction sequences against the properties your protocol must never break.

    Best atEdge cases and broken invariants

  3. L3

    Formal verification

    Symbolic execution and provers check critical properties for every possible input and state, not just the ones a fuzzer happened to try.

    Best atGuarantees for all inputs

Offensive security

Penetration testing and red teaming

From a single web application to a full adversary simulation, every engagement is tailored to your risks, your technology and your timelines.

How we work

A clear process, from scope to fix review

No surprises: you know what we will test, when, and what you will receive.

  1. 01

    Scoping

    We agree on objectives, scope and timelines, and sign the authorisation and NDA. For code we fix a commit hash; for systems, the targets and test windows.

  2. 02

    Threat modelling

    We map your attack surface the way an adversary would: contracts, privileged roles and dependencies, or exposed assets, technologies and people.

  3. 03

    Testing

    Manual review, fuzzing, formal methods and hands-on exploitation, with a working proof of concept for every serious finding.

  4. 04

    Reporting

    An executive summary plus a detailed technical report with evidence, severity ratings and prioritised remediation.

  5. 05

    Fix review

    Once you have fixed the issues, we review the fixes or retest your systems, and update the report.

Why BCTI

Findings that matter, explained so you can act

Aligned with

  • OWASP
  • OWASP SCSVS
  • EEA EthTrust
  • PTES
  • NIST SP 800-115
  • MITRE ATT&CK

Toolchain

  • Foundry
  • Echidna
  • Medusa
  • Halmos
  • Certora
  • Slither
  • Manual and expert-led

    Tools are a starting point, not the deliverable. Every engagement is run hands-on by specialists who think like attackers.

  • Proof, not opinions

    Every serious finding comes with a working proof of concept: an exploit test for contracts, reproducible steps for systems. That leaves no debate about impact.

  • Confidential by design

    Signed NDA from day one and strict handling procedures for every piece of code and evidence we receive.

  • Standards and open tooling

    Our work follows recognised standards, and the fuzzing and verification suites we write are built on open tools your team can keep running.

Insights

Latest from the blog

View all posts

How exposed are you, really?

Tell us about your protocol or your environment and we will propose an engagement tailored to it.

Talk to us