Public scan · no wallet · evidence-first

Scan a token, a contract, a repository. Get the evidence.

Quick scan

One paste. Auto-detect route. Review the report.

No walletNo loginEvidence-based

VegaSec runs read-only checks on public sources and returns one report: what we found, how strong the evidence is, and what we could not check. No wallet, no login, no promise that a target is safe.

Free, no wallet, read-only, shareable report URL.

vegasec · evidence scan output

sample
vegasec scan 0x4a3f...e21b
source verified · etherscan
solc 0.8.19 · resolved from pragma
slither · 47 detectors armed
semgrep · 31 rules
reentrancy · withdraw() L142 · HIGH
tx.origin auth · L88 · MEDIUM
evidence bundle sealed · 3 sources
evidence level · PARTIAL · sources read 7 of 9
could not check · 2 items · source unavailable, human intent

Buyer-ready sample report

This is a report, including the parts we cannot confirm.

Pre-Launch Token Watchlist

EVIDENCE: PARTIAL

This is an evidence level, not a safety verdict.

Sources read
7 of 9
Findings
7 (0 high, 3 medium, 4 low)

Could not check

  • source unavailable One planned source returned nothing for this target.
  • source not verifiable One planned source has no verified equivalent for this target.

Repository Audit

DeFi Repository Risk Review

EVIDENCE: PARTIAL

8 of 9

deployer risk0/100
owner risk0/100
liquidity risk0/100

The 0 to 100 score lives inside the report, after the evidence and the unknown items, with the formula published. It is derived, not the answer, and it does not include what the scan could not check.

Example report, generated from a public sample target.

Measured, not claimed

Proof you can open, not a logo wall.

Four figures this product can prove today. Each one links to the page or the stored artifact it was read from, and each one names the sample it was measured on.

One artifact per figure

Static engine on the corpus

of 143 contracts

101 of 143 labelled targets matched (70.6%)

12 bug classes. An alarm outside the labelled class counts against precision, which is why this is recall and not accuracy.

Open the measurement

Reviewer roles on the same contracts

of 143 contracts

118 of 137 role targets found (86.1%)

9 roles, each measured on its own class. A role that found nothing of its class is not counted as zero.

Open the measurement

Contracts run in the public lane

in the lane

10 contracts with a stored signed report

Bug class from the documented corpus, counts from the stored report. Static analysis: the class is matched, not exploited.

Open a stored report

Artifact anyone can verify

key vsig-2026-09

10 of 10 batch reports signed

The certificate prints only the fields the signature covered: target, engine versions, severity counts, date and limitations.

Open a certificate

Engine and reviewer figures come from one public corpus (SmartBugs-Curated, MIT, commit 230e649), measured on the same 143 contracts and reconciled by test against the raw artifacts. The batch figure comes from the contracts run in the public lane, each with a stored report; those reports carry static findings only, with no operator judgment attached. Static analysis matches a documented class: it does not reproduce an exploit.

Our measurement

Our assessment, measured, not promised.

Two numbers describe what VegaSec can and cannot see, both measured on the same public corpus, plus the live index of the contracts we have already scanned. Each claim carries its evidence level, its sample and what it does not say.

One artifact per claim

Deterministic engine on the corpus

EVIDENCE: STRONG

101 of 143 labelled expectations matched (70.6%)

Sample: 143 contracts, 12 classes, SmartBugs-Curated (MIT, commit 230e649123).

Outside scope: 42 expectations were not matched and 200 flags fell outside the labelled class, which counts as an alarm even when the finding is real (precision 33.6%). The classes centralization, logic, uninitialized have no label in the corpus, so their recall is not measured.

143 of 143 in scope, 0 outside

Hunter roles on the same corpus

EVIDENCE: PARTIAL

118 of 137 role targets found with the quote inside the cited lines (86.1%)

9 hunter roles, 1,277 of 1,287 calls answered, the same 143 contracts.

Outside scope: 9 fixtures sit in classes with no role (front-running, timestamp-dependence), 4 targets went unanswered, and 2 roles found nothing of their own class (hunt_oracle_price_manipulation, hunt_signature_replay). Fixture precision is 56.1%.

134 of 143 in scope, 13 outside

Our findings judged by a second reader

EVIDENCE: PARTIAL

34 of 37 findings confirmed by a second reader (3 partial, 0 wrong)

Adversarial verifier checked 37 items: it caught 3/3 deviations and wrongly flagged 14/34 correct findings.

Outside scope: a partial verdict is not a confirmation, and the verifier checks the reader instead of labelling the finding, so confirmation is a floor: 14/34 correct findings were flagged by it.

37 of 37 in scope, 3 outside

Contracts we have already scanned

EVIDENCE: PARTIAL

50 contracts in the public index

Live read of the same public index that /contracts renders, newest first, capped at 50.

Outside scope: contracts we never scanned and any protocol whose scan is not listed. The count describes the index, not the market.

50 of 50 in scope, 2 outside

  • VSS-20261004-6BJ83DI7
  • VSS-20261004-ULCW38KZ
  • VSS-20261004-6FZOAZXK
Open the contract index

Sources: docs/benchmarks/2026-09-26-smartbugs-143.json and docs/benchmarks/2026-09-26-role-scorecard-corpus143-r4.rescored.json, reconciled by test against the raw artifacts.

Validated cases

Contracts already run in this lane, with the stored report

Every card below is a public contract this engine scanned. The bug class comes from the documented corpus, the counts and the findings come from the stored artifact, and the link opens the stored report. Static analysis only: it matches a documented class, it does not reproduce an exploit.

12 contracts with a stored report

Pick a contract to open its stored audit.

Bug class

Source

Outcome

12 cases shown

Documented corpus

Reentrancy in a personal bank (the classic DAO pattern)

reentrancy-simple-dao

Reentrancy
16 findings in the stored report

What the scan marked

  • HighMatches the corpusslither:reentrancy-ethReentrancy

    Location: contract.sol:47-60 · Collect

  • Highslither:controlled-array-length

    Location: contract.sol:73-97 · LogFile

Severity split

High 2Informational 14

Stored artifact

Report id
VSS-20260928-6RUEOUOS
Contract file
apps/web/data/benchmarks/smartbugs/reentrancy-simple-dao/contract.sol
Source hash
0196d033850b...

Audit pipeline

What the engine ran, stage by stage

Replay of the audit pipeline the engine runs: intake, source acquisition, toolchain validation, static analysis, finding normalization, exploitability review, remediation draft, operator review and finalization. The finding counts come from the stored report. The per-stage budget is the replay pacing used on this page, not live worker timing.

Ready to replay

  1. Audit intake

    Passed320 ms replay pacing

    Normalizes the submitted target and confirms it can enter the Solidity lane.

  2. Source acquisition

    Passed1.4 s replay pacing

    Resolves the pasted source or the verified explorer source without treating malformed input as demo data.

  3. Toolchain validation

    Passed2.3 s replay pacing

    Confirms the configured static analyzers run and produce parseable output.

  4. Static analysis

    Passed16 findings8.8 s replay pacing

    Runs slither and semgrep against the sandboxed source and captures raw detector evidence.

  5. Finding normalization

    Passed16 findings1.1 s replay pacing

    Dedupes detectors, classifies the vulnerability class and weights severity.

  6. Exploitability review

    Partial16 findings1.9 s replay pacing

    Frames the automated findings with conservative exploitability and limitation notes.

  7. Remediation draft

    Partial16 findings1.5 s replay pacing

    Prepares remediation oriented evidence for the shareable report.

  8. Operator review

    Blocked0 ms replay pacing

    Records whether a human operator artifact is attached before escalation.

    Blocked: no operator review artifact is attached to this stored report.

  9. Finalization

    Partial16 findings620 ms replay pacing

    Publishes the automated report artifact or explains why the scan failed closed.

    Artifact: VSS-20260928-6RUEOUOS

Replay of stored data. No live scan runs on this page.

These stored reports carry no operator review artifact, so the pipeline stops at the automated report. A human review is a separate engagement, quoted per target.

Free, read-only, no login and no wallet. A human review is quoted per target.

The problem, with the source named

Crypto keeps losing funds. Where it loses them changed.

Two public series, each with the report it comes from and the link to read it. No fear number of our own.

TRM Labs, 2026 Crypto Crime Report

$2.87B stolen across about 150 hacks and exploits in 2025

70% of that value sits in five events, and the Bybit breach alone accounts for $1.46B (51%). Source: TRM Labs, 2026 Crypto Crime Report.

Read the report

Immunefi, Ecosystem Vulnerability Scoreboard

DeFi protocol losses fell from $2.62B in 2022 to $534M in 2024, then returned to $680M in 2025

The median loss per incident fell 75%, from $6M to $1.5M, while the number of incidents rose. Source: Immunefi, Ecosystem Vulnerability Scoreboard.

Read the report

What the numbers say about scope

Reading, not a measurement

Both series point the same way: the loss per event got smaller while the number of events grew, and the target moved from contract code to keys, wallets and control planes. A static analysis of source code reads the code. It does not read the key, the deployer machine or the signing process, and it cannot see what changes after the snapshot.

That is why every report carries a date, and why the path continues after the scan.

The path, step by step

When a scan is not enough, and what comes after it.

Four steps and the door each one opens. The scan is free and public. The rest is scoped and quoted in writing before anything runs.

Pick a step

01 · Free scan

No login, no wallet

Paste a contract, a token, a repository or an explorer URL. The engine reads public sources, writes the report and leaves it at a shareable URL. A missing source fails closed to UNKNOWN instead of being filled in.

Run a scan

Read-only and public. This step is free and carries no operator approval.

The scan stays free. The paid steps quote before they run, and the certificate is an artifact served today.

What the scan reads. What stays outside its reach.

Inside the scan

Contract source and bytecode, holder distribution, liquidity and lock state, deployer history, repository activity, NFT interface probes.

Outside its reach

Team intent, off-chain promises, what changes after the snapshot, private deals, price behaviour.

A clean left column never cancels the right one.

Methodology

Scan, Review, Monitor: one evidence model across every surface.

VegaSec keeps the report model consistent: public Scan creates the baseline, Private Review adds operator approval, and Continuous Watch checks whether code or contract state changed after the baseline. Score, confidence, evidence, limitations and next action stay visible across all three.

01

Evidence

Public market data, GitHub signal, verified contract source, NFT interface probes (collected server-side).

02

Score

Deterministic 0-100 derived from severity counts. Same formula across every report; nothing hand-tuned.

03

Confidence

Separate axis. Low confidence pushes the verdict toward UNKNOWN. The two are never collapsed into one number.

04

Next action

Verdict copy is operator-facing English: re-scan, run a Private Review, ship a remediation, or escalate.

Public sources VegaSec reads

Read-only, server-side, no wallet, no login.

Every signal comes from a public provider we name. No paid data resold, no opaque "intelligence feed", no scraping behind login walls.

All keys are server-side only

DexScreener

DEX

Token + Pair market data

Public, key-less pair lookup. Liquidity / holder posture / trading signal.

GitHub public API

GIT

Repository metadata + commits

Default branch, latest commit SHA, license, README, CI signal, security policy.

Etherscan v2 · Basescan

SRC

Verified Solidity source

Acquisition path for slither + semgrep static analysis. Key never exposed to the browser.

Public chain RPC

RPC

NFT interface probes

ERC-721 / ERC-1155 detection, tokenURI inspection, owner / proxy state. Anonymous read.

Limits

VegaSec does not state that a target is safe and does not give investment advice. Every result is a snapshot of public data at scan time. A missing source fails closed to UNKNOWN.