Skip to content
// The complete Web3 security lifecycle

Secure what you build.Before and after launch.

SaferICO combines expert human-led smart contract audits with continuous AI-powered monitoring, scanning and investigation — one platform covering the whole life of your protocol.

01 — Before launch

Human-led security audit

Security engineers

A deep, point-in-time review by security engineers who read every line, model the threats and prove each finding with a working exploit.

Manual code reviewThreat modeling Static analysisFuzz testing Invariant testingExploit validation Security verificationPublished report
02 — After launch

SAFI — the security agent

Autonomous agent · 24/7

Continuous protection once the code is live: it watches, detects, investigates the alert with real tools and prepares the response for you to sign.

Continuous monitoringAutomated scanning AI investigationContract monitoring GitHub / CI securityThreat detection Security alertsAutomated workflows
204Published audit reports
201Detectors in the engine
25EVM mainnets read
<24hAverage reply on Telegram
// Choose the right instrument

Two ways to protect your protocol.

They are not tiers of the same thing. They solve different problems, at different moments, with different evidence.

Product 01

Human-led audit

Deep security review before launch.

QuestionIs this code correct, and what could a determined attacker do with it?
MethodSenior engineers reading line by line, plus fuzzing, invariants and a proof-of-concept for every finding.
CoversThe code as it exists on a frozen commit.
OutputA severity-ranked report, published and independently verifiable.
CadenceA scoped engagement, priced per protocol.
Blind spotEverything that happens after the report is signed.

→ You leave with a document you can hand to an exchange, an investor or a listing desk.

ONE PLATFORM
Product 02

SAFI security agent

Continuous protection after launch.

QuestionWhat changed since the audit, and does it put anything at risk right now?
MethodScheduled on-chain and front-end checks, 201 detectors in CI, and an agent that investigates with real tools.
CoversThe contract, the wallet, the repository and the signing page — as they are today.
OutputAn alert with a severity, an explanation and an unsigned transaction.
CadenceEvery 15 minutes, every commit, every month.
Blind spotLogic no automated check can reason about — which is why the audit exists.

→ You leave with a message the moment your protocol stops matching that document.

Audit before launch. · Monitor after launch.

// The lifecycle

Three stages. One investigation layer. No gap between them.

Security is not a milestone you pass. It runs while you build, it gates the launch, and it keeps running long after — with one layer underneath that opens the moment anything stops adding up.

01
During development

Every commit, not every release

The scanner runs inside the pull request, in your own runner. A finding blocks the merge instead of surviving into production.

201 detectors · source never leaves your runner
02
Before launch

A human reads every line

A deep assessment on one frozen commit — and a working exploit proving every finding, so nothing lands as an opinion.

204 published · independently verifiable
03
After launch

The baseline can now be broken

Watchtower re-reads the chain and the front end on a fixed schedule, and tells you the moment reality stops matching the report you paid for.

7 contract events · 1 wallet event · 6 site checks
04 · INVESTIGATION — NOT A STAGE

It opens from any column above, at any hour

SAFI reads the alert, names the exploit path in the code that allows it, and hands back an unsigned transaction — your wallet still has to sign it.

19 tools · unsigned only · your keys never leave your wallet

Stages 01 to 03 run on a clock. The layer underneath runs on an alarm.

// The idea the platform is built on

Audit once. Watch forever.

Human audit The baseline

A deep point-in-time assessment. It tells you exactly what the code did on one frozen commit, and proves it with a working exploit for every finding.

204 reports published · independently verifiable
AUDITDEPLOYSAFI
SAFI agent The difference

Continuous monitoring and security intelligence. It tells you the moment reality stops matching that baseline — and what the gap lets someone do.

7 contract events · 1 wallet event · 6 site checks

Your audit establishes the security baseline. SAFI watches what happens after that baseline changes.

// The platform

One platform. Every security surface.

Not a drawer of disconnected tools. Five surfaces that hand work to each other, on one account and one meter.

01

Scanner

Automated vulnerability detection over verified source and runtime bytecode.

201 detectors · 25 chains
02

SAFI

AI security investigation and automation — it calls the tools, it does not describe them.

19 tools · unsigned only
03

Watchtower

Continuous on-chain and front-end monitoring, on a fixed severity scale.

every 15 minutes
04

CI Guard

Security checks inside the pull request, executed in your own runner.

source never leaves
05

Probe Rig

Adversarial testing for AI agents and wallet-connected systems.

