Service · Web3 security

The attack surface your smart contract audit doesn’t cover

Audits review your contracts. Attackers also go after everything around them: RPC endpoints, front ends, bridges, admin panels, keys and privileged roles. We provide continuous Web3 exposure monitoring and human-led pentesting of smart contracts and Web3 infrastructure on EVM-compatible chains, as a complement to your audits.

01 Definition

What is continuous Web3 exposure monitoring?

Continuous Web3 exposure monitoring is the ongoing review of everything around your smart contracts that an attacker can reach: off-chain infrastructure, front-end code, keys and privileged roles. A smart contract audit examines the contract code at a point in time; this watches the rest of the system as it changes.

This service is delivered by our team today, with the team’s own tooling. Web3-specific checks are performed by people, not automated by our platform. The platform’s general exposure intelligence, such as public source maps and public code references, covers the off-chain web surface.

02 Beyond the contract

What we review beyond the contract code

What we review beyond the contract code
AreaWhat we look for
RPC endpoints and nodesExposed or misconfigured endpoints, administrative methods open to the internet, missing limits
Front-end integrityInjected or modified scripts that could drain wallets, unexpected third-party script changes, exposed source maps
Bridges, relayers and keepersOff-chain components that sign or relay transactions: their hosts, their keys and who can control them
Admin panels and back officesDashboards and management interfaces reachable from the internet
Leaked keys and secretsPrivate keys, mnemonics and API keys in public repositories, source maps and front-end bundles
Privileged rolesOwner and admin roles, multisig signers and thresholds, timelock delays
Upgradeable proxiesWho can upgrade, through which process and with what delay
Oracle configurationData sources, staleness limits and fallback behavior
03 Pentesting

Human-led pentesting of contracts and infrastructure

Our team tests contracts and the infrastructure around them from an attacker’s point of view: access control, upgrade paths, privileged functions, integrations and the off-chain services that depend on them.

Findings follow the same evidence standard as the rest of our work: Validated with the evidence that proves them, or reported as a Signal for review. Reports are signed by our security director. This complements a smart contract audit; it does not replace one.

04 Safety

Safety rules that do not bend

  • No mainnet transactions, ever

    Validation happens only on local forks of the chain. We never send a transaction to mainnet.

  • Authorization and ownership first

    We verify ownership of your domains and get your written authorization for contracts and infrastructure before any testing.

  • The scope you approve

    Contracts, chains, hosts and exclusions are agreed in writing, and nothing outside them is touched.

05 How it works

How a Web3 engagement runs

  1. Scope

    Contracts, chains, front ends, off-chain services and the roles that control them.

  2. Verify and authorize

    Domain ownership verification and written authorization before any testing.

  3. Monitor and test

    Continuous review of the exposure around your contracts, plus scheduled pentests by the team.

  4. Report and retest

    Signed reports with evidence, and a retest after each fix.

06 Who it is for

Who it is for

Exchanges, custodians, DeFi protocols, wallet providers and digital-asset service providers, including those preparing a registration dossier for regulators such as El Salvador’s CNAD. See our Web3 and digital assets specialization.

07 FAQ

Questions about Web3 security

Is this a smart contract audit?

No. It complements one. An audit reviews contract code at a point in time; we test the contracts and the infrastructure around them as an attacker would, and keep watching that infrastructure as it changes.

Which chains do you cover?

We cover EVM-compatible chains.

Do you ever send transactions to mainnet?

No. Validation runs only on local forks of the chain.

Is Web3 monitoring automated in your platform?

Not today. Our team performs the Web3-specific checks with its own tooling. The platform’s general exposure intelligence covers the off-chain web surface, such as public source maps and public code references.

Find it before an attacker does.

Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.

Facts on this page verified 11 November 2026.