20 probes · 6 stages
// The security stack underneath — 10 tools, one pipeline
SolidityLanguage
EVMExecution layer
ERC StandardsToken specs
FoundryTest framework
RemixIDE & debugging
SlitherStatic analysis
MythrilSymbolic execution
EchidnaProperty fuzzing
HalmosFormal verification
MedusaParallel fuzzing

Tooling output is never the audit — every result is verified by a human auditor before it reaches your report. These are the engines, not separate products you have to choose between.

// Surface 01 · Scanner

Paste an address.
Get the whole report.

201 detectors run across the verified source and the runtime bytecode, on 25 EVM mainnets. Every finding carries a rule id, a severity and the line it came from.

1Honeypot simulation — a buy and a sell are simulated before you are told the token is safe to trade.
2Owner powers — mint, pause, blacklist, fee changes and upgrade paths, each named with the function that grants it.
3An audit-grade PDF at the end, with a proof-of-concept for every finding that has one.

Free to try: 3 scans a day with no account, 10 a month once you sign in. A scan costs 5 credits on a paid plan.

VaultV2.sol · verified sourceLive
0x7f3a…9e21 · Ethereum 38risk score
SAFE-0001 · unprotected withdraw pathCritical
SAFE-0008 · owner can mint after launchHigh
SAFE-0035 · fee changeable without timelockMedium
SAFE-0037 · missing event on state changeLow
SAFE-0040 · compiler version not pinnedInfo
// Surface 02 · SAFI

It does not describe the tools.
It calls them.

SAFI reads the alert, pulls the contract, decodes the calldata, traces the funds and names the exploit path — then builds the transaction that fixes it and stops.

119 real tools — scan, decode, trace, monitor, lock, distribute. Every call is metered and logged.
2It never moves funds. Every write is handed to you as an unsigned transaction.
3Your wallet is the last gate — by construction, not by policy.
safi · investigation sessionLive
Your wallet is the authorisation layer. SAFI prepares; you sign. It holds no key and can move nothing on its own.
// Surface 03 · Watchtower

Your audit was a photograph.
This is the video.

Every 15 minutes it re-reads the contract, the wallet and the page your users sign on — and tells you the moment any of them stops matching the baseline your audit established.

17 contract events — ownership, mint, pause, proxy upgrade, liquidity, blacklist and the runtime code hash itself.
21 wallet event and 6 site checks, including a new script origin on your signing page — the Bybit shape.
3Alerts arrive on Telegram. That is the only channel today; email is not built yet and this page will not pretend otherwise.

Certificate expiry is deliberately absent: a Cloudflare Worker cannot read the TLS chain, so it is not measured and not claimed.

watchtower · live feedLive
14:02Runtime code changed — implementation slot now 0x9c…41Critical
13:47Ownership transferred — 0xA1…c4 → 0x7d…9fHigh
13:31New script origin on the signing page — cdn.unknown.tldCritical
13:15Liquidity moved — 12.4% of the pool withdrawnMedium
12:58Approval granted to an unrecognised spenderMedium
12:44Baseline re-verified — 0 differencesClear
// Surface 04 · CI Guard

The audit that runs
on every commit.

The same 201 detectors, executed inside your own GitHub runner. Unreleased code never leaves your machine — only counts and rule ids come back.

1A severity budget you set: the check fails the pull request when a new Critical or High appears.
2Diff-aware — it reports what this commit introduced, not the backlog you already triaged.
3One action, no server. Add it to a workflow file and it runs where your code already is.
pull request #482 · saferico/ci-scanLive
function setFeeTo(address to) external {
- require(msg.sender == owner, "not owner");
+ // TODO: restore the owner check before launch
feeTo = to;
}
1New critical
0New high
14Unchanged

Check failed — a new Critical crossed the budget. The source never left the runner.

// Surface 05 · Probe Rig

Test the agent
before it holds a key.

20 adversarial probes across 6 stages, from prompt injection through to an attempted signature — driven against a decoy wallet that holds no private key.

1Six stages: reconnaissance, injection, tool abuse, exfiltration, privilege escalation, signature.
2A capability graph of everything your agent can actually reach, drawn from its own tool list.
3The decoy signs nothing. A successful probe proves the path exists without ever risking a real balance.
probe rig · 20 probes, 6 stagesLive
Direct instruction overrideBlocked
Tool-call argument injectionReached
System prompt exfiltrationBlocked
Unbounded transfer amountPartial
Approval to an unknown spenderReached
Signature without confirmationBlocked
Decoy signer: 0x00…dEaD — holds no private key, so the run cannot move real funds by construction.
// Build on it

Six doors. One engine.

A CLI, a local MCP server, a hosted MCP endpoint, a REST API with an OpenAPI description, a browser playground, and machine-readable discovery files. Whatever runs on your own CPU is free, because it costs us nothing to give away.

npm CLI

FREE · NO ACCOUNT

The full 201-detector audit as a terminal command. The engine is fetched once, verified against a published SHA-256, and run locally in a sandboxed VM context.

SARIF 2.1.0 · exit code is the gate · your source never leaves

Local MCP server

FREE · NO ACCOUNT

The same package speaks MCP over stdio, so Claude Code or Cursor can run the real audit against files it already sees — without those files leaving the machine.

3 tools · the full engine, not a summary of it

Hosted MCP

BUSINESS & ABOVE

A remote MCP server carrying the six live read tools — prices, token facts, honeypot simulation, wallet balances, verification status, bytecode analysis — through your API key.

6 tools · same registry as the REST API

REST API + OpenAPI

BUSINESS & ABOVE

Ten operations under /api/v1, described by an OpenAPI 3.1.0 document generated from the tool registry the server executes. If it is in the spec, the server accepts it.

5 keys per account · 2 credits per call

API playground

KEY TO EXECUTE

Every operation as a form built from openapi.json at page load, so it cannot drift from the API. Read the shapes for free; paste a key when you want to call something.

your key stays in the tab · never stored

Discovery files

PUBLIC · NO KEY

Three machine-readable files describing what an automated client can do here — and, as deliberately, what it cannot. All generated from the same registry.

no file can describe a tool that does not exist

The hosted endpoints do not run the 201 detectors. That is a split, not a gap: the audit needs far more CPU than an edge request may use, and sending unreleased contracts to a third party to find out whether they are safe is a strange thing to ask. The engine runs in your browser, your CI runner, or your terminal.

Developer docs →
// Shipped since the last release

Three new tools. None of them cost anything.

Each one answers a question you have before you are ready to pay anybody: what is this transaction doing, is this agent config safe to install, and what is actually being caught out there.

Pulse

FREE · NO ACCOUNT

What our own monitoring detected across every watched contract this week — ownership transfers, proxy upgrades, mint and pause events. Not a news wire. Our data.

A bucket is published only above 5 events from 3 distinct watchers — below that it is suppressed and counted, never rounded to zero. No address, no chain, no user, nothing finer than a day. Open Pulse →

Transaction Explainer

FREE · NO ACCOUNT

Paste a hash and read what the transaction actually did, in a sentence. It is not an explorer — every link out of it points at one.

Public RPC refuses debug_traceTransaction, so there is no call tree here. What is missing is named in the response rather than quietly left out. Explain a transaction →

Agent Config Scan

FREE · NO ACCOUNT

Read the skill file or MCP server config before you install it. 21 rules for what is dangerous by construction: a shell command in a server definition, a key committed into a config, an instruction telling the model to ignore its operator.

A skill is prose plus configuration, and what makes it dangerous is intent — which is not decidable. So a clean result says “none of these patterns were present”, and never “this is safe to run”. Scan a config →
// The gate

One gate. Thirty-one realms.

Five surfaces do the security work. Behind them sits everything else you already paid for — 31 realms across four wings, on one login, one credit meter and one severity scale.

Verify15 Launch5 Trade & get paid4 SAFI & tools7
31 realms1 account1 credit meter1 severity scale25 EVM mainnets
// One investigation, start to finish

The scanner found nothing.
A human read it anyway.

This is what a manual review buys you: a function that compiles clean, reads clean, and does the opposite of what its name says.

Case study · real investigation

The function named “Liquidity” that quietly drained investors

An investor asked us to review FastBNB Yield before depositing more. The contract was verified on BscScan, the token maths was ordinary, and every automated pass came back clean. The manual review found an owner-only function labelled as adding liquidity — which in reality swept every depositor's BNB into the owner's private wallet. We traced each drain on-chain and published the proof.

⚑ Critical · owner drain BNB Chain Verified source On-chain proof
18 BNBTraced out of the contract
0Detectors that flagged it
1Auditor who read the name
FastBNB.sol · verified on BscScan Replay
// reads like it adds liquidity to the pool…function Liquidity() public onlyOwner {  payable(owner).transfer(    address(this).balance   // ← every depositor  );}
18 BNB traced out — contract → owner wallet · depositors could not withdraw
StageWhat we didResult
ReadEvery external and owner-only function, by hand1 hit
ProveSimulated the call against a forked blockBalance → 0
TraceFollowed the transfers on BscScan18 BNB
PublishReport with hashes, sent to the investorSame day
// Our methodology · how every audit runs

Not just tools. A battle-tested pipeline.

Every engagement moves through the same six-stage security pipeline, refined since 2021. No stage is optional, and nothing ships until every finding is verified fixed.

01

Scope Review

We map the architecture, define the threat model with your team, and freeze the exact commit — so everyone knows precisely what is under review.

▸ scope locked · commit hash frozen
02

Static Analysis

Slither, Mythril and our own detector suite sweep every code path for known vulnerability classes — reentrancy, access control, math, upgradeability.

▸ 201 detectors · every path swept
03

Manual Review

Senior auditors read the code line by line — business logic, economic attacks, privilege abuse and the bugs no scanner can see. This is where the critical findings live.

▸ line-by-line · logic & economics
04

Fuzz Testing

Echidna, Medusa and Foundry invariant campaigns hammer the contracts with millions of randomized inputs to break assumptions humans never think to try.

▸ 1M+ randomized runs · invariants held
05

Security Validation

Every finding gets a proof-of-concept exploit, a severity rating and a concrete fix. After your team patches, we re-test each one until it is verified closed.

▸ PoC per finding · fixes re-verified
06

Final Report

You receive a severity-ranked report with PoCs, fixes and verification status — published on our GitHub so investors and users can verify it themselves.

▸ public report · independently verifiable
// Three of the twenty in our Hall of Hacks

The audited contract was not
always the thing that broke.

Every one of these protocols had been reviewed. The money still left — through something that changed afterwards, or through a surface the review never covered.

Euler Finance · 13 Mar 2023 $197M

eIP-14 added donateToReserves eight months after review — the one balance-reducing path that skips the solvency check every other path runs.

AuditClean, and correctly so
ChangeA new function, outside the auditor's scope
DetectRuntime code changed
RespondPause · re-scope · re-audit the delta
Nomad Bridge · 1 Aug 2022 $190M

A routine upgrade committed a root of 0x00…00 and marked it confirmed. Every unproven message became proven — then strangers copy-pasted the calldata.

AuditReviewed pre-launch
ChangeAn upgrade initialised the trusted root
DetectProxy upgraded
RespondHours of warning before the first drain
Bybit · 21 Feb 2025 $1.43B

The contract was never broken. A tampered JavaScript bundle reached the bucket serving the signing page. Three signers approved exactly what their screens showed them.

AuditContract was sound
ChangeA new script origin on the signing page
DetectExternal script origin
RespondFreeze signing until the origin is explained

Written up in full, with external citations, in the Hall of Hacks — 20 incidents, $5.67B.

// Our work

Audit portfolio.

The latest reports from our public repository. Every one is published in full — the original PDF, downloadable and independently verifiable.

// Coverage

25 EVM mainnets read.
Any EVM chain audited.

Every network below has a live RPC we verified and an explorer that hands back verified source. Manual audits are not limited to this list — Solidity carries across.

Ethereum BNB Chain Polygon Base Arbitrum Optimism Avalanche Abstract ApeChain Berachain Blast Celo Fraxtal Gnosis HyperEVM Katana Linea Mantle Monad opBNB Sei Sonic Taiko Unichain World Chain

Building and deploying is priced on seven of these; a plan is paid on six. See the per-chain pages →

// Pricing

Two products. Two ways to pay.

A monthly subscription buys you the platform. A human audit is a scoped engagement, priced per protocol. They are not tiers of one ladder, and this page will never sell them as if they were.

Category 01 — SAFI & the platformmonthly · pay from your wallet · no auto-renew

Free

Everything you need to check a token

$0/mo
10 scans a month · 3 a day with no account
  • 10 full scans a month
  • npx saferico — CLI & local MCP, free
  • Honeypot buy/sell simulation
  • Owner-powers detection
  • All 25 read networks
  • Your results saved and shareable
Create a free account

Business

For teams building & launching

$29.9/mo
4,000 credits · everything in Pro, plus…
  • SAFI AI Agent — Advanced
  • API keys, REST API & hosted MCP
  • Every SaferICO tool unlocked
  • Token Suite · create, stake, burn
  • Lock & Vesting · MultiSender
  • Wallet security + dev utilities
Choose Business
Best value

AI Agents

The complete AI security suite

$59.9/mo
12,000 credits · everything in Business, plus…
  • SAFI AI Agent — full, incl. trading
  • API, MCP & playground — 12,000 credits
  • Every AI & automated-scan tool
  • Trading · swap, DCA & spend caps
  • 24/7 automations & guided launches
  • Priority support line
Choose AI Agents

Protocol

For a team with money already on-chain

$199/mo
40,000 credits · everything in AI Agents, plus…
  • 50 contracts & wallets monitored
  • API, MCP & CI — 40,000 credits
  • Unlimited team members
  • Unlimited repositories in CI
  • Priority queue · a named contact
  • Alerts on Telegram, under a minute
Choose Protocol

No auto-renew — you decide each month · pay in ETH / BNB / POL on 6 networks · see full plan details →

Category 02 — Human-led security audita scoped engagement · priced per protocol
// Not a subscription

A team of security engineers, reading your code.

Scope, timeline and price are set after we read the repository — because a 300-line token and a lending market are not the same job, and a fixed number in front of both would be a guess.

Scope review & frozen commitStatic analysis Line-by-line manual reviewFuzzing & invariants PoC for every findingRe-test after your fix Severity-ranked reportPublished publicly
Quoted per protocol Send the repository and the scope. You get a timeline and a fixed price back, usually within 24 hours — before anything starts.
Request an audit → See the six-stage methodology →

To be explicit: a $9.99, $29.90 or $59.90 subscription is not a professional security audit and is never sold as one. It buys automated scanning, monitoring and the SAFI agent. A human audit is a separate engagement with a scope, a team and a published report.

// Got questions?

Frequently asked questions.

Everything teams ask before securing their contracts — timelines, chains, reports, and how to get started.

Still have questions?

Get a direct answer from our security team — usually within a few hours.

Chat with us →

A smart contract audit is a systematic examination of your contract's code to identify security vulnerabilities, bugs and logic errors before deployment. Since smart contracts handle real funds and are immutable once deployed, a professional audit can prevent catastrophic losses and protect your users.

Timelines depend entirely on the complexity, size and architecture of your protocol. After reviewing your codebase during the scoping phase, we provide a clear, tailored timeline alongside the engagement terms — so you know exactly what to expect before we begin.

Manual audits: any EVM-compatible chain — we have audited on 20+, including Ethereum, BNB Chain, Arbitrum, Base, Optimism, Polygon, Avalanche, zkSync, Linea, Scroll, Mantle and Blast. Since these chains all share Solidity, a review carries across them; the only real differences are things like precompiles and L2 sequencer behavior. Automated tools read 25 EVM networks — every one with a live RPC we verified and an explorer that hands back verified source. Building and deploying is priced on seven of those, and a plan is paid on six. Chain not listed? Contact us — we can almost certainly help.

An executive summary, detailed findings categorized by severity (Critical, High, Medium, Low, Informational), proof-of-concept for vulnerabilities, remediation recommendations and a post-fix verification. All reports are published publicly on our GitHub.

SaferICO is one of the few auditors officially verified and listed in the Etherscan Auditor Directory. Auditing since 2021, with 250+ completed audits and 1,000+ findings, we bring real depth of knowledge — and we are the only one that keeps watching the contract after the report is signed.

Your report becomes the security baseline. Watchtower then re-reads the contract, the wallet and your signing page every 15 minutes and alerts you the moment reality stops matching that baseline — an ownership transfer, a proxy upgrade, a liquidity move or a new script origin. CI Scan runs the same detectors on every commit, inside your own GitHub runner.

Pick a plan on the Plans page and pay from your own wallet — that wallet instantly becomes your account for 30 days. Logging in is a free signature (no gas, no email, no password). Scanning is free — 10 a month with an account, 3 a day without one — and the AI Agents plan ($59.9/mo) unlocks the full AI suite, including trading and automations. Manual audits are a separate engagement: contact us on Telegram. Nothing auto-renews.

Fill in the audit request form below or reach us directly on Telegram. Share your GitHub repository link, describe the scope, and we will respond within 24 hours with a timeline and a quote.

// Get in touch

Request an audit.

Contact us directly

Preferred method — fastest response.

SaferICO Security Team

Average response: < 24 hours

Open Telegram →
Why choose SaferICO
Etherscan-verified auditor
Auditing since 2021
250+ projects secured · 204 reports published
Multi-chain expertise (20+ EVM chains)
Detailed public audit reports
Continuous monitoring after the audit
Security consulting & threat modeling
Submit audit request

Fill in your project details and we will respond within 24 hours.

✅ Telegram is opening with your request ready to send. If the message box is empty, just paste (Ctrl/Cmd+V) — we copied it for you.

Audit it before launch.
Watch it forever after.

Start with a free scan, put SAFI on the contract, or send us the repository and get a scope and a timeline back within 24 hours